Delivery Maps
A delivery map is a top-level map that represents a deliverable, such as a user guide or a help center. Heretto CCMS uses delivery maps to scope reporting so that metrics reflect complete deliverables instead of reusable or structural submaps.
A delivery map is a ditamap that represents a complete deliverable, such as a user guide, a release note bundle, or a help center. This is different from a submap, which exists only to organize or group content inside another map.
CCMS uses delivery maps to determine which maps in your content set represent complete deliverables. Reports that analyze reuse or publication-level metrics, such as the Reuse Report (Insights), use delivery maps to scope their analysis so that results reflect your actual deliverables rather than every map in your content set, including submaps that were never meant to stand on their own.
You set a map as a delivery map manually, in the Overview tab of the Resource Drawer. A map isn't treated as a delivery map until you do this.
Delivery Map Operation and Guidelines
You can set any map type as a delivery map. Any map set as a delivery map is treated as one. This is true for both standalone maps that are not referenced by any other maps and submaps that are referenced by their parent maps.
A map is not treated as a delivery map till it is explicitly set as one in the Overview tab. Once a map is set as a delivery map, the CCMS understands that the map represents a complete deliverable, like a user guide or help center, and reflects it in reports.
In reports, topics referenced through a submap are counted as part of the parent delivery map totals.
In reports, submaps with the
processing-role="resource-only"attribute aren't included in delivery map analysis.
Set a Map as a Delivery Map
Mark a map as a delivery map so the CCMS recognizes it as a complete publication. You can do this for any map type in the CCMS.
The CCMS now understands that your map represents a complete deliverable, such as a user guide, and reflects that in reports.