Oxygen XML Forum

Hi,

we have to share many Transformation Scenarios including the xsl-Stylesheets in our company and it's not so comfortable and easy to describe (because you have multiple files and have to change the paths in the scenario).

I have three ideas for a solution:
- Posibility to create transformation scenario packages and put them e.g. into the updateSite.xml for the Addon-Installer
- shared transformations, with an public directory or serverbased to have a shared repository of transformations
- A server-client system to publish everything (settings, scenarios...) to one or more oxygen editors in the lan.

Thanks,
Patrick

Hi Patrick,

You can create transformation scenarios specific for a certain document type/framework.
If you edit a document type in the Document Type Association Preferences page you can define new transformation scenarios in the Transformation tab.
We do not have the possibility to pack a set of transformation scenarios as add-ons but maybe you could pack your entire framework/document type as an add-on and update it whenever you have changes to it.

Regards,
Radu

Hi Radu,

We have already a framework package which includes the author actions, dtd, schematron and some default transformations. But we don't want to deploy all transformations in this package, because it's not easy to use anymore if there are hundrets of transformations defined by default.

Thanks
Patrick

Hi Patrick,

You also have the possibility to export/import global transformation scenarios from the Options menu.
Or you can save them at project level and maybe have all users open and use the same project file which is located on a shared network drive.

For example for out user manual we have a common subversion repository to which our entire project is committed. Our project consists of DITA topics and an Oxygen "project.xpr" project file which has a bunch of transformation scenarios saved to it.
Each of us has a local working copy of the project which is updated from the central repository.
When somebody commits changes to the project file, the others can update it from the central repository and receive new transformation scenarios or changed project-level options.

Regards,
Radu