Transformation scenario with multiple ditavals

[zuza]

Hello,

For our Release Notes we need to to specify 2 ditavals for publishing. This works fine when publishing from the command line, but I can't see a way to specify more than 1 ditaval when creating a profiling set by importing a ditaval, nor when configuring a transformation scenario in oXygen Editor. So I can't really see how my output will look like until I run the script to publish from the command line.

I am using oXygen 20.1 and DITA-OT 2.5.

Can you suggest any workaround for this? Can this be implemented in a later version of oXygen Editor?

To explain why we need 2 ditavals: 1 ditaval is product specific and is automatically generated from the product configuration. It contains hundreds of features which are either included or excluded, also specifies which values are included for @product based on a complex subject scheme map, and some values for @audience. This ditaval is/will be used when generating all product specific documents (such as Technical Reference Manual, Core User Guide, etc.).

The second ditaval (also automatically generated) is release specific (one product can have multiple releases) and contains release specific filters, such as release status (alpha, beta, final), customer, product release "label" (branch + version + configuration).


Thank you.

Best regards,
Ozana

[Radu]

Hi Ozana,

I understand your use case.
Indeed Oxygen's "Filters" tab which you usually use when configuring filters in a transformation scenario does not allow you to do that. We have an internal issue already added to improve our Filters tab by allowing our users to choose multiple DITAVAL files. We'll update this forum thread when we manage to make this improvement.
In the meantime, you can edit the transformation scenario, clear all the information you have set in the "Filters" tab, then go to the "Parameters" tab and edit the args.filter parameter and specify in it multiple ";" delimited paths just like you do in the command line with the --filter parameter:

https://www.dita-ot.org/2.5/parameters/ ... -base.html

Regards,
Radu

[zuza]

Thanks, Radu, that works.

Looking forward to the improved Filters tab!

Ozana

[SubSkip]

Hi Radu,

Can you clarify how we are supposed to add the filters to the parameter? I've tried using the full path to the filters as well as just the two filters separated by a comma and neither worked. I get the message that the filters were not found. We have a flat file system.

Thanks!

-Craig

[SubSkip]

Actually, I made a mistake and used a comma instead of a semicolon. This works as described.

Thanks!

-Craig

[Radu]

Hi Craig,

Great, thanks for the update.

Regards,
Radu

[kirkilj]

Hi Radu,

The OT docs say that the path separator is a semi-colon on Windows and a colon on *nix. We use our own Ant build scripts and decided to let the writers provide a comma-separated list and we transparently replace the comma with the ${path.separator} property value before invoking the dita command with the appropriate args.filter parameter value. Otherwise, the build fails spectacularly.

In the meantime, you can edit the transformation scenario, clear all the information you have set in the "Filters" tab, then go to the "Parameters" tab and edit the args.filter parameter and specify in it multiple ";" delimited paths just like you do in the command line with the --filter parameter:

https://www.dita-ot.org/2.5/parameters/ ... -base.html

Regards,
Radu

[zuza]

Just to confirm that the filters tab in oxygen v22 hasn't changed - only 1 ditaval file can be specified at the moment - is that correct?

Thank you.

Regards,
Ozana

[Radu]

Hi Ozana,

This is correct, we have not yet updated our user's interface to allow choosing multiple DITAVAL files in the "Filters" tab.
In Oxygen 22.0 we added support for the DITA OT Project file and you can specify your map, filter pairs also in such a file which can later be used for publishing:

https://www.oxygenxml.com/doc/versions/ ... oject.html

Regards,
Radu