Building an Electronic Records Archive at the National Archives and Records Administration Recommendations for Initial Development (2003) / Chapter Skim
Currently Skimming:
7 Strategy for Evolution and Acquisition
7 Strategy for Evolution and Acquisition
Pages 62-70
The Chapter Skim interface presents what we've algorithmically identified as the most significant single chunk of text within every page in the chapter.
Select key terms on the right to highlight them within pages of the chapter.
From page 62... ...
The SDSC demonstrations successfully exploit the clear separation of the major modules of ingest, storage, and access. A modular approach presumes that each modular component will be changed several 1Consultative Committee for Space Data Systems (CCSDS)
|
From page 63... ...
To exploit modular structure for incremental evolution, it is necessary to define the software interfaces by which each module connects to other modules. These interfaces require defining subroutine cans and data types transferred between the modules.
|
From page 64... ...
Converters may be used within ingest modules to generate derived forms, or within access modules to generate the data type requested by the user or necessary for preparing a visual presentation. · Data-type checkers, which are simply a variant of data-type converters.
|
From page 65... ...
An example of a digital preservation architecture sketch in this spirit is that of the Library of Congress' National Digital Information Infrastructure Preservation Program (NDIlPP) .4 A common architecture is especially important for a complex program such as the ERA, which must unify multiple systems.
|
From page 66... ...
to interconnect hardware components. The structure of hardware components should allow flexible interconnection of hardware from various vendors using standard networking hardware and protocols- c.g., {P.5 Replacing old hardware with new, or adding hardware capacity is a matter of attaching the new hardware to the network and perhaps changing the network configuration.
|
From page 67... ...
COTS modules must be chosen carefully to be valuable to a long-lived system. COTS offerings with a large market truly common products and slowly changing specifications (perhaps today's operating systems and network-attached file systems are examples)
|
From page 68... ...
By working within a common framework, the pilot systems can, in subsequent design iterations, eventually coalesce into a smaller number of more comprehensive systems as experience and confidence grow. it is especially important that the data model the data types anct related metaclata used ~ each pilot conform to a common architecture so that the digital data obtained by ingesting records into one of the early systems will carry forward into future evolutions.8 At some system iteration it may be necessary to rebuild the archive according to a new data model Respectably if the data model is changed significantly)
|
From page 69... ...
Successfully building on the pilot experience will require skill in developing an initial architecture, managing the first system developments, learning from early operations, making revisigns to architecture and specifications, and evolving the overall program. ERA pilots should exploit available collections of records that could be organized and macle available quickly, and they should sample different dimensions of the overall archiving challenge.
|
From page 70... ...
NARA is preparing to acquire digital forms of State Department diplomatic cables, which are simple text files. One pilot might focus on preserving these cables, extracting appropriate metadata automatically from the cables, perhaps providing fulltext search, or other access appropriate to the collection.
|
Key Terms
This material may be derived from roughly machine-read images, and so is provided only to facilitate research.
More
information on Chapter Skim is available.