Content Management Interoperability Services (CMIS) Version 1.1

2.1.16 Retentions and Holds
Retentions and Holds can be used to protect documents from being deleted or modified. A Retention describes
a period of time where the document must not be deleted, while a Hold just marks the document as
protected as long as the Hold is applied to a document.
This specification defines a basic interface for end user operations. Administrative operations such as
managing a file plan or shortening retention periods are out of scope. A repository MAY support settings
that require administrative privileges and bend the rules described in the following section. The implications
are repository specific.
Retentions and Holds can be applied to documents by applying predefined secondary types for Retentions
and Holds. CMIS specifies secondary types for:
• Repository Managed Retentions
• Client Managed Retentions (with a subtype for Destruction Retentions)
• Holds
If a repository does not support one of the predefined types for Retention and Hold management, the corresponding
secondary type MUST NOT be returned by a getTypeChildren service call.
All secondary types for retention and hold management SHOULD be able to be applied to objects derived
from the cmis:document base type. Applying such types to other CMIS objects and its behavior is repository
specific. A repository MUST throw a constraint exception if the operation is not supported.
Retentions and Holds are applied to document versions. How this affects other versions in the version series
is repository specfic.
Retentions and Holds protect at least the content of a document from modifications. If this protection also
applies to the properties, ACL, policies, relationships, etc. of a document, is repository specific. Clients may
use the Allowable Actions to discover what they can do with protected documents.
2.1.16.1 Repository Managed Retentions
Repository Managed Retentions are used in scenarios where the repository is responsible for calculating the
concrete expiration date and potential destruction date for a document. As a first step a records manager
usually creates a file plan in the repository and assigns rules which are used to calculate the retention period
for a specific entry in the file plan. Creating a file plan is out-of-scope for CMIS. It has to be done using the
native (user) interfaces of the repository. In order to enable a client to classify documents according to this
file plan, the repository exposes the file plan as a secondary type hierarchy. The CMIS client can now apply
one of the exposed file plan categories to a document. This process is called classification:
CMIS-v1.1-csprd01
Standards Track Work Product
Copyright © OASIS Open 2012. All Rights Reserved.
18 August 2012
Page 115 of 331