[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (CMIS-714) Proposal to addRetention & Legal Hold Policies for next version of spec
[ http://tools.oasis-open.org/issues/browse/CMIS-714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26792#action_26792 ]
Martin Hermes commented on CMIS-714:
------------------------------------
Update from the discussions on the TC call, August, 8th:
(1) Mass Operations for CMIS
It was decided to seperate the discussion of introducing mass operations into CMIS from the discussion about Retention and Hold Management. This makes both discussions easier and allows independent timelines for both features. Jira Issue and Proposal for Mass Operations have to be created.
(2) Using the type hierarchy to expose a file plan / classification tree
Exposing the classifications via the type hierarchy has several advantages, like
- a repository can expose property definitions for properties which are required to do the classification
- classifications can be used in queries
- no additional API required for exposing or applying a classification
So far we did not find any disadvantages of exposing the classifications via the type hierarchy.
(3) Using StartOfRetention + duration instead of expirationDate for client managed retentions
Using StartOfRetention + Duration property to manage retention times seems to be more common in Records Management than using an explicit expirationDate. On the other hand it might be usefull be able to use the expirationDate in a query. It was decided that a client should appliy a StartOfRetention property + duration, and the repository calculates the expirationDate.
(4) Assignment rule and Prolongation rule
It was decided to make those rules a SHOULD requirement
(5) Changing "Legal Hold" to "Hold"
As there can be different reasons for setting a document on hold, the term "Legal Hold" will be replaced by "Hold"
(6) Methods to apply retentions or holds
The specification should refer to the secondary type proposal to describe how retentions or holds re applied to an object
> Proposal to add Retention & Legal Hold Policies for next version of spec
> ------------------------------------------------------------------------
>
> Key: CMIS-714
> URL: http://tools.oasis-open.org/issues/browse/CMIS-714
> Project: OASIS Content Management Interoperability Services (CMIS) TC
> Issue Type: New Feature
> Components: Domain Model
> Reporter: Martin Hermes
>
> A new Draft Version 0.2 of the proposal to add Retention & Legal Hold Policies has been uploaded. Main differences to the previous version:
> - A "Managed Retention Policy" has been added to support repository-determined retention periods (Thanks to Jens)
> - Previous Retention Policy with expiration date and optional destruction date has been split into two policies: Retention Policy and Destruction Policy
> Feedback appreciated
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]