Describe any processes for changes to identifiers

From aptrust
Jump to: navigation, search

Documentation shall describe any processes used for changes to such identifiers. Describe any processes for changes to identifiers
Status Ready for review
Compliance Rating Fully compliant

Supporting Text

This is necessary in order to ensure that each AIP can be unambiguously found in the future. This is also necessary to ensure that each AIP can be distinguished from all other AIPs in the repository.

Examples for Meeting the Requirements

Documentation describing naming convention and physical evidence of its application (e.g., logs).


A repository needs to ensure that there is in place an accepted, standard naming convention that identifies its materials uniquely and persistently for use both in and outside the repository. The ‘visibility’ requirement here means ‘visible’ to repository managers and auditors. It does not imply that these unique identifiers need to be visible to end users or that they serve as the primary means of access to digital objects. Ideally, the unique ID lives as long as the AIP; if it does not, there must be traceability. Subsection 4.2.1 requires that the components of an AIP be suitably bound and identified for long-term management, but places no restrictions on how AIPs are identified with files. Thus, in the general case, an AIP may be distributed over many files, or a single file may contain more than one AIP. Therefore identifiers and filenames may not necessarily correspond to each other. Documentation must represent these relationships.

Evidence Provided

APTrust does not allow for changes to sematic identifiers so there is no process for changes to semantic identifiers.

UUID is an internal identifier and in a few cases it can change, but it does not affect depositors. Refer back to 4.2.4 and see Bagging specifications#How Bag Names Become Object Names for additional information.


Ready for Review

Compliance Rating

Fully compliant