Popular pages
Showing below up to 39 results starting with #101.
View (previous 50 | next 50) (20 | 50 | 100 | 250 | 500)
- 4.2.3.1 Procedures if a SIP is not incorporated or discarded (2,214 views)
- 5.1.1.1.2 Procedures in place to monitor and receive notifications when hardware technology changes are needed (2,207 views)
- 5.1.1.1 Employ technology watches or other technology monitoring notification systems (2,204 views)
- 4.1.8 Records of actions and processes related to acquisition (2,201 views)
- 4.3.3.1 Mechanisms for creating, identifying or gathering any extra Representation Information required (2,201 views)
- 4.2.7.3 Bring Content Information of AIP up to level of understandability if it fails testing (2,200 views)
- 4.2.8 Verify each AIP for completeness and correctness (2,200 views)
- 4.2.4.1.4 Provide a list of all identifiers and check for duplications (2,199 views)
- 4.2.2 Description of how AIPs are constructed from SIPs (2,195 views)
- 4.2.5.2 Tools or methods to determine what Representation Information is necessary for understandability (2,194 views)
- 4.2.5 Tool and resources to provide authoritative Representation Information for all objects (2,191 views)
- 5.1.1.1.6 Procedures in place to monitor and receive notifications when software changes are needed (2,191 views)
- 5.1.1.1.4 Procedures, commitment and funding to replace hardware when evaluation indicates the need to do so (2,183 views)
- 5.2.2 Implemented controls to adequately address each of the defined security risks (2,178 views)
- 4.5.1 Specify minimum information requirements to enable the Designated Community to discover and identify material (2,176 views)
- 4.2.5.3 Have access to the requisite Representation Information (2,168 views)
- 5.1.1.1.8 Procedures, commitment and funding to replace software when evaluation indicates the need to do so (2,164 views)
- 4.3.3 Mechanisms to change preservation plans as a result of its monitoring activities (2,163 views)
- 5.1.1.1.3 Procedures in place to evaluate when changes are needed to current hardware (2,163 views)
- 4.2.4.1.2 Assign and maintain persistent identifiers of the AIP and its components (2,159 views)
- 5.1.1.6.2 Process for testing and evaluating the effect of changes to the repository's critical processes (2,156 views)
- 4.2.4.1.3 Describe any processes for changes to identifiers (2,150 views)
- 4.3.2 Mechanisms for monitoring its preservation environment (2,146 views)
- 5.2.1 Maintain a systematic analysis of security risk factors associated with data, systems, personnel, and physical plant (2,144 views)
- 4.4.2 Contemporaneous records of actions and administration processes that are relevant to storage and preservation of the AIPs (2,140 views)
- 4.3.2.1 Mechanisms for monitoring and notification when Representation Information is inadequate for the Designated Community to understand the data holdings (2,137 views)
- 4.1.1.1 Procedures for identifying information properties that we will preserve (2,136 views)
- 4.1.1.2 Record of content information and information properties that we will preserve (2,133 views)
- 4.2.10 Contemporaneous records of actions and administration processes relevant to AIP creation (2,128 views)
- 4.4.1 Specifications for how the AIPs are stored down to the bit level (2,125 views)
- 4.5.2 Capture or create minimum descriptive information for each AIP (2,118 views)
- 5.1.1 Identify and manage the risks to its preservation operations and goals associated with system infrastructure (2,107 views)
- 5.1.1.6.1 Documented change management process that identifies changes to critical processes that potentially affect the repository's ability to comply with its mandatory responsibilities (2,093 views)
- 4.6.1.1 Log and review all access management failures and anomalies (2,077 views)
- 4.2.5.4 Tools or methods to ensure that Representation Information is persistently associated with objects (2,061 views)
- 4.6.2 Follow policies and procedures that enable the dissemination of digital objects that are traceable to the originals (2,059 views)
- 5.1.1.1.7 Procedures in place to evaluate when changes are needed to current software (2,050 views)
- 5.2.4 Suitable written disaster preparedness and recovery plan(s), including at least one off-site backup of all preserved information together with an offsite copy of the recovery plan(s) (2,041 views)
- 4.6.2.1 Record and act upon problem reports about errors in data and responses from users (1,933 views)