managing electronic records in governmental bodies - National ...
managing electronic records in governmental bodies - National ...
managing electronic records in governmental bodies - National ...
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
14<br />
4.1.5 Version control<br />
Version control is imperative. Electronic <strong>records</strong> can be located <strong>in</strong> various places at<br />
the same time e.g <strong>in</strong> a centralized database, <strong>in</strong> shared network fil<strong>in</strong>g spaces, on<br />
local hard drives and on a variety of other storage media. This makes it more difficult<br />
to manage the creation, revision and deletion of <strong>records</strong>. If the creation of <strong>records</strong> is<br />
not managed properly it can happen that someone may accidentally use the wrong<br />
version of an <strong>electronic</strong> record or that <strong>records</strong> which should have been kept are<br />
accidentally destroyed.<br />
If too many versions of a document are kept without proper version control it<br />
becomes impossible to identify the f<strong>in</strong>al version which will become the record copy.<br />
Likewise if several versions of a record are kept, it can lead to the wrong versions of<br />
<strong>records</strong> be<strong>in</strong>g used <strong>in</strong> policy decisions that could have far-reach<strong>in</strong>g legal<br />
implications.<br />
When a f<strong>in</strong>al version is declared as a record, edit<strong>in</strong>g should not be allowed. If it is<br />
necessary to create a new version of a record it should only be possible to check out<br />
a copy of the record and to create a new version with the copy. The new version<br />
should be checked back <strong>in</strong>to the repository as a new record. The l<strong>in</strong>k between the<br />
new version and the orig<strong>in</strong>al record should be ma<strong>in</strong>ta<strong>in</strong>ed especially where retention<br />
of previous versions is necessary as evidence of approval or the evolution of the<br />
document.<br />
4.1.6 Authenticity<br />
Authenticity refers to the degree of confidence that a user can have that the record<br />
that he has access to is the orig<strong>in</strong>al authentic record. Governmental <strong>bodies</strong> need to<br />
be able to prove the <strong>in</strong>tegrity of <strong>electronic</strong> record to enable them to be accountable.<br />
Information conta<strong>in</strong>ed <strong>in</strong> <strong>records</strong> is a means of ensur<strong>in</strong>g accountability and it may<br />
need to be produced as evidence <strong>in</strong> courts of law. To protect the authenticity,<br />
reliability, <strong>in</strong>tegrity, accuracy, adequacy and completeness of <strong>records</strong>, and to ensure<br />
their legal admissibility, the <strong>records</strong> must be protected aga<strong>in</strong>st alterations by<br />
users and system adm<strong>in</strong>istrators. All events that affect the reliability of <strong>records</strong><br />
must be tracked and that audit trail must be kept as an unalterable record. It is also<br />
imperative that the system logs a history of all changes that were done on a record<br />
<strong>in</strong>clud<strong>in</strong>g the date of the change and the identification of the person who has taken<br />
the action. It should log changes to the <strong>records</strong> and to the metadata to ensure that<br />
the <strong>records</strong> rema<strong>in</strong> reliable.<br />
4.1.6.1 Audit and history trail<br />
In account<strong>in</strong>g, an audit trail is the sequence of paperwork that validates or<br />
Manag<strong>in</strong>g <strong>electronic</strong> <strong>records</strong>_Policy Guidel<strong>in</strong>es.doc<br />
First Edition<br />
Version 1.1<br />
April 2003