Before you can import content into Content Manager, you need to convert it. In this operation, the values for direct addresses are converted into GUIDs, DITA conditional-processing attributes are converted to Content Manager conditions, and the filemap.xml file is generated.
Before you begin
- Create input and output directories on the system on which Content Importer is installed.
- If you want to add additional metadata to the filemap.xml file that is generated by the conversion operation, develop an XSL override file. The ContentImporter.xsl file is provided as an example; you can use it as a starting point.
Procedure
- In the Conversion input field, specify the folder that contains the source files that you want to prepare for import.
You must have write permissions to the folder.
- In the Language field, specify the language for the files that you want to import.
- Optional: Select the force re-GUID-izing check box if you want new GUIDs to be generated.
By default, Content Importer uses existing GUIDs if they are present in a filemap.xml file, a .met file, or the file name of an object.
- In the Default resolution field, specify the resolution for the image files.
- Optional: To run an XSL file after conversion, select the Post conversion XSL check box, and specify the fully qualified name of the XSL file.
- In the CMS base folder path field, specify the Content Manager folder into which the content will be imported.
This folder does not need to exist. If it does not exist, it will be created when the content is uploaded.
- In the Conversion output / Import input folder field, type the directory to which the prepared files are written.
You must have write permissions to the folder.
- Click Next.
Results
A window opens and the results of the operation are displayed. Errors are highlighted in red. You can aggregate the errors by clicking the Error description field.
The following files are written to the input and output directories.
| Directory | Files |
|---|
| Conversion input directory |
|
|---|
| Conversion log directory |
- DITA2Trisoft_ProcessLog.log
|
|---|
| Conversion output directory |
- filemap.xml
- (If you ran an XSL script) filemap_pre_custom_xsl.xml
|
|---|
The
filemap_pre_custom_xsl.xml is a copy of the
filemap.xml that was produced before the custom XSL file was run; it is identical to the
filemap.xml file that is located in the conversion input directory. The
filemap.xml file that is located in the conversion output directory has been modified by the custom XSL file.
What to do next
If the conversion operation generated errors, correct the problems and run the conversion operation again. If the conversion operation did not generate errors, you now can import the content.