Guidelines for Data
Before you upload content to SDL LiveContent Reach, check that your data meets these guidelines to ensure a smooth upload process.
Procedure
- XML files (topics, DITA maps, and so on) must use PUBLIC identifiers.
- You must use PUBLIC identifiers when identifying DTDs and ENTITY files.
- Each XML file should have a unique ID attribute on the root element (for example,
<task id="T5690">). If you upload multiple XML files that have the same ID, the last one uploaded overwrites any previous version.Note: Per the DITA standard, your topics must have a unique ID attribute, but your DITA maps do not require an ID attribute. When you upload a file, it will be stored in the database by its ID attribute. If no ID attribute is present, it is stored in the database by its filename. Therefore, if you upload multiple files with the same ID attribute, they will overwrite each other. Alternatively, if you upload multiple files with no ID attribute and the same filename, they will overwrite each other. However, if your files contain a proper unique ID attribute, you can upload multiple files the same filename, and they will be stored in the database by ID, and therefore no overwriting will occur. - To refer to objects in a digital asset management system (DAM), specify the scope as external, as in this example:
Specifying the<object src="http://digital-desert.com/mpg-videos/c425v.mpg"> <param name="scope" value="external"/> </object>valueattribute as external ensures that SDL LiveContent Reach seeks the media file at the URL rather than within its own database.