Define a new publishing tag

You can add publishing tags, which are properties that are applied to a map and its topics when a user selects the Publish option for a map.

For example, a user can select the Version publishing tag and enter a new version number for the map being published. Once published, the new version value appears in the published DITA map's Version column.

Publishing tag values are also written into each document's Custom Properties file; for example:

<version>4.0</version>

Note: You should make these configuration changes in the Test environment and test them before copying them to the Production environment. In a dedicated SaaS deployment, after testing the changes, ask IXIASOFT Customer Support to copy the changes to the Production environment.

1. In the TEXTML Administration perspective, connect to your server.
2. Locate the publishtags.xml file in the repository's /system/conf collection.
3. Check out the file and open it for editing.
4. Create a new <tag> element; for example:

   <tag cascade="true"  label="ISBN" mandatory="false" metaname="isbn">
   </tag>

   Table 1. Tag element attributes

   Attribute	Description	Value
   cascade	Determines whether the user-entered value is written to all children elements (true) or just to the map itself (false).	true or false (default)
   label	Determines the tag label displayed in the Publishing Tags dialog box.	Any sequence of characters.
   mandatory	Determines whether the user must enter a tag value.	true – user must enter a value to publish. false (default) – publishes without user input.
   metaname	Defines the element where the user input will be written in the Custom Properties file.	Must be the same as the NAME attribute of the corresponding index definition.
   historical Uniqueness Index	If present, TEXTML Server verifies that the publishing tag value is unique within the index. For example, for the version tag, this means that you won't be able to reuse a publication version when publishing.	Must be the same as the name of the corresponding index definition. For example, to indicate that the version value entered by the user must be unique within the index, enter: historicalUniquenessIndex="version"

5. Create one or more <classbehavior> elements to determine how the publishing tag values will be written into the Custom Properties file of each type of object, as follows:

   <classbehavior ditaclass="- map/map" name="override" value="false"/>
   <classbehavior ditaclass="- topic/topic" name="override" value="false"/>

   Table 2. Classbehavior element attributes

   Attribute	Description	Value
   ditaclass	The class of document object.	For maps, enter: - map/map For topics and images, enter: - topic/topic Note: In this file, an image is treated as a topic by the CMS. Publication information is written into its Custom Properties file.
   name	Determines the action taken with respect to existing information in an object's Custom Properties file.	Only override is supported. The implementation depends on the value attribute, described below.
   value	Determines whether the override action is actually carried out.	true – existing publishing tags with the same metaname are overwritten. false – the system adds another publishing tag with the same metaname to the object's Custom Properties file.

6. Save, close, and check in the file.
7. Inform users of the changes.
   The changes will be applied automatically once users close and then reopen their IXIASOFT CCMS Desktop. Users can also apply the changes without restarting their CCMS Desktop by clicking IXIASOFT CCMS > Synchronize Configuration.