Content Management Interoperability Services (CMIS) Version 1.1

cmis:secondary
cmis:rm_repMgtReten3on
FilePlanCategory1
FilePlanCategory2
FilePlanCategory1.1
FilePlanCategory1.2
FilePlanCategory2.1
FilePlanCategory2.2
Figure 2.8: Repository Managed Retentions Types
The usage of Repository Managed Retentions allows support of support advanced scenarios where the
retention period is not fixed at creation time, but managed more dynamically (e.g. depending on certain
property changes like "3 years after setting status to released"). The capabilities that are kind of rules are
supported and how they are enforced varies widely between repository implementations. Some may do this
automatically, some may require manually triggered batch runs, require an approval or workflow for certain
actions etc. This model has minimal requirements for the application but can use much of the functionality
that a repository provides.
This specification only defines the classification process, that is applying a Repository Managed Retention
to a document. Creating and managing the rules and how rules are mapped to file plan categories is outof-scope
and repository specific. Which set of Repository Managed Retentions can be assigned to which
objects is also repository specific.
Whether a user is allowed to apply a Repository Managed Retention is repository specific. If the user has
no permission to do so, a permissionDenied exception MUST be thrown. In case of others constraints,
a constraint exception MUST be thrown.
2.1.16.1.1 Repository Managed Retention Type
2.1.16.1.1.1 Attribute Values
The Repository Managed Retention object-type MUST have the following attribute values.
id
Value: cmis:rm_repMgtRetention
localName
Value:
localNamespace
Value:
queryName
Value: cmis:rm_repMgtRetention
CMIS-v1.1-csprd01
Standards Track Work Product
Copyright © OASIS Open 2012. All Rights Reserved.
18 August 2012
Page 117 of 331