A user guide for information architects using IXIA CCMS 7.0 with the the IXIA Dynamic Release Management (DRM) module. It contains information to work with branches and setup the information architecture for documentation in a DRM deployment of IXIA CCMS.
The IXIA Dynamic Release Management (DRM) module allows technical publication teams to easily manage the documentation for multiple products across multiple release cycles.
The DITA perspective is the default working environment for IXIA CCMS.
The IXIA Dynamic Release Management view lists the products, libraries, releases, and versions that are configured for your deployment.
The Information view shows all the DRM versions for the selected object.
When you create a product, library, release, or version, IXIA CCMS creates an XML file that defines that product, library, release, or version.
Before writers can add objects (maps, topics, images, resources) to IXIA CCMS, the documentation structure must be set up.
You can change a product or library's DRM version name to a new unique name.
You clone a version when you want to use the content of a version as a starting point for the next version.
If all of the work for one version is complete, you can close the version. This prevents anyone from accidentally creating or changing content for that version.
You can reopen any version that is closed If you need to change the content in it.
In the IXIA Dynamic Release Management module, IXIA CCMS Web automatically forks in some situations so that users do not need to decide whether to fork or edit.
You can edit libraries or their dependencies if the organization or structure of your libraries needs to change.
The Locate Containers feature is used to find the container and container parts associated to a version.
You can change a product into a library or a library into a product using Refactor.
You can export the Dynamic Release Management tree view to a tab-separated-value (TSV) file.
A version tag is an object that captures the contents of a product version or library version at a particular point in time. It is like a snapshot for an entire version.
The following section examines how Content Level Security works with content defined within the IXIA Dynamic Release Management environment.
When the documentation structure is set up, writers can add content to versions.
