System of identifiers is adequate now and in the future

From CLOCKSS Trusted Digital Repository Documents
Jump to: navigation, search - The system of identifiers shall be adequate to fit the repository’s current and foreseeable future requirements such as numbers of objects.

The CLOCKSS archive has a single class of AIP, called an Archival Unit (AU), documented in Definition of AIP. Part of that documentation describes the Reference information that forms part of the Preservation Description Information (PDI) of an AIP (AU):

  • Context: the context information for an AU consists of:
    • The plugin ID, which is the encoded name of a Java class implementing the LOCKSS plugin interface.
    • The parameters, which are a set of {name, value} pairs providing the arguments needed to construct an instance of the class named by the plugin ID.
    In effect, the context for the AU is a customized instance of a Java class, normally referred to as its plugin. It is thus executable, capable of performing operations on the AU such as adding content and metadata from a SIP (see below), extracting metadata, and taking part in integrity checks.


  • Reference: Each AU has an immutable internal name, computed from its context information and stored with it. The software locates it in the POSIX filesystems using a map from this internal name to the path to the AU's root directory which is built during system startup and subsequently maintained as new AUs are created. Content within an AU can be located by querying the metadata database using specific bibliographic metadata fields to match against the bibliographic metadata supplied by the publisher or derived from the AU's context.

Both the Java class name space and the set of parameter names and values are unlimited, and thus the supply of AU identifiers is unlimited.

Relevant Documents

  1. Definition of AIP
  2. LOCKSS: Extracting Bibliographic Metadata
  3. LOCKSS: Metadata Database