DITA Aliases
In Ingeniux CMS, DITA content is managed and edited as assets in the Asset Tree; whereas, HTML pages created by the CMS are managed in the Site Tree.
For customers who maintain a "mixed format" authoring environment and require DITA content to be assimilated with page content, the aliases feature may be useful for both managing and publishing these collections.
For example, your organization may need DITA content to display on your website alongside CMS page (HTML) content or to be integrated with page content. It can be difficult to envision the overall organization of your website for these types of "mixed" integration scenarios. The aliases feature helps organizations model complex format integrations in the Site Tree prior to publishing the collection.
To create an alias, provided you have alias management permissions, you can move a DITA map, which resides in the Assets Tree, under a page or folder in the Site Tree. After this action completes, Ingeniux CMS leaves an alias of the DITA map and all of its dependencies under the targeted page or folder. Moving a DITA map to the Site Tree creates an alias of the DITA map; however, the actual DITA map remains in the Asset Tree, where it can continue to be edited and managed. In essence, an alias is a representation of a DITA map that can be updated to reflect changes in the actual DITA map.
Ingeniux CMS provides multiple ways to access and then manage aliases:
By navigating to the Alias Managervia Administration (i.e., ).
By navigating to the Alias Manager via Assets (i.e., ).
By dragging DITA maps from the Asset Tree to the Site Tree in Site and then operating on these DITA structures from the context menu in the Site Tree.
This section describes how to configure aliases by way of Administration.
CMS 10.6.378 Alias Dependency Versioning
DITA dependency behavior differs between CMS 10.6.378 and CMS 10.6.308–10.6.342.
The CMS 10.6.308-10.6.342 alias management system only tracks DITA dependencies based on the latest checked-in version of the DITA map used to create the alias structure. If you mark an older map version for publish, the alias management system will not account for any dependency or content changes in the marked version. If you attempt to publish the older map version, aliases will only account for the latest version content and dependencies.
CMS 10.6.378 introduces dependency versions, where the alias management system now accounts for content and dependency changes in the latest version and any historical version of the DITA content marked to a publishing target.
For example, if the latest version of a DITA map (the most recent version listed in the map's History tab) includes a dependency that is excluded from a previous version marked for the publishing target, that dependency will not be included in alias structure generated during DITA Preview, publish, etc. for that publishing target.
This feature can help you to suppress any aliased DITA dependencies not ready for publish, alter the alias structure for different targets, and more.
You can filter the dependencies included in the alias structure marked for each publishing target by using the publishing target drop-down list in the Site Tree.
See CMS DITA Versioning Functionality for details about other CMS dependency versioning features.
CMS 10.6.378 Alias Localization
DITA alias localization behavior differs between CMS 10.6.378 and CMS 10.6.308–10.6.342.
In CMS 10.6.308–10.6.342, you can only set one wrapper page type instance based on default DSS rendering schema for DITA content, meaning the content wrapper only returns components and other data for the default locale. For localized DITA aliases, the wrapper does not return lingually cloned content versions based on locale.
In CMS 10.6.378, you can set a wrapper page type based on any locale-specific DSS rendering schema, and aliases will accurately reflect the locale of their corresponding DITA content. DITA publishing pipeline and preview processes will render localized DITA aliases to the DSS with the appropriate expanded XML locale data.
See Rendering Localized DITA Content for more details.