1. Introduction
This document sets out the requirements for depositors to National Records of Scotland (NRS) who meet the following criteria:
- Have analogue records which have been selected, or will likely be selected, for permanent preservation by NRS;
- Who intend to change the format of those selected records from analogue to digital, via a digitisation process (e.g. scanning), and;
- Who intend to submit these records to NRS in their newly digitised form, in place of their original analogue equivalents.
The requirements below are to be reviewed in parallel to our ‘Depositor Guidance for the Transfer of Archival Born Digital Records’, which outlines essential requirements for preparation and process for transfer.
2. Digitisation and NRS
It is the responsibility of the record creator and/or depositor to decide what format a record is kept in while it is in their custody, and under their management. This may include the decision to digitise analogue records and destroy the original versions, should that depositor determine that managing their records in digital formats would be more straightforward, efficient and/or cost effective than managing analogue records.
However, depositors responsible for public records must ensure these are managed in accordance with their statutory obligations. In particular, public authorities subject to the Public Records (Scotland) Act 2011 ('PRSA') must ensure that all arrangements for their public records meet the terms of their agreed Records Management Plan.
Any digitised records to be submitted to NRS for permanent preservation must be transferred with documented assurance that the digitisation process did in no way impact the integrity, authenticity and usability of the archival records.
NRS asserts a right of refusal for records which have been digitised in a manner which affects their integrity, authenticity and/or usability. For more information on these characteristics, see Glossary and the NRS Digital Preservation Policy.
3. Preparation
3.1. Legal Basis and Security
NRS cannot provide assurance that records created through digitisation projects are legally admissible in their new digital format. The responsibility to confirm this lies with the depositor considering digitisation.
For this reason, advice must be sought from your own information governance team to determine any legal blockers that would prevent digitisation before the digitisation project begins. This is particularly relevant where records may need to be presented in court, and you may be required to provide further assurances of competent processing than those described in this document (see note on BS 10008 below).
It will also be necessary to consider cyber security risks when establishing a digitisation project, to ensure digital images are stored securely prior to transfer to NRS. We, therefore, strongly recommend advice is sought from cyber security professionals. While some preservation risks are reduced in the transition from analogue to digital (physical security, fire, weather damage), having records stored digitally will open the records to a new set of cyber security risks.
3.2. Engagement
NRS depositors considering digitising records which will, or could be, transferred to NRS for permanent preservation must contact us as early as possible in this process. This will allow us to advise you on the requirements outlined in this document and work through any questions or issues that you may have. Contact should be made via your archive contact or via digital_records@nrscotland.gov.uk if you do not have an archive contact.
It is also necessary for depositors to agree arrangements for transfers to NRS. This includes notifying NRS of the intended size of the digital image transfers (in estimated bytes and number of objects) in advance, and informing us of requirements for access following transfer. We will work with you to determine timeframes and expectations for transfer processes.
NRS cannot provide assurance on commercial suppliers for digitisation, but we are able to contribute to non-commercially sensitive discussions with your suppliers to ensure our requirements are understood and established within their processes.
Where possible, NRS can support peer learning with other depositors who are conducting digitisation projects, so that you can benefit from shared experiences.
3.3. Research
The requirements outlined in this document should be seen as the minimum required to provide assurance of competent processing for digitisation that is expected for submission to NRS.
You may wish to further research digitisation processing for preservation, and we recommend the following resources:
- BS 10008 Evidential weight and legal admissibility of electronically stored information (ESI)
- This is the core standard in preserving integrity, authenticity and usability of digitised records. We would strongly recommend alignment to this standard as far as possible, with particular focus on Annex E Preparation of paper documents.
- ISO/TR 13028 Information and documentation – Implementation guidelines for digitization of records
You may also wish to review the following guidance from archival institutions with similar requirements to NRS:
5. Metadata requirements
5.1. Table A: Technical Metadata
Name
|
Description
|
Unique Identifier
|
Recommend using Version 4 UUID.
|
File Path
|
Full folder pathway of each file to be transferred.
|
File Name
|
Including extension.
|
Size
|
Bytes.
|
Folder Reference
|
As reflected in physical folder.
|
Box Reference
|
As reflected in physical box.
|
Other structural references
|
e.g series reference, shelf reference, room reference.
|
Checksum
|
MD5 Hash.
|
Operator Code
|
Code for operator who scanned image (do not send personal data).
|
Scanner Code
|
Identifier for device used.
|
Scan date and time
|
ISO 8601 Date Format (YYYY-MM-DD hh:mm:ss).
|
Image resolution
|
PPI.
|
Errors
|
Note where placeholders have been added if page damaged or unable to obtain clear scan.
|
Comments
|
Optional field to note any additional notes from the operator.
|
5.2. Table B: Quality Assurance Metadata
Name
|
Description
|
Unique Identifier
|
Recommend using Version 4 UUID.
|
Check date and time
|
ISO 8601 Date Format (YYYY-MM-DD hh:mm:ss).
|
QA Operator Code
|
Code for operator who checked image against analogue record (do not send personal data).
|
Image validation check
|
Image accessible and not corrupted Y/N.
|
Image order check
|
Image appears in same position as analogue folder Y/N.
|
Image quality check
|
Image is as legible as analogue record Y/N.
|
Errors
|
Description of error if applicable.
|
Number of attempts
|
Number of attempts to have image meet quality assurance checks.
|
Supervisor Code
|
Code for supervisor who approved quality assurance steps (do not send personal data).
|
Supervisor approval date and time
|
ISO 8601 Date Format (YYYY-MM-DD hh:mm:ss).
|
5.3. Table C: Descriptive Metadata
Name
|
Description
|
Unique Identifier
|
Recommend using Version 4 UUID.
|
Additional fields
|
Additional fields will be determined by NRS and depositor (context specific).
|
5.4. Table D: Transfer Manifest
You will note some repetition between the manifest file and the technical metadata requirements. This will ultimately lead to the generation of two separate csv files: one containing technical metadata produced during scanning, the other containing the transfer manifest produced immediately prior to transfer to NRS. The purpose of this separation is to:
- Be able to confirm that the images have not been inadvertently altered in the time between production and archiving.
- Be able to produce an accurate pathway that can be used for verification.
- Be able to produce a manifest file with consistent fields that can be efficiently utilised during NRS’s ingest processes.
- Be able to record up-to-date information regarding the closure status of the images to be sent.
The manifest file will be assembled ‘fresh’ immediately prior to transfer using the instructions from our Depositor Guidance. DROID software can be used to produce this, or the below minimum metadata fields can be assembled manually. Further instructions can be found in the Depositor Guidance.
Name
|
Description
|
FILE_PATH
|
Full folder pathway of each object to be transferred.
|
NAME
|
Including extension.
|
SIZE
|
Bytes.
|
LAST_MODIFIED
|
ISO 8601 Date Format (YYYY-MM-DD hh:mm:ss).
|
MD5_HASH
|
MD5 Checksum.
|
ACCESS_STATUS
|
CLOSED/OPEN
Whether or not the records will be open to public access from receipt by NRS.
|
ACCESS_CONDITIONS
|
If ACCESS_STATUS ‘CLOSED’, mandatory field.
If ACCESS_STATUS ‘OPEN’, complete as N/A.
The reason why records are not open to public.
|
OPEN_FROM
|
If ACCESS_STATUS ‘CLOSED’, mandatory field.
If ACCESS_STATUS ‘OPEN’, complete as N/A.
Date that the closure ends. ISO 8601 Date Format (YYYY-MM-DD hh:mm:ss).
|
RIGHTS
|
Field to outline any copyright restrictions.
|
IDENTIFIER
|
Unique identifier applied during scanning.
|
5.5. Table E: Example Transfer Package
You can view this image in the attached Word document.