Naming convention for file import
Filenames of the files that are imported must comply with Content Manager naming convention because some of the metadata for the new object is derived from the filename. If not named by Content Manager convention, import fails.
Filename format
Filenames of objects you want to import must have following format:
title=GUID=version=language=resolution.extension- The equal (=) character is the value separator.
- The combination of docid, version, language and resolution allows Content Manager to uniquely identify the object.
| Format | Context | Description |
|---|---|---|
| title | Mandatory. | The title of the object that is imported. |
| GUID | Mandatory when importing new versions or revisions for an (existing) object. Must match the existing object's GUID. If not provided, the system generates the GUID. | Content Manager object identifier; used to locate objects in the repository. |
| version | When no version is provided (depending your configuration), the system creates a new version if the latest available version is released otherwise it creates a new revision. | The version of the object. |
| language | When no language is provided, the language set in the UI is used. If no language is set in the UI, the default language is used. | The language of the object. |
| resolution | Mandatory. | The resolution for images, when imported. |
| extension | Mandatory. | The file extension; determines how objects are imported. File handlers can be configured for file extensions, that define how the files are imported. |
The following examples illustrate how files are imported based on file names:
- image 001=IMG001=1=en=low.gif : version 1 of the image is imported (created if IMG001 does not exist) and the gif image is imported as its low resolution rendition.
- how to log on= = = =.xml: the topic "how to log on" is created (id is an Tridion Docs generated id) and the XML is imported as its first version in the default language.
- how to log on=TASK023= = = .xml: depending on the action defined in the configuration (store or create), the latest version of the TASK023 object in the default language is updated. If this latest version is released a new version of TASK023 is created.
- how to log on=TASK023=3= = .xml: version 3 of TASK023 is updated. When version 3 is released it depends on the configured import action if version 3 is updated, version 4 is created or no action is taken at all.