How Change Tracking works in SDL Contenta

This section assumes that the user is already familiar with the editor tool and how to use it.

Note that the functions and some of the terminology used in this section, such as DI map, check-in, processing instructions or PIs, and scanning for new objects, are explained in the preceding topics.

Object Mapped Elements (OMEs)

In FrameMaker and XMetaL you should not turn change tracking on unless you are editing a leaf node.

  • Arbortext Editor only

    XML and SGML documents exported by SDL Contenta that contain object mapped elements (OMEs) are marked with xy_object processing instructions (PIs) that are not visible in the editor’s interface. The xy_object processing instructions map the element to the Contenta object. When checked-in, or imported, into SDL Contenta, the element and its data are stored in the specified, mapped object within the Contenta hierarchy.

    An OME can be deleted, copied, moved or inserted in your editor. When an element is initially inserted it is never marked with xy_object PIs. The xy_object PI marking occurs when the data is scanned for new objects. The scan can be initiated from the Contenta menu or by saving the file. The Arbortext Command Language (ACL) custom code that does the xy_object marking derives element-to-object mapping information from the DI map stored in Contenta AppData.

  • Other Data (non-OMEs)

    As long as the user does not delete, insert, copy or move an OME, change tracking behavior does not deviate from the standard functionality of the editing application.

  • Activating Change Tracking

    To activate (turn on) change tracking, use the standard editor functionality. For example, in Arbortext (Epic) from the menu bar click Tools > Change Tracking > Track Changes.

    With Arbortext, this inserts the markup after the root element's start tag when the user saves the document. Note that the root element of a document checked-out of SDL Contenta is always a OME. If the root element was locked for edit when the user checked-out the object(s) from SDL Contenta, then the root element's xy_object modified attribute is set to yes. When the user saves the document back to SDL Contenta, the change tracking state information is stored in the root element's Contenta object.

    If the Arbortext document is checked-in to SDL Contenta after the user saves with Change Tracking activated, the next time the Arbortext editor is executed on the same Contenta object, the document displays with Change Tracking turned on.

    This is not true of XMetaL or FrameMaker. You must turn change tracking on each time after you check out a document that was checked in by either of these editor tools