It is important to define appropriate transfer requirements for electronic records. Ultimately responsibility for the long-term preservation of electronic records of permanent value should fall within the statutory remit of the records and archives institution. However, this can be achieved by transferring custody to the archival institution or by designating other agencies as places of deposit.
The advantages and disadvantages of custodial and non-custodial strategies are discussed in Lesson 3.
Formats
Which formats are acceptable for transfer and which are not? The archival institution should specify what formats are acceptable for transfer. Records professionals must make decisions about access and preservation formats for all types of records (for example, deciding to microfilm or digitise paper records and so on).
It is easy to confuse access and preservation formats when dealing with electronic records as both formats will be in electronic form. This will require careful consideration of the different types of electronic files (such as word-processed documents, database files, spreadsheets and so on). In short, an archival institution can choose to
-
accept a wide variety of file formats and then convert the files into the accepted archival preservation formats
or
-
require the records creators to provide the electronic files for transfer in specified preservation formats.
If the original custodian of the records cannot provide the data file in a standard format, additional processing may be required to convert it to an acceptable format for preservation and distribution. Often reformatting involves only simple processing routines such as removing labels from labelled tapes, changing the recording density or converting the character code. In some cases, however, the records staff member may need technical assistance to convert a data set to a standard format.
The best way to determine the appropriate preservation format for electronic files is to
-
understand the legal environment (the legal admissibility of electronic records, the status of electronic records in the accepted definition of a record in the environment and so on)
and
-
experiment with what happens when files are converted to various preservation formats.
The archival institution should specify what formats are acceptable for transfer.
Documentation
What kind of documentation is expected or required? Records managers should maintain the documentation needed to plan, develop, operate and use machine readable records and automated systems. This documentation should explain the arrangement, contents and coding of information in a machine-readable file. Two common elements of documentation are described below.
-
A diagram or list of record layout/file layout/file description/data dictionary: This document records the contents of the electronic records by describing each item of information in each field (such as the length, type and position of each field and the relationship between files).
-
A codebook: This provides an explanation of the codes used to represent information in abbreviated form.
Documentation is not standard and cannot be universally defined. Good documentation should allow the user to read, understand and use the electronic records it describes. For example, users of electronic records need to know how the information in the records was collected, entered and processed. Assembling this documentation should be a regular records management routine.
Documentation at the time of transfer must be adequate not only for the immediate use of the records but also for use over time. The documentation required for reference use can be quite minimal when the records are current and the software in which it was created is widely available. The documentation for long-term preservation should be much more extensive, and there is much to be said for gathering all the information available.
If the records programme receives and must accept electronic files that are not well documented, the transferring department should complete a transfer form. This will help in collecting precise technical specifications, including the following.
-
Record length.
-
Exact record count. There should be an exact count of the number of electronic records in a file.
-
Character code. This code represents alphanumeric data in binary form.
-
Block size. A block is a section of recorded information on a magnetic tape or disk, separated from other blocks by a small area of non-recorded tape or disk, often called the inter-record gap or IRG. One block may contain many electronic records or one electronic record may extend over several blocks, depending on size, hardware used and the programmer’s decision.
-
Type of label. A label is an identifier that provides information about a file, magnetic tape or direct access device. There are two types of labels: external labels identify the physical medium and are used to locate magnetic tapes, diskettes, etc. Internal labels are written in computerised form at the beginning and/or end of a file or volume and provide information that identifies the file(s) or records stored on the device.
-
Number of tracks. A track is one of seven or nine parallel rows of bits along the length of a magnetic tape or one of a series of concentric circles on a magnetic disk or diskette where data are recorded.
-
Density. This is the number of bits recorded in a single linear track on a magnetic tape or disk, notated in bits per inch [bpi], characters per inch [cpi] or frames per inch [fpi].
-
Parity. This is the means of verifying recorded data and detecting errors using binary calculation as a means of identifying data loss.
-
File structure. This file structure is the way in which a particular file is organised. A file has a rectangular file structure if it contains data on only one observation or unit of analysis. The file structure is hierarchical if each electronic record contains data on more than one unit of analysis.
-
Hardware used.
A transmittal form is useful for gathering this information, obtaining the necessary authorisations for the release of electronic data/records and keeping records of the transfer. The following is an example of a data file transfer/electronic records form.
Records managers should maintain the documentation needed to plan, develop, operate and use machine-readable records and automated systems.
DATA FILE TRANSFER/ELECTRONIC RECORDS
-
Complete one form for each file on tape.
-
Distribute the copies of this form as denoted below.
-
Blank forms are available from the National Archives.
|
Agency:
|
Records Disposal Authorisation/Schedule Number:
|
Division:
|
File Name (Series Title):
|
Transferred by:
|
System Name:
|
Phone Number:
|
Dates or Years of Records:
|
Transfer Date:
|
Transfer Approved By:
|
|
This file is written on tape number(s) (external label):
|
This file was computer generated on:
|
Date file was created:
|
File is number ___________________________ of __________________________ files on this reel of tape.
Number of electronic records: ___________________________________________________________________
Length of longest electronic record is _______________________________________________ characters.
Number of blocks: ____________________________________________________________________________
Blocking factor is __________________________________________________ electronic records per block.
Block size is ___________________________________________________________________ characters.
Number of characters in last block is ______________________________________________________________.
|
MODE
|
TRACK
|
PARITY
|
DENSITY
|
LABEL
|
BCD
|
7
|
Even
|
556
|
None
|
EBCDIC
|
9
|
Odd
|
800
|
IBM
|
ASCII
|
|
|
1600
|
ANSI
|
FIELDATA
|
|
|
6250
|
Other
|
Other
|
|
|
|
|
Comments:
|
Copy to: 1) National Archives; 2) Data Processing/Operations; 3) User/Custodian of Records; 4) Records Officer
|
Figure 12: Example of Data File Transfer/Electronic Records Form
Adapted from Hedstrom. Archives & Manuscripts: Machine-Readable Records, p. 47.
Share with your friends: |