Including customized profiling attributes and styles with framework

[LeeHart]

Our framework supports multiple document types, most of which have profiling attributes. We'd like to have consistent presentation of this profiling. What can we add to our framework to define the profiling attributes and colors/styles to be used with those profiling attributes.

I can see that the data is stored in author.profiling.styles and related settings including profiling.conditions but I don't see where to add those to our framework.

Thanks,

Lee

[Radu]

Hi Lee,

Oxygen does not have the possibility to store profiling settings at framework level. We have an issue for this and if we implement it in a future version I will update this forum thread.

A couple of alternatives for you:

1) You can define the profiling attributes and their values in a subject scheme map which would be part of your DITA content:

https://www.oxygenxml.com/doc/versions/ ... e-map.html

but the problem would still exist for the colors and styles as they cannot be defined in the subject scheme map.

2) Both the Editor / Edit Modes / Author / Profiling/Conditional Text and Editor / Edit Modes / Author / Profiling/Conditional Text / Colors and Styles pages have a "Project Options" radio button. When checked, these settings will be saved at project level. This means that you could share with everybody your custom "project.xpr" and if they all have it opened in their Oxygen "Project" view the settings will be used from it.

3) An Oxygen plugin can be used to impose a set of fixed options:

https://github.com/oxygenxml/wsaccess-j ... se-options

The plugin folder can either be copied to the "OXYGEN_INSTALL_DIR\plugins" folder or installed as an add-on from an internal web site which you may have:

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

An Oxygen plugin can also contain a custom framework folder:

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

So you could have a plugin which has both a framework and imposes the options and have that plugin packed as an add-on.

Regards,
Radu

[LeeHart]

1) None of the content is DITA so we don't use a subject schema map.

2) Squirreling them into project files will do for now. The downside is that when the project settings are imported they seem to overwrite all of the existing settings, rather than merge in.

3) A fixed set of options also has problems; different writing teams have different standard values that they want to give unique colors and not just the ANY color.

Thank you for your quick response.

Lee

[Radu]

Hi Lee,

About (3), you could have distinct add-ons, one for each team, each add-on with a specific XML options file.

Regards,
Radu

[pieterjan_vdw]

Hi Radu,

Is there already an update on adding the profiling attributes to the Framework?

Kind regards,

Pieterjan

[Radu]

Hi Pieterjan,

No, we do not yet have a feature to save custom profiling attribute values at framework level. If you want this for DITA XML, maybe you can use a custom Subject Scheme Map.

Regards,
Radu