Mapping of ditaval files and bookmaps

[susannecm]

We manage the DITA documentation for a set of related products in one Oxygen project.
The project contains one ditaval file per product and output format.
The ditaval files are referenced in the transformation scenarios assigned to the respective bookmaps, so the output is always based on the correct ditaval file.
Is it possible to somehow make sure that the correct profiling condition set is selected by default when a bookmap is opened in the DITA Maps manager? I was reading about the ditavalref element, but it only seems to affect branches in the map.

Thanks for your help
Susanne

[Radu]

Hi Susanne,

Oxygen does not take into account the ditavalref when showing content as filtered-out in the visual editor. Also there are various publishing issues related to ditavalref so you should try to avoid using it for now.
At the same time Oxygen remembers and applies for each opened project the applied profiling condition set but it does not remember and restore the applied condition set for any DITA Map opened in the DITA maps manager view. In a way some of the DITA maps opened in the DITA Maps manager are sub-maps so for them the profiling condition set applied on the master DITA Map should still be used.
So I do not have a good idea about how to make this work automatically for you. We do have API which would allow you to build a plugin which would be notified when a DITA Map becomes selected in the DITA Maps Manager and which could impose a certain profiling condition set. If you want to try this approach maybe we could try to give you more details about this, maybe build a sample plugin for you.

Maybe what we could do in the future would be that when you change the "Root Map" setting in the DITA Maps Manager view to another root map, Oxygen could detect the last applied profiling condition set used for the new root map and apply that. What would you think of that possible improvement?

Regards,
Radu

[susannecm]

Hi Radu,

thanks for the warning - no ditavalref for now.

I Believe that the root map feature would not help in our case - we would just swap one thing to remember against another. However, there might be one exception: What would happen if the root map is always set to <Current map>?

As for the plugin, I assume this is a job for a Java programmer. I cannot do this myself, but I'm allowed to assign the job to a colleague. So yes, I am interested in more details.

Kind regards
Susanne

[Radu]

Hi Susanne,

I asked one of my colleagues to try and build a sample plugin but unfortunately we do not seem to have enough API for this. I will add an internal issue with your use case and maybe we'll have a better solution for this in a future Oxygen version.

Regards,
Radu

[redixus]

Maybe that so curious but not shure where to ask so.

Let's take a doc A and a doc B. The procedures to use them are very same (description, links - except the last one). We have to generate pdf for each doc. But how e proceed it?

[Radu]

Hi,

You could have two transformation scenarios, one for document A and one for document B, each one with its own "Filter" settings.
Or you could have a single transformation scenario which in the "Filters" tab would refer to the ".ditaval" filter using Oxygen editor variables like:

${cfd}/${cfn}.ditaval

so for each of the published .ditamap files a different DITAVAL file will be used.

Regards,
Radu