For a keyref, listing navtitle instead of key names

Are you missing a feature? Request its implementation here.
colinm
Posts: 28
Joined: Wed May 26, 2010 7:05 pm

For a keyref, listing navtitle instead of key names

Post by colinm »

Hello,

Currently, when one adds @props ,@otherprops, @audience or any attribute that supports controlled values, the editor proposes a list of keys.

Would it be possible to add an option to list in priority the @navtitle associated with the <subjectdef> element, instead of key names?

I ask because for my users, the keys refer to identifiers that they hardly know. On the other hand, having identifiers makes the processing of the content much easier than if the keys were the "human readable" labels.

Having the possibility to expose "human" labels to the authors and leave identifiers in the XML would be very much welcome.

By the way in general, I think taxonomies entry have both an ID and a label.

Thanks!

Colin Maudry
NXP Semiconductors
Colin Maudry
Enterprise documentation analyst and Open Data specialist
Rennes, France
Tweets at @CMaudry
colinm
Posts: 28
Joined: Wed May 26, 2010 7:05 pm

Re: For profiling attributes, listing navtitle instead of ke

Post by colinm »

In the title, I primarily meant profiling attributes, not keyref, though it could apply too.

If by accident there is a label conflict, the actual key name would still appear in the documentation pop up that displays when one hovers a key.
Colin Maudry
Enterprise documentation analyst and Open Data specialist
Rennes, France
Tweets at @CMaudry
Radu
Posts: 9055
Joined: Fri Jul 09, 2004 5:18 pm

Re: For a keyref, listing navtitle instead of key names

Post by Radu »

Hi Colin,

Right, so you have a Subject Scheme map which defines attribute values for certain profiling attributes like @product. It also defines a <navtitle> for each value.
The values of @product can be edited basically in two ways for a certain XML element:

1) If the topic is opened in the Author mode, right click inside the element and choose Edit Profiling Attributes. If you are using this dialog, we already made the necessary changes for Oxygen 15.1 (which will be released in a couple of weeks) to show the navigation title for each subject scheme value instead of showing the actual value.
2) Use the Attributes view or the in-place Attributes editing dialog to edit the value for @product. In this case the value of the attribute is still presented in the combo-box because it is the actual value which will get inserted.

Which one of the choices above do you usually work with?

Regards,
Radu
Radu Coravu
<oXygen/> XML Editor
http://www.oxygenxml.com
colinm
Posts: 28
Joined: Wed May 26, 2010 7:05 pm

Re: For a keyref, listing navtitle instead of key names

Post by colinm »

Hi Radu,

Multumesc for the prompt reply!

I don't use any solution so far, it's a new authoring environment I'm setting up at NXP, so I'm looking for the most user-friendly solution.

The solution with right clicking on an element and getting the filtering window sounds good. I use Oxygen 15.0, and I indeed see key names instead of navtitle. We'll wait for Oxygen 15.1 then.

By the way, to reduce the verbosity, I define the subjects' navitles using the attribute instead of the topimeta block:

Code: Select all


<subjectdef keys="test_developer" navtitle="Test developer"/>
I saw that in your examples you use a topicmeta block: shall I expect the same navtitle support in v15.1 if I use the attribute instead of topicmeta?

Thanks!
Colin Maudry
Enterprise documentation analyst and Open Data specialist
Rennes, France
Tweets at @CMaudry
Radu
Posts: 9055
Joined: Fri Jul 09, 2004 5:18 pm

Re: For a keyref, listing navtitle instead of key names

Post by Radu »

Hi Colin,

Oxygen will identify the navtitle either way, either as attribute or in the topic meta.
Actually it already does, even in 15.0 if you hover over those checkbox choices in the Edit Profiling Attributes the tooltip should show the navtitle for each value.

Regards,
Radu
Radu Coravu
<oXygen/> XML Editor
http://www.oxygenxml.com
Post Reply