4.2.4.1.3 Describe any processes for changes to identifiers

Documentation shall describe any processes used for changes to such identifiers.

APTrust does not allow changes to semantic or internal identifiers, so there is no process for changing these identifiers. UUIDs assigned to objects and files for internal tracking (e.g., PREMIS events and files) are also immutable.

4.1.1 Content information and information properties
4.1.1.1 Identification of information properties
4.1.1.2 Record of content information and information properties
4.1.2 The repository shall clearly specify the information that needs to be associated with specific Content Information at the time of its deposit.
4.1.3 Recognition and parsing of SIPs
4.1.4 Verification of Producer
4.1.5 Verification of SIP
4.1.6 Control over digital objects document
4.1.7 Communication with producer/depositor
4.1.8 Acquisition records
4.2.1 Associated definition for each AIP or class of AIPs
4.2.1.1 Identify which definition applies to which AIP
4.2.1.2 Definition of each AIP
4.2.2 Description of how AIPs are constructed from SIPs
4.2.3 Document final disposition of all SIPs
4.2.3.1 Procedures if a SIP is not incorporated or discarded
4.2.4 Convention that generates persistent, unique identifiers for AIPs
4.2.4.1 Uniquely identify each AIP
4.2.4.1.1 Have unique identifiers
4.2.4.1.2 Assign and maintain persistent identifiers of the AIP and its components
4.2.4.1.3 Describe any processes for changes to identifiers
4.2.4.1.4 Provide a list of all identifiers and check for duplications
4.2.4.1.5 System of identifiers is adequate now and in the future
4.2.4.2 System of reliable linking/resolution services in order to find identified objects
4.2.5 Tool and resources to provide authoritative Representation Information for all objects
4.2.5.1 Tools or methods to identify the file types of all objects
4.2.5.2 Tools or methods to determine what Representation Information is necessary for understandability
4.2.5.3 Have access to the requisite Representation Information
4.2.5.4 Tools or methods to ensure that Representation Information is persistently associated with objects
4.2.6 Documented processes for acquiring PDI for associated Content Information
4.2.6.1 Documented processes for acquiring PDI
4.2.6.2 Execute documented processes for acquiring PDI
4.2.6.3 PDI is persistently associated with Content Information of AIP
4.2.7 Content Information is understandable for Designated Community at the time of AIP creation
4.2.7.1 Processes for testing understandability for Designated Community of the Content Information of AIPs
4.2.7.2 Execute testing process of Content Information of AIPs
4.2.7.3 Bring Content Information of AIP up to level of understandability if it fails testing
4.2.8 Verify each AIP for completeness and correctness
4.2.9 Independent mechanism for verifying the integrity of the content
4.2.10 Contemporaneous records of actions and administration processes relevant to AIP creation
4.3.1 Documented preservation strategies relevant to its holdings
4.3.2 Mechanisms for monitoring its preservation environment
4.3.2.1 Mechanisms for monitoring and notification when Representation Information is inadequate for the Designated Community to understand the data holdings
4.3.3 Mechanisms to change preservation plans as a result of its monitoring activities
4.3.3.1 Mechanisms for creating, identifying or gathering any extra Representation Information required
4.3.4 Provide evidence of the effectiveness of its preservation activities
4.4.1 Specifications for how the AIPs are stored down to the bit level
4.4.1.1 Content Information preservation
4.4.1.2 Monitoring integrity of AIPs
4.4.2 AIP storage and preservation records
4.4.2.1 AIP procedures
4.4.2.2 Compliance with specification
4.5.1 Specify minimum information requirements to enable the Designated Community to discover and identify material
4.5.2 Capture or create minimum descriptive information for each AIP
4.5.3 Create bi-directional linkages between each AIP and its descriptive information
4.5.3.1 Maintaining Associations
4.6.1 Comply with Access Policies
4.6.1.1 Log and review all access management failures and anomalies
4.6.2 Follow policies and procedures that enable the dissemination of digital objects that are traceable to the originals
4.6.2.1 Record and act upon problem reports about errors in data and responses from users

Requirement Text collapse

Evidence Provided collapse

In This Section