Oxygen XML Forum

Hi,
I have successfully set up a trial of Oxygen XML Web Author on my machine and am using the WebDAV plugin to access my DITA files on our SVN repository.
When I open existing topics (that render perfectly in desktop Author), I notice that things like keyrefs are not resolved from within Web Author.
Does Web Author have the perspective of the entire Oxygen project or just the file that is currently opened?
I guess I am still trying to identify how and when we will use this tool but we definitely need an online editor that allows shared updating of content.
Also since the SVN repo cannot be updated directly (and I don't want SMEs updating content directly before I review them), is there a common process for creating a copy of such files in a shared location?
Regards,
Ann

Hello,

keyrefs are not resolved from within Web Author

You have to select the ditamap to be used for resolving keyrefs [1] for the opened topic.

Does Web Author have the perspective of the entire Oxygen project or just the file that is currently opened?

Web Author does not have a project view at the moment. We plan to add a Ditamaps-Manager view which will allow one to see an overview of the entire Dita project, to add new topics/open topics for editing.

Is there a common process for creating a copy of such files in a shared location?

Short answer is there isn't. The long answer is, you can create such a process relatively easy. Here's how:
The WebDAV plugin can enforce the use of a certain server [2]. You can use that enforcing to make sure that SMEs only edit SVN branches created by you.

The SVN repository could look like this:
Whenever you want to send some files/a project for review, you could make a new branch in the SME_ACCESS folder.
The WebDAV plugin could enforce only the visibility of the SME_ACCESS folder from your repository.

At the end, when SMEs have finished their work, you could merge the branches yourself.


We also plan to release a new product, which will fit this use-case. You might be interested in trying out the beta when it's available (1-2 months from now).

The product works like this:

• - Project owner uses oXygen desktop to select a set of files which need to be sent to SMEs for review/editing.
  - The files are copied to a cloud server and SMEs receive links to the copied files.
  - SMEs edit the files using Web Author.
  - At the end, the project owner uses oXygen desktop to merge the changes made by the SMEs in his/her local project.
  - The merging is performed using an xml-diff tool included in oXygen desktop.

[1] https://www.oxygenxml.com/doc/versions/ ... _documents
[2] https://www.oxygenxml.com/doc/versions/ ... d%20server

Best,
Gabriel

Hi Gabriel,
Thanks very much for your detailed reply.
When you say

At the end, when SMEs have finished their work, you could merge the branches yourself.

I don't understand how the SME can update the content directly in an SVN branch without a checkout/working copy of the files?
I am guessing that we need some central location for a checkout of the SME_ACCESS svn files that the SME changes but am not sure how to configure this.
Any advice appreciated,
Regards,
Ann

Hello,

The SVN server can be configured to enable "autoversioning" [1]. This means that when the SME saves the file in Web Author, a commit with an default message is created.

Best,
Cristian

[1] http://svnbook.red-bean.com/en/1.7/svn. ... oning.html