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: Comments on Records Management proposal


Hi,

 

a few comments on the records management page:

 

1.       It is very hard to find the page on the wiki. Could this be somehow linked to the wiki home page? http://wiki.oasis-open.org/cmis/Retention_Proposal

2.       We have a specification proposal but to me it is unclear what we want to achieve with this proposal. I think we need to start first discussing what our goal should be with such a proposal. Is it just about retention management (meaning prevent deletion in a certain period of time and/or get rid of information after a certain period of time) or is it about records management (related but not the same). The proposal is about retention management plus a single concept (Hold) that has its origin in the DoD model. Why exactly this subset? What about other important concepts like for example “Mark official”?

3.       Do we want to expose details like the exact retention date as part of the standard? Isn’t this more part of the administrative part of a repository?

4.       Do we want to deal with specific common records management standards like DoD or MoReq or do we just want to have some common high-level functionality?

5.       Do we want to deal with dispositions?

6.       Do we need propagation rules like inheriting retention periods, holds etc. on folders or subtypes. Wouldn’t it be useful to have a feature on a type definition level that objects of this type are always under a certain kind of retention?

7.       Do we need enhancements in other areas like for example dealing with updates on millions of records.

8.       I assume that the RM feature set is somehow optional. Given that a repository supports the RM feature what can a client expect? One example would be that you can build a DoD certifiable application with such a repository. I would like to start the discussion on that level.

 

So what would typical use cases be that this part of the standard should cover and what are related RM standards that we need to consider? Does it make sense to follow the DoD model perhaps?

 

Jens

 



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]