Add Generated Front Matter to a Publication
You can add placeholders to a publication structure that will be filled with generated front matter content during a publishing action:
• List of Effective Data Modules (LOEDM)
• Change Record (CR)
• Highlights (HIGH)
• List of abbreviations (LOA)
• Table of Contents (TOC)
You can add the placeholders at publication root level (in parent and nested publications) or in a publication section.
|
|
Only one of each type of front matter item is permitted in each publication (and each nested publication). They are permitted in any order.
|
To insert a front matter item:
1. Select the publication root, or the publication section in which you want to insert the front matter item.
2. Select one of the following from the Insert New option in the context menu:
◦ Insert New List of effective data modules
◦ Insert New Change record
◦ Insert New Highlights
◦ Insert New List of abbreviations
◦ Insert New Table of Contents
The item is added to the publication structure.
When publishing to PDF, the publishing process generates content for each front matter placeholder present in the publication structure.
When publishing to Arbortext Content Delivery A&D, the publishing process generates and populates a descriptive data module (DM) to represent each front matter placeholder present in the publication structure. These DMs are present in Arbortext Content Delivery A&D output only, they are not saved as objects in Windchill.
Be aware of the following:
• A front matter title page is available for the Front Matter section of a PDF publication (not required for Issue 4.0.1). You can insert a Front Matter Title Page data module as the first data module in a publication and its content will be output. If the publication does not include a Front Matter Title Page data module, a simple title page will be auto-generated for you.
• The list of New and Changed DMs for LOEDM and HIGH is extracted by analyzing the status assigned to DMs when publishing against a publication baseline.
Deleted DMs are not noted.
• HIGH content is generated according to these rules:
◦ Initial publish of a publication structure containing a HIGH object — all New and Changed DMs appear in HIGH. Deleted DMs do not appear.
◦ Subsequent publish of the same publication structure with a baseline selected — only Changed DMs appear in HIGH (compared to baseline). Deleted DMs do not appear unless they have updateHighlights=”1” set.
Subsequent publish of the same publication structure with no baseline selected — all DMs appear as New in HIGH. Deleted DMs do not appear
• Content of HIGH is extracted from these elements in data modules in a publication:
◦ Issue 4.0.1 and 4.1 — simplePara in a reasonForUdpdate element
◦ Issue 4.2 — simplePara and simpleRefPara in a reasonForUdpdate element
• HIGH includes Reason for Update (RFU) information from the latest issue of the DM only.
• HIGH includes a single table of data module code + RFU entries.
• LOEDM and HIGH include relevant entries from their parent publication only.
• LOEDM generated for Arbortext Content Delivery A&D will not include a page count.
• The list of abbreviations for LOA is made up of acronyms in the publication that have the attribute acronymType="at01" set.
Abbreviations are listed alphabetically by term, according to the language of the publication.
Duplicate abbreviations are excluded from the list if their descriptions are identical.
