Hi,
I am still a bit unsure of Tridion's support of lack of support for standard DITA condition profiling attributes (audience, platform, product etc.). If I use them, how will they be handled by the SDL processors?
Also if I use the Content Importer to import DITA content that uses these, they are converted to ishconditions. Can this conversion be turned off?
Any feedback around this topic is greatly appreciated,
Regards,
Ann
Hi Ann,
We use a lot of filtering attributes in our DITA implementation, including the standard ones you mention.
However, we chose to convert all DITA attributes in our legacy data to corresponding ishconditions in order to use Tridion's filtering functionality, which is very useful.
Using standard attributes, they will not show up in the Conditions pane in Publication Manager and so on.
We didn't think it was worth keeping them.
Peter S
Cytiva
Thanks for your reply Peter. Can I ask you to clarify what you mean when you say
in order to use Tridion's filtering functionality,
Also do you see any losses/cons in converting your standard condition attributes over to ishconditions?
What editor do you use for authoring your DITA?
Thanks again,
Ann
Thanks for your reply Peter. Can I ask you to clarify what you mean when you say
in order to use Tridion's filtering functionality,
Also do you see any losses/cons in converting your standard condition attributes over to ishconditions?
What editor do you use for authoring your DITA?
Thanks again,
Ann
Hi Ann,
Sorry for the delay.
I presume you will use Publication Manager.
In the Conditions pane you can overview and can create a conditional context for all the ISH-conditions in the DITA files in the baseline.
This is not available if you use standard DITA attributes - they don't show up and can't be applied. Unless you ask/pay for a special customization I would presume.
Similarly, in the tree in Content pane, topics with conditions set on topic level are highlighted red (deselected, will not appear in output) and green (selected, will appear in output).
This does not work for standard DITA attributes either.
We use Oxygen as editor, and can apply ISH-conditions through the WAN bridge to Tridion (there a menu called SDL Tridion DOCS)
The CON with using ISH-conditions is of course that it's not a standard DITA attribute, so we will have to convert them back to DITA attributes should we switch CMS.
But the Tridion ISH-conditions and how you can select them and overview them in the Pub Manager interface is a great feature.
We had to either choose sticking with DITA attributes and lose those features, or convert every standard attribute to an ISH-condition.
I have not regretted that we chose the latter.
Of course it would be great if Tridion could handle standard DITA attributes the same way ISH conditions are handled.
As far as I am aware, this it not possible.
The truth is of course that the filtering functionality was in place before DITA was introduced and likely a decision was taken to stick with it.
Best,
Peter
Translate
