Mime-Version: |
1.0 |
Sender: |
|
Subject: |
|
From: |
|
Date: |
Thu, 13 Apr 2017 09:46:12 -0400 |
Content-Transfer-Encoding: |
8bit |
Content-Type: |
text/plain; charset="utf-8" |
Reply-To: |
|
Parts/Attachments: |
|
|
What makes data disposition more difficult than content disposition is that
in many (perhaps most) databases it is impossible to identify and then
delete discrete records. There are extremely complex relationships
between the various tables, and by deleting data in one table it can affect
related tables and corrupt your data. Some systems are built to manage
that, which helps - it's important to check on these things in the RFP stage
when purchasing new software if you have that opportunity.
Otherwise it means dispositioning the system as whole, which results in the
retention of some data for far longer than the requirements of the retention
schedule. Given that you're caught in a catch-22, capture the process in
an approved policy or procedure to justify the action.
Wayne Hoff, CRM, IGP
Calgary, AB
Views expressed are my own and not my employer's.
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]
|
|
|