Oldest pages
Showing below up to 100 results starting with #1.
View (previous 100 | next 100) (20 | 50 | 100 | 250 | 500)
- 3) Organizational Infrastructure (00:05, 22 September 2013)
- 4) Digital Object Management (00:17, 22 September 2013)
- 5) Infrastructure and Security Risk Management (00:20, 22 September 2013)
- 5.1.1 Identify and manage the risks to its preservation operations and goals associated with system infrastructure (15:28, 23 September 2013)
- 5.1.1.1 Employ technology watches or other technology monitoring notification systems (15:29, 23 September 2013)
- 5.1.1.1.1 Hardware technologies appropriate to the services it provides to its designated communities (15:31, 23 September 2013)
- 5.1.1.1.2 Procedures in place to monitor and receive notifications when hardware technology changes are needed (15:32, 23 September 2013)
- 5.1.1.1.3 Procedures in place to evaluate when changes are needed to current hardware (15:33, 23 September 2013)
- 5.1.1.1.4 Procedures, commitment and funding to replace hardware when evaluation indicates the need to do so (15:34, 23 September 2013)
- 5.1.1.1.6 Procedures in place to monitor and receive notifications when software changes are needed (15:37, 23 September 2013)
- 5.1.1.1.7 Procedures in place to evaluate when changes are needed to current software (15:38, 23 September 2013)
- 5.1.1.1.8 Procedures, commitment and funding to replace software when evaluation indicates the need to do so (15:39, 23 September 2013)
- 5.1.1.2 Adequate hardware and software support for backup functionality sufficient for preserving the repository content and tracking repository functions (15:42, 23 September 2013)
- 5.1.1.3 Effective mechanisms to detect bit corruption or loss (15:43, 23 September 2013)
- 5.1.1.3.1 Record and report to its administration all incidents of data corruption or loss, and steps shall be taken to repair/replace (15:43, 23 September 2013)
- 5.1.1.5 Defined processes for storage media and/or hardware change (e.g., refreshing, migration) (15:45, 23 September 2013)
- 5.1.1.6 Identified and documented critical processes that affect its ability to comply with its mandatory responsibilities (15:46, 23 September 2013)
- 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 (15:47, 23 September 2013)
- 5.1.1.6.2 Process for testing and evaluating the effect of changes to the repository's critical processes (15:48, 23 September 2013)
- 5.1.2.1 Mechanisms in place to ensure any/multiple copies of digital objects are synchronized (16:09, 23 September 2013)
- 5.2.1 Maintain a systematic analysis of security risk factors associated with data, systems, personnel, and physical plant (16:10, 23 September 2013)
- 5.2.2 Implemented controls to adequately address each of the defined security risks (16:11, 23 September 2013)
- 5.2.3 Staff shall have delineated roles, responsibilities, and authorizations related to implementing changes (16:12, 23 September 2013)
- 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) (16:13, 23 September 2013)
- 4.1.1 Identify content information and information properties (16:16, 23 September 2013)
- 4.1.1.1 Procedures for identifying information properties that we will preserve (16:19, 23 September 2013)
- 4.1.1.2 Record of content information and information properties that we will preserve (16:21, 23 September 2013)
- 4.1.2 Specify content information at deposit (16:21, 23 September 2013)
- 4.1.3 Recognition and parsing of SIPs (17:33, 23 September 2013)
- 4.1.4 Verify the identity of the Producer (17:36, 23 September 2013)
- 4.1.5 Verify SIPs for completeness and correctness (17:37, 23 September 2013)
- 4.1.6 Obtain sufficient control over digital objects (17:39, 23 September 2013)
- 4.1.7 Provide depositor with responses (17:40, 23 September 2013)
- 4.1.8 Records of actions and processes related to acquisition (17:42, 23 September 2013)
- 4.2.1 Associated definition for each AIP or class of AIPs (17:54, 23 September 2013)
- 4.2.1.1 Identify which definition applies to which AIP (17:58, 23 September 2013)
- 4.2.1.2 Definition of each AIP (18:03, 23 September 2013)
- 4.2.2 Description of how AIPs are constructed from SIPs (18:05, 23 September 2013)
- 4.2.3 Document final disposition of all SIPs (18:06, 23 September 2013)
- 4.2.3.1 Procedures if a SIP is not incorporated or discarded (18:07, 23 September 2013)
- 4.2.4 Convention that generates persistent, unique identifiers for AIPs (18:35, 23 September 2013)
- 4.2.4.1 Uniquely identify each AIP (18:36, 23 September 2013)
- 4.2.4.1.1 Have unique identifiers (18:37, 23 September 2013)
- 4.2.4.1.2 Assign and maintain persistent identifiers of the AIP and its components (18:39, 23 September 2013)
- 4.2.4.1.3 Describe any processes for changes to identifiers (18:40, 23 September 2013)
- 4.2.4.1.4 Provide a list of all identifiers and check for duplications (18:41, 23 September 2013)
- 4.2.4.1.5 System of identifiers is adequate now and in the future (18:42, 23 September 2013)
- 4.2.4.2 System of reliable linking/resolution services in order to find identified objects (18:43, 23 September 2013)
- 4.2.5 Tool and resources to provide authoritative Representation Information for all objects (18:45, 23 September 2013)
- 4.2.5.1 Tools or methods to identify the file types of all objects (18:48, 23 September 2013)
- 4.2.5.2 Tools or methods to determine what Representation Information is necessary for understandability (18:49, 23 September 2013)
- 4.2.5.3 Have access to the requisite Representation Information (18:51, 23 September 2013)
- 4.2.5.4 Tools or methods to ensure that Representation Information is persistently associated with objects (18:52, 23 September 2013)
- 4.2.6 Documented processes for acquiring PDI for associated Content Information (18:53, 23 September 2013)
- 4.2.6.1 Documented processes for acquiring PDI (18:54, 23 September 2013)
- 4.2.6.2 Execute documented processes for acquiring PDI (18:55, 23 September 2013)
- 4.2.6.3 PDI is persistently associated with Content Information of AIP (18:57, 23 September 2013)
- 4.2.7.1 Processes for testing understandability for Designated Community of the Content Information of AIPs (19:00, 23 September 2013)
- 4.2.7.2 Execute testing process of Content Information of AIPs (19:01, 23 September 2013)
- 4.2.7.3 Bring Content Information of AIP up to level of understandability if it fails testing (19:02, 23 September 2013)
- 4.2.8 Verify each AIP for completeness and correctness (19:02, 23 September 2013)
- 4.2.9 Independent mechanism for verifying the integrity of the content (19:03, 23 September 2013)
- 4.2.10 Contemporaneous records of actions and administration processes relevant to AIP creation (19:04, 23 September 2013)
- 4.3.1 Documented preservation strategies relevant to its holdings (19:06, 23 September 2013)
- 4.3.2 Mechanisms for monitoring its preservation environment (19:06, 23 September 2013)
- 4.3.2.1 Mechanisms for monitoring and notification when Representation Information is inadequate for the Designated Community to understand the data holdings (19:07, 23 September 2013)
- 4.3.3 Mechanisms to change preservation plans as a result of its monitoring activities (19:09, 23 September 2013)
- 4.3.3.1 Mechanisms for creating, identifying or gathering any extra Representation Information required (19:10, 23 September 2013)
- 4.4.1 Specifications for how the AIPs are stored down to the bit level (19:13, 23 September 2013)
- 4.4.1.1 Preserve the Content Information of AIPs (19:14, 23 September 2013)
- 4.4.1.2 Actively monitor the integrity of AIPs (19:15, 23 September 2013)
- 4.4.2 Contemporaneous records of actions and administration processes that are relevant to storage and preservation of the AIPs (19:16, 23 September 2013)
- 4.4.2.1 Procedures for all actions taken on AIPs (19:19, 23 September 2013)
- 4.4.2.2 Demonstrate that any actions taken on AIPs were compliant with the specification of those actions (19:20, 23 September 2013)
- 4.5.1 Specify minimum information requirements to enable the Designated Community to discover and identify material (19:21, 23 September 2013)
- 4.5.2 Capture or create minimum descriptive information for each AIP (19:22, 23 September 2013)
- 4.5.3 Create bi-directional linkages between each AIP and its descriptive information (19:23, 23 September 2013)
- 4.6.1 Comply with Access Policies (19:25, 23 September 2013)
- 4.6.1.1 Log and review all access management failures and anomalies (19:26, 23 September 2013)
- 4.6.2 Follow policies and procedures that enable the dissemination of digital objects that are traceable to the originals (19:30, 23 September 2013)
- 4.6.2.1 Record and act upon problem reports about errors in data and responses from users (19:31, 23 September 2013)
- 3.1.1 Mission statement (20:18, 23 September 2013)
- 3.1.2 Preservation strategic plan (20:19, 23 September 2013)
- 3.1.2.1 Succession, contigency, escrow plans (20:20, 23 September 2013)
- 3.1.2.2 Monitor environment for time to deploy succession, contingency, escrow (20:20, 23 September 2013)
- 3.1.3 Collection policy (20:21, 23 September 2013)
- 3.2.1 Identified duties and appointed staff (20:22, 23 September 2013)
- 3.2.1.1 Identified and established duties (20:22, 23 September 2013)
- 3.2.1.2 Appropriate number of staff (20:23, 23 September 2013)
- 3.2.1.3 Professional development program (20:24, 23 September 2013)
- 3.3.1 Designated community (20:25, 23 September 2013)
- 3.3.2 Preservation policies (20:25, 23 September 2013)
- 3.3.2.1 Review and update preservation policies (20:26, 23 September 2013)
- 3.3.3 Documented history of changes (20:27, 23 September 2013)
- 3.3.4 Commit to transparency (20:29, 23 September 2013)
- 3.3.5 Information integrity measurements (20:30, 23 September 2013)
- 3.3.6 Self-assessment and external certification (20:30, 23 September 2013)
- 3.4.1 Business planning processes (20:32, 23 September 2013)
- 3.4.2 Financial transparency, compliance, and audits (20:33, 23 September 2013)
- 3.4.3 Risk, benefit, investment, expenditure (20:34, 23 September 2013)