Content-Type: |
text/plain; charset=UTF-8 |
Sender: |
|
Subject: |
|
From: |
|
Date: |
Thu, 23 Oct 2014 11:53:45 -0700 |
In-Reply-To: |
|
MIME-Version: |
1.0 |
Reply-To: |
|
Parts/Attachments: |
|
|
On Thu, Oct 23, 2014 at 10:16 AM, Gary Link <[log in to unmask]> wrote:
> My system as envisioned would not rely on a preset role and folder
> structure at all. The folders would be created when the task is created.
> It would receive the record series code assigned to the function it was
> created under.
Interesting concept, but "tasks" or "projects" often contain a variety of
records associated with a wide range of record series, so how would it
differentiate between these?
Correspondence, environmental, procurement, logistics, facilities, etc all
have different requirements and record series (and sub-series), with
differing retentions. And how would you apply legal holds or destruction
moratoriums when needed?
I think it might be a simple "solution" that results in even greater
challenges down the road.
--
Larry
[log in to unmask]
*----Lawrence J. MedinaDanville, CARIM Professional since 1972*
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]
|
|
|