Login
Home CMS Documentation Home CMS 10 DITA Processing Pipeline Authoring and Editing DITA Content Oxygen Desktop Plugin Oxygen Desktop Plugin Authoring and Editing Creating DITA Content

Creating DITA Content

Prerequisites: Users must have permissions to create assets in the CMS Assets Manager. See Creating Groups for details to set permissions.
Users can directly create CMS DITA content based on templates in Oxygen XML Editor.

For example, users can choose from prebuilt Oxygen XML Editor templates or select their own custom templates to create specific DITA topic types or maps. The system stores new content in the CMS Assets Manager.

Keep in mind that the CMS system administrator sets the CustomTemplatesOnly key to true, then operating users only have access to custom templates and not Oxygen XML Editor's prebuilt templates for document creation. For custom template setup details, see Installing CMS 10.6 Oxygen Web Service or Installing CMS 10.3–10.5 Oxygen Web Service.

Warning
Do not use tools outside of the Ingeniux CMS Browser tab to create CMS DITA content in the Oxygen XML Editor UI. These tools throw errors in the Oxygen Desktop Plugin. If you use outside tools, then restart the Oxygen XML Editor application to clear the errors.
To create CMS DITA content via the Oxygen Desktop Plugin:
  1. Open the Oxygen XML Editor application.
  2. Navigate to the folder that will contain the new content item in the Ingeniux CMS Browser tab tree structure.

    Create Document

  3. Right-click the folder, and click Create Document (or press CTRL+Shift+D).
    The Choose Template to Create Document From dialog displays.

    Choose Template to Create Document From Dialog

  4. Select a template for the new content item.
  5. Click Choose Template.
    The Document Name and Extension dialog displays.

    Specify Name and Extension of the Document to Create Dialog

  6. Enter the name of the new content item in the text field, and click Create Document.
    The Oxygen Desktop Plugin creates the content item based on the template, stores the content item in the CMS Assets Manager, assigns the asset an ID, and checks out the item to you.