Manage profiling attributes

Profiling is a term used in the DITA and DocBook schemas to describe conditional text. This feature is useful when you need to produce more than one version of a document, and the versions differ in minor ways. Administrators can customize profiling attributes with specific groups and values you want to use for filtering and flagging. Administrators can also add new profiling metadata conditions using the @props attribute.

FAQ's

How do I know what profiling attributes I have?

If you're an administrator:

To view a list of profiling attributes and their values:

  1. From the top menu, select Administration_TopMenuOpt the Administration menu.
  2. Select Advanced settings, and then Profiling attribute management.
  3. On the Profiling attribute management screen, you'll see a list of all your profiling attributes.

If you're not an administrator:

  1. From the top menu, select Components.
  2. In the Components browser, find a topic to profile.
  3. Right-click the topic and select Edit...
  4. In the Oxygen editor, select Update Profiling Attributes.

Can I change the order attributes are listed?

Yes, if you are an administrator, and you change the attribute's Display Name.

  • Each attribute has a Name and a Display Name.
  • On the Update Profiling Attributes screen, when a user wants to select a profiling attribute, Inspire displays attributes in alphabetical order according to the Display Name.


If you are an administrator, you can change an attribute's Display Name. Follow the steps in Update profiling values.

Can I search for a group or value used in my profiling attributes?

At this time you can only search for a word or phrase that appears in the profiling attribute Name field.

How do I configure a namespace with Valid Values?

Inspire supports using an XML namespace that is identified by a prefix. When an attribute uses that prefix, it’s said to be in that namespace. After creating the namespace as an attribute and marking it as Profiled, you can add values to the namespace. Then users can select the namespace and apply its values to content for use when you need to publish or translate different versions of the same document.

For example, to apply profile filtering to an attribute with a language namespace (xml:lang):

  1. In Attribute Management, an administrator creates an attribute with the following properties:
    • Name is xml:lang
    • Display Name is Language
    • Language option selected
    • Profiled option selected

  2. In Profiling Attribute Management, an Administrator configures xml:lang with Valid Values of en-US and fr-FR.

  3. In the Components browser, a user creates or opens a component that has a Language setting of English. This ensures the xml:lang namespace value is set to en-US on the root element.

  4. In the Oxygen editor, an author selects text and applies a profiling attribute in the Language category with the value of fr-FR.

  5. When a user opens the Publish Component screen to publish the component or a map containing the component, they can add a filter to create a document in just one language. If they want an all-English document, in the Language category they would choose with the value of en-US.

    The same functionality works when a user opens the Translate component screen to send the component or a map containing the component to be translated.

Does it matter if I update groups or values first?

Since groups organize the attribute values into subcategories, the normal process is to first update profiling attribute values, and then organize them into groups. For example, you want to use the audience profiling attribute to list the countries that need a slightly different document than the US English version. To do this, you can follow these basic steps:

  1. Edit the audience attribute.
  2. Create a value for Austria, Bahrain, and Canada.
  3. Create a North America (NA) group to collect the US and Canadian values.
  4. Create a Europe, Middle East, and Africa (EMEA) group to collect Austria and Bahrain.
  5. Edit the Canada value to add it to the NA group.
  6. Edit the Austria and Bahrain values to add them to the EMEA group.
  7. When you add a new value for another country, you can add it to a group at the same time.

You can create groups first if you already know how you want to organize your attribute values. In this scenario, you would create the NA and EMEA groups first. Then, when you add a value for a country, you can add them to the appropriate group at the same time.

Can the attribute name and the group name be the same?

No, you can't create a group with the same value as an attribute value. If you try, you'll see an error telling you that the value is used for another group or attribute, and you must create a unique value.