Information Technology Reference
In-Depth Information
12. Store Keys, public and private
COMPONENT
:KeyStore
Public keys can be stored in any convenient
location that is accessible to users. However, for
long-term preservation these keys must be
guaranteed to be available, as must the
appropriate encryption or digest algorithm.
The same applies for private keys, which must be
held in “escrow” for some agreed period, with
adequate security.
The collection of information adequate for preservation is a key concept in OAIS - the
Archival Information Package.
13. Construct the AIP
COMPONENT
:Archival
Information Packager (see
Sect. 17.10
)
The AIP is a logical construct, and key to
preservation in the OAIS Reference Model. The
AI Packager logically binds together the
information required to preserve the Content
Information so that it is suitable for long-term
preservation. However, this should not be
regarded as a static construct, since, as has been
stressed, preservation is a dynamic process. The
AI Packager works with the Preservation
Orchestration Manager
Having the AIP, this must now be securely stored.
14. Store the AIP data object
securely for the long term.
COMPONENT
: Preservation Data
Object (PDO) (see
Sect. 17.6
)
Digital storage comes in many different forms,
and the hardware and software technology is
constantly evolving. The PDO virtualises the
storage at the level of a data object; in this way, it
extends the current virtualised storage, which
allows transparent access to distributed data. The
PDO hides the details of the storage system, the
collection management etc. - all of which can
cause a great deal of trouble when migrating, as
hardware and software technology changes.
One way of looking at this is to view it as an
implementation of the OAIS Archival Storage
functional element. As such, it allows the
development of a market of interchangeable
“Archival Storage” elements for a variety of
archives.
Now we come to the period when the data object is stored for many years - in principle
indefinitely.
During this time the originators of the data pass away; hardware and software become
obsolete and are replaced; the organisation that hosts the repository evolves, merges, perhaps
terminates (but hands on its data holdings); the community of users, their tools, their
underlying Knowledge Base change out of all recognition.
In the background, something must keep the information alive, in the same way as the body's
autonomic nervous system keeps the body alive, namely by triggering breathing, heartbeat
etc. Note that the autonomic nervous system does not actually do the breathing etc., but
provides the trigger. This is what must be arranged.
