Sarah, 

You bring up a very interesting topic.  I am not sure that such a system 
is even possible from a practical perspective.  You can use SharePoint to 
manage only records if you wish and workflow's within SharePoint to manage 
your event driven retention, but I am not sure of the user acceptance of 
what you are proposing.  You are essentially telling employees, if you act 
on your information I will manage and dispose of it in accordance to 
company retention policies, if you do nothing your data will live forever 
untouched.  This is a frequent conversation that I have with colleagues. 
It is possible that ERM can exist without ECM, but you must have a very 
strong audit program with real consequences for users who violate policy. 
Of course if you are implementing this is in a small organization or at a 
departmental level the level of visibility for abuse is much higher and 
your plan could be more successful.  The larger the deployment is though, 
the more diluted the oversight becomes and that is when you can run into 
issues.


Josh Hargrafen 



From:   Sarah Wagner <[log in to unmask]>
To:     [log in to unmask]
Date:   12/20/2011 10:06 AM
Subject:        Re: Electronic Records Management Systems
Sent by:        Records Management Program <[log in to unmask]>



It wouldn't necessarily need to keep the creation or last modified date
from the native born system, but at least be able to have an index field
that the record creator/uploader could input for the date of the record,
such as an obsolete date for a standard operating procedure, which prompts
the retention time to start ticking, rather than the date the record is
uploaded, which could be 1 or 2 years after the record is obsolete.

On Tue, Dec 20, 2011 at 10:43 AM, Molly Kitchen 
<[log in to unmask]>wrote:

> "We are not looking for content management, but an electronic records
> management system to manage born-digital inactive records.  It should
> have a chain of custody, a good method for managing the retention time 
of
> records based on the date of the record, not just when you upload the
> record. "
>
>
> It sounds like you want a system that keeps the "create date" or "last
> modified
> date" of the native born system to remain as your retention trigger date
> and
> you don't want to this trigger date to be modifed when migrating to an
> ERMS.
> I don't think your going to find an out of the box solution to this 
issue.
>
> List archives at http://lists.ufl.edu/archives/recmgmt-l.html
> Contact [log in to unmask] for assistance
> To unsubscribe from this list, click the below link. If not already
> present, place UNSUBSCRIBE RECMGMT-L or UNSUB RECMGMT-L in the body of 
the
> message.
> mailto:[log in to unmask]
>

List archives at http://lists.ufl.edu/archives/recmgmt-l.html
Contact [log in to unmask] for assistance
To unsubscribe from this list, click the below link. If not already 
present, place UNSUBSCRIBE RECMGMT-L or UNSUB RECMGMT-L in the body of the 
message.
mailto:[log in to unmask]



List archives at http://lists.ufl.edu/archives/recmgmt-l.html
Contact [log in to unmask] for assistance
To unsubscribe from this list, click the below link. If not already present, place UNSUBSCRIBE RECMGMT-L or UNSUB RECMGMT-L in the body of the message.
mailto:[log in to unmask]