Storage Document Identification

Though each CMS has its own concept of a document, a version and the relationship between them, three basic attributes identifying a document are critical to proper storage:

• A GUID: Each document must have a globally unique identifier to distinguish it from other documents. For some systems, this may be supplied by the user; for others it may be generated. Note that the GUID is stored with the Oracle Transportation and Global Trade Management Cloud document record after the content is created or queried.
• A primary name: For systems supporting versioning, a document must have a primary name. Documents that share a primary name are grouped together as versions of the initial document of that name. For systems without versioning, the primary name acts as an alternate ID to identify a document when browsing or searching.
• A folder: Many content management systems support the browsing of documents via hierarchical folders. When storing content, Oracle Transportation and Global Trade Management Cloud optionally passes a folder specification to the CMS. This takes the form <parent folder>/<child folder>/…. On storage, folders and subfolders are created by the CMS to meet the folder specification and the content is stored in the last descendant on the folder branch. Note that the folder specification is optional. Documents stored without a folder are considered unfiled. Some CMS systems, however, do not support unfiled documents and a folder specification is required for storage.