Uncategorized pages
Showing below up to 50 results starting with #251.
View (previous 50 | next 50) (20 | 50 | 100 | 250 | 500)
- 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.1 Uniquely identify each AIP
- 4.2.4.2 System of reliable linking/resolution services in order to find identified objects
- 4.2.4 Convention that generates persistent, unique identifiers for AIPs
- 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.5 Tool and resources to provide authoritative Representation Information for all objects
- 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.6 Documented processes for acquiring PDI for associated Content Information
- 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.7 Content Information is understandable for Designated Community at the time of AIP creation
- 4.2.8 Verify each AIP for completeness and correctness
- 4.2.9 Independent mechanism for verifying the integrity of the content
- 4.3.1 Documented preservation strategies relevant to its holdings
- 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.2 Mechanisms for monitoring its preservation environment
- 4.3.3.1 Mechanisms for creating, identifying or gathering any extra Representation Information required
- 4.3.3 Mechanisms to change preservation plans as a result of its monitoring activities
- 4.3.4 Provide evidence of the effectiveness of its preservation activities
- 4.4.1.1 Preserve the Content Information of AIPs
- 4.4.1.2 Actively monitor the integrity of AIPs
- 4.4.1 Specifications for how the AIPs are stored down to the bit level
- 4.4.2.1 Procedures for all actions taken on AIPs
- 4.4.2.2 Demonstrate that any actions taken on AIPs were compliant with the specification of those actions
- 4.4.2 Contemporaneous records of actions and administration processes that are relevant to storage and preservation of the AIPs
- 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.6.1.1 Log and review all access management failures and anomalies
- 4.6.1 Comply with Access Policies
- 4.6.2.1 Record and act upon problem reports about errors in data and responses from users
- 4.6.2 Follow policies and procedures that enable the dissemination of digital objects that are traceable to the originals
- 5) Infrastructure and Security Risk Management
- 5.1.1.1.1 Hardware technologies appropriate to the services it provides to its designated communities
- 5.1.1.1.2 Procedures in place to monitor and receive notifications when hardware technology changes are needed
- 5.1.1.1.3 Procedures in place to evaluate when changes are needed to current hardware
- 5.1.1.1.4 Procedures, commitment and funding to replace hardware when evaluation indicates the need to do so
- 5.1.1.1.5 Software technologies appropriate to the services it provides to its designated communities
- 5.1.1.1.6 Procedures in place to monitor and receive notifications when software changes are needed
- 5.1.1.1.7 Procedures in place to evaluate when changes are needed to current software
- 5.1.1.1.8 Procedures, commitment and funding to replace software when evaluation indicates the need to do so
- 5.1.1.1 Employ technology watches or other technology monitoring notification systems
- 5.1.1.2 Adequate hardware and software support for backup functionality sufficient for preserving the repository content and tracking repository functions
