OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

cmis message

[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=24892#action_24892 ] 

Martin Hermes commented on CMIS-714:
------------------------------------

Thanks for your responses. I agree, that it is a little bit unusual to have a own policy for every document. Its basically caused by the current CMIS policy API. A better solution might be to have only a policy which describes the properties of the policy, but specifying the properties when applying the policy to a document. But this would require changes in the CMIS Domain Model. As an alternative for the CMIS policy API, we might think about using Florians secondary type proposal to add the retention information to a document. What do you think about this approach?

I'd like to explain a little bit more why the Retention Policies described in Section 1 are very essential for our use cases. We have basically two scenarios where such Retention Policies are important:

1) Documents are attached to Business Objects in an ERP system. In this case the leading business object (e.g. a sales order) determines how long a document has to be kept and when it has to be deleted. 

2) The second use case is about archiving business objects from an ERP system. In this scenario, structured data from business objects are converted into documents and moved into a DMS system. Again, the retention and disposal time is calculated by the ERP system and it must be possible to pass this information to the archive system.

Today we have a dedicated interface based on WebDAV to support those scenarios. Many partners, like OpenText, EMC or IBM have implemented this proprietary interface. With CMIS we see the possibility to get rid of the proprietary interface and to avoid that DMS providers need to implement an additional interface beside CMIS.


> 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]