Transformation scenario with multiple ditavals
Posted: Mon Feb 04, 2019 2:02 pm
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
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