In the context of CMIS, managed entities are classified as objects. CMIS defines only the following primary base object types, which are supported in edoc CMIS archivelink:
-
cmis:document: A self-contained unit of information that is referred to, for example, as a document, file, or rendition in the context of ECM and ERP systems. In CMIS, a file (document) is treated as a content stream (file content). The object type must exist in the CMIS repository.
-
cmis:folder: Is an information unit that organizes other objects into a logical structure. In the context of ECM and ERP systems, this object type is referred to as a “folder” or “file” resp. “dossier”. This object type must exist in the CMIS repository.
-
cmis:item: Is an information unit that is a generic object. The object has neither file content nor a folder structure. In the context of ECM and ERP systems, the object is typically referred to as a record. The object type is an optional component in the CMIS repository.
Secondary object type as a supplement
The base type cmis:secondary is a secondary object type (a kind of subtype) that allows you to extend an object's primary base types with additional properties.
Objects of type cmis:secondary are not standalone objects.
The following object types are used by default in edoc CMIS archivelink:
-
Document
-
Folder
-
Record
Basic information on all CMIS base object types
All object types always have a unique object type ID within a repository, as well as specific properties and functions. The properties and functions of a base object type are part of an object's type definition.
Each CMIS object type consists of general and specific properties that further classify and describe an object. The general properties are shared by all CMIS object types.
General properties include, for example, the object ID in a repository, the specific name, and an object type ID, which are used to uniquely identify the CMIS object.
In contrast, specific properties clearly describe the particular characteristics of an object—for example, whether an object is a document or a folder, whether the object can be versioned, or whether the object is read-only.
The CMIS standards are defined by OASIS. For more information, please see the website.
Specific characteristics of the “Document” object type (cmis:document)
In the context of CMIS, a document can contain one or more content streams. A content stream can be a file or a rendition (a visualization of a file’s contents). The document has its own ID, can contain specific MIME types, and can be versioned. In CMIS, a file (document) is treated as a content stream (file content).
Specific characteristics of the base object “Folder” (cmis:folder)
In the context of CMIS, a folder is the CMIS equivalent of a file in the ECM context. A folder thus represents a logical structural unit that organizes and groups other objects (documents, subfolders, records). A folder itself has no file content (content stream).
A folder structure is always organized hierarchically and has only one root. Folders and folder structures do not support versioning.
Specific characteristics of the base object “Record” (cmis:item)
In the context of CMIS, a record has neither file content (content stream) nor a structural function such as cmis:folder. The cmis:item object type is used to store any metadata as a standalone object (record, entry, or reference) in the repository.
This object type consists solely of the general CMIS properties; it has no specific properties of its own and cannot be versioned, but it can be stored in folders.
Because of these characteristics, the cmis:item object type is suitable for storing organization-specific properties using custom fields, such as contact information, addresses, etc.
See also