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]