Documentation Center

Running a standard import

Import content, DITA or otherwise, with or without pre-existing metadata. The conversion phase creates the required metadata, then the objects are imported in the specified Repository folders.

About this task

This type of import can be used for DITA content as well as any other type of content: PDF, Word, CHM, HTML, etc.

Procedure

  1. Start Content Importer.
    Content Importer opens with the same account as the one you currently use for the other client tools, such as Publication Manager.
  2. In the Source content folder field, specify the path to the folder where your original content is located. You must have write permission to the folder. In case there are any artifact files left in the folder after previous import, a message with the option to delete these files appears.
  3. In the Conversion folder field, specify the path to the folder where the converted content must be copied. You must have write permission to the folder. This content is the result of the conversion phase. Content Importer imports the content from that folder into the Repository. In case there are any artifact files left in the folder after previous import, a message with the option to delete these files appears.
  4. In the Target Repository folder field, specify the path to the Repository folder where your content must be imported. If the path does not exist in the Repository, it will be created by Content Importer.
  5. Under the Target Repository folder field, make sure the checkbox is checked if you don't want the import to stop after the conversion phase and wait for user confirmation. If you want the import to stop after conversion, uncheck the checkbox.
  6. In the XSL file location field, specify the path to a XSL file, if you want to add extra processing to the generated content's metadata before it is copied to your conversion folder.
  7. Set the Default language for the files that you want to import. This is needed only if it is not already defined in the object's metadata.
  8. Set the Default resolution for your image files. This is needed only if it is not already defined in the object's metadata.
  9. In the Resolution map, check that the correct pairing between image file format and resolution value is made. To change an existing entry, you need to select it, Remove it and Add it again with the appropriate combination.
  10. Check the Generate new identifiers checkbox if you need to replace existing identifiers from your original content by new ones (the object identifiers used by Content Manager are the ones that start with GUID). By default, Content Importer uses existing identifiers if they are present a .3sish file, or the file name of an object.

    The Generate new identifiers checkbox can be left unchecked if your original content doesn't have identifiers: identifiers are generated anyway if none are found.

  11. Check the Use file names for titles checkbox if you want your source content file names to become the object names in the Repository. If the checkbox is left unchecked, Content Importer uses the value of the <title> element.
  12. Select Convert and import to proceed to the content import.
    The conversion information and then import information is displayed: progression information and errors (if any).

Results

.3sish and filemap.xml files are created in the conversion folder during conversion. The .3sish files are used to add the appropriate metadata to your imported content. The filemap.xml file is used to map file paths to identifiers in the Repository when resolving links. Then the objects (content and metadata) are imported in the Repository.

If any error appear after the conversion phase, you need to fix your original content and then run the conversion phase again in order to import the files that caused the errors.