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.
27<br />
<strong>records</strong> to capture of their websites <strong>in</strong> their specific legal, bus<strong>in</strong>ess and social<br />
context. The necessary policy requirements associated with <strong>manag<strong>in</strong>g</strong> websites<br />
should then be drafted to ensure that these <strong>records</strong> are kept. Governmental <strong>bodies</strong><br />
should document the results of the risk assessment. websites are not static;<br />
therefore the potential risk level should rout<strong>in</strong>ely be <strong>in</strong>vestigated and documented.<br />
Due to the nature of the websites it is preferable that the <strong>records</strong> are captured at the<br />
back end at the time that the <strong>records</strong> are created and posted to the website. All<br />
documents published to the website should be checked <strong>in</strong>to the <strong>electronic</strong> repository<br />
as <strong>records</strong> before be<strong>in</strong>g published to the site. The appropriate metadata for each<br />
<strong>in</strong>dividual record should be captured before it is published to the website. Metadata<br />
regard<strong>in</strong>g the post<strong>in</strong>g of the record to the website (e.g. date of post<strong>in</strong>g, format it was<br />
published <strong>in</strong>, authorizations for post<strong>in</strong>gs and removal from website) should also be<br />
captured and l<strong>in</strong>ked to the record. The website should l<strong>in</strong>k to the repository and<br />
extract its <strong>in</strong>formation from the repository. This should prevent multiple copies of the<br />
same document exist<strong>in</strong>g <strong>in</strong> various places.<br />
Extract<strong>in</strong>g a precise copy of the site to the <strong>electronic</strong> repository should create a<br />
record of the public face of the website. This should be done the first time the<br />
website becomes active and thereafter each time a change/update is done. If the<br />
website changes on a daily basis the <strong>governmental</strong> body should decide how<br />
frequently version control should be applied, tak<strong>in</strong>g <strong>in</strong>to account the specific risks<br />
that were identified dur<strong>in</strong>g the risk assessment.<br />
The l<strong>in</strong>ks <strong>in</strong> the extracted copy of the website should rema<strong>in</strong> active. If a record that<br />
was l<strong>in</strong>ked to the specific website was disposed of accord<strong>in</strong>g to a disposal authority,<br />
the l<strong>in</strong>k to the metadata of that document should be ma<strong>in</strong>ta<strong>in</strong>ed to <strong>in</strong>dicate what<br />
happened to the specific document.<br />
A historical log should be kept all actions taken on the website after it has been<br />
extracted to the <strong>electronic</strong> repository.<br />
Besides the metadata regard<strong>in</strong>g every record that is posted to the website<br />
appropriate metadata about the website itself should also be captured at the time<br />
that the website is extracted to the repository.<br />
Records of web-based activities should be extracted to the Integrated Document<br />
Management System. S<strong>in</strong>gle transactions between the website and the user should<br />
be captured at the time of the transaction. The follow<strong>in</strong>g should be captured:<br />
o Date and time of the transaction;<br />
o The IP or doma<strong>in</strong> address of the user;<br />
o The user profile;<br />
o The query or other action performed;<br />
o The resources provided to the user with the relevant metadata attached;<br />
o If an e-form was used, <strong>in</strong>formation regard<strong>in</strong>g the specific version of the e-<br />
form that was used for that specific transaction.<br />
The <strong>National</strong> Archives and Records Service does not yet have the expertise to<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