Overall TDR Requirement Status

From aptrust
Jump to: navigation, search

This page is generated automatically by subpages in the category TDR and with 'Status' and 'Compliance Rating' attributes.

 StatusCompliance RatingLast modification date
"Modification date" is a predefined property that corresponds to the date of the last modification of a subject and is provided by Semantic MediaWiki.
3) Organizational Infrastructure12 September 2017 20:07:39
3.1.1 Mission statementReady for reviewFully compliant8 September 2017 16:56:20
3.1.2 Preservation strategic plan8 September 2017 16:46:20 Succession, contingency, escrow plansIn ProgressMostly compliant28 September 2017 16:20:13 Monitor environment for time to deploy succession, contingency, escrowIn ProgressHalf compliant28 September 2017 16:54:36
3.1.3 Collection policyIn ProgressSlightly compliant28 September 2017 16:49:28
3.2.1 Identified duties and appointed staff8 September 2017 16:47:50 Identified and established dutiesNot StartedNot compliant12 September 2017 19:43:53 Appropriate number of staffSlightly compliant25 September 2017 16:33:18 Professional development program8 September 2017 16:57:17
3.3.1 Designated communityIn ProgressMostly compliant8 September 2017 16:59:00
3.3.2 Preservation policiesIn ProgressSlightly compliant8 September 2017 16:59:42 Review and update preservation policiesIn ProgressSlightly compliant8 September 2017 17:00:17
3.3.3 Documented history of changesIn ProgressSlightly compliant8 September 2017 17:00:41
3.3.4 Commit to transparencyIn ProgressSlightly compliant8 September 2017 17:00:52
3.3.5 Information integrity measurementsIn ProgressMostly compliant8 September 2017 17:01:18
3.3.6 Self-assessment and external certificationIn ProgressSlightly compliant8 September 2017 17:01:34
3.4.1 Business planning processesIn ProgressHalf compliant28 September 2017 14:44:47
3.4.2 Financial transparency, compliance, and auditsIn ProgressMostly compliant28 September 2017 16:03:17
3.4.2. Christian's Special SectionIn ProgressSlightly compliant25 September 2017 17:02:17
3.4.3 Risk, benefit, investment, expenditureIn ProgressMostly compliant28 September 2017 16:10:40
4) Digital Object Management19 September 2017 20:03:27
4.1.1 Content information and information propertiesIn ProgressMostly compliant25 September 2017 16:23:27 Identification of information propertiesIn ProgressHalf compliant8 September 2017 17:48:25 Record of content information and information propertiesIn ProgressHalf compliant8 September 2017 17:48:35
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.In ProgressSlightly compliant12 September 2017 17:17:13
4.1.3 Recognition and parsing of SIPsIn ProgressHalf compliant8 September 2017 17:50:32
4.1.4 Verification of ProducerIn ProgressFully compliant8 September 2017 17:51:23
4.1.5 Verification of SIPIn ProgressHalf compliant8 September 2017 18:20:54
4.1.6 Control over digital objectsIn ProgressHalf compliant11 September 2017 20:43:25
4.1.7 Communication with producer/depositorIn ProgressMostly compliant2 October 2017 21:20:46
4.1.8 Acquisition recordsIn ProgressMostly compliant8 September 2017 17:59:44 Procedures if a SIP is not incorporated or discardedNot StartedNot compliant12 September 2017 19:44:28
4.2.4 Convention that generates persistent, unique identifiers for AIPs11 September 2017 20:00:27
4.3.1 Documented preservation strategies relevant to its holdingsReady for reviewFully compliant4 October 2017 18:07:03
4.3.2 Mechanisms for monitoring its preservation environmentIn ProgressMostly compliant4 October 2017 18:16:13 Mechanisms for monitoring and notification when Representation Information is inadequate for the Designated Community to understand the data holdingsIn ProgressMostly compliant4 October 2017 18:20:33
4.3.3 Mechanisms to change preservation plans as a result of its monitoring activitiesIn ProgressMostly compliant4 October 2017 18:23:58 Mechanisms for creating, identifying or gathering any extra Representation Information requiredIn ProgressNot compliant4 October 2017 18:34:17
4.3.4 Provide evidence of the effectiveness of its preservation activitiesIn ProgressMostly compliant4 October 2017 18:45:42
4.4.1 Specifications for how the AIPs are stored down to the bit levelIn ProgressSlightly compliant2 October 2017 17:11:50 Content Information preservationIn ProgressSlightly compliant19 September 2017 21:47:29 Monitoring integrity of AIPsIn ProgressHalf compliant5 October 2017 19:14:35
4.4.2 AIP storage and preservation recordsIn ProgressMostly compliant2 October 2017 16:49:53 AIP proceduresIn ProgressSlightly compliant2 October 2017 21:36:27 Compliance with specificationIn ProgressSlightly compliant2 October 2017 21:40:20
4.5.1 Specify minimum information requirements to enable the Designated Community to discover and identify materialReady for reviewFully compliant12 September 2017 19:44:53
4.5.2 Capture or create minimum descriptive information for each AIPReady for reviewMostly compliant8 September 2017 19:36:51
4.5.3 Create bi-directional linkages between each AIP and its descriptive informationIn ProgressHalf compliant8 September 2017 20:48:08 Maintaining AssociationsIn ProgressSlightly compliant8 September 2017 20:55:58
4.6.1 Comply with Access PoliciesIn ProgressMostly compliant4 October 2017 18:52:51 Log and review all access management failures and anomaliesIn ProgressSlightly compliant4 October 2017 18:56:45
4.6.2 Follow policies and procedures that enable the dissemination of digital objects that are traceable to the originalsReady for reviewFully compliant4 October 2017 18:58:59 Record and act upon problem reports about errors in data and responses from usersReady for reviewFully compliant4 October 2017 19:04:17
5) Infrastructure and Security Risk Management8 September 2017 16:27:56
5.1.1 Identify and manage the risks to its preservation operations and goals associated with system infrastructureIn ProgressMostly compliant12 September 2017 19:45:11 Employ technology watches or other technology monitoring notification systems8 September 2017 16:30:02 Hardware technologies appropriate to the services it provides to its designated communitiesIn ProgressMostly compliant11 September 2017 17:48:17 Procedures in place to monitor and receive notifications when hardware technology changes are neededIn ProgressMostly compliant12 September 2017 19:45:30 Procedures in place to evaluate when changes are needed to current hardwareIn ProgressMostly compliant12 September 2017 19:45:48 Procedures, commitment and funding to replace hardware when evaluation indicates the need to do soIn ProgressMostly compliant12 September 2017 19:46:03 Software technologies appropriate to the services it provides to its designated communitiesIn ProgressMostly compliant12 September 2017 19:46:15 Procedures in place to monitor and receive notifications when software changes are neededIn ProgressHalf compliant12 September 2017 19:46:30 Procedures in place to evaluate when changes are needed to current softwareIn ProgressHalf compliant12 September 2017 19:46:58 Procedures, commitment and funding to replace software when evaluation indicates the need to do soIn ProgressHalf compliant12 September 2017 19:47:08 Adequate hardware and software support for backup functionality sufficient for preserving the repository content and tracking repository functionsIn ProgressHalf compliant12 September 2017 19:47:57 Effective mechanisms to detect bit corruption or lossIn ProgressHalf compliant12 September 2017 19:47:19 Record and report to its administration all incidents of data corruption or loss, and steps shall be taken to repair/replaceIn ProgressHalf compliant12 September 2017 19:48:08 Process to record and react to the availability of new security updates based on a risk-benefit assessmentIn ProgressHalf compliant12 September 2017 19:48:20 Defined processes for storage media and/or hardware change (e.g., refreshing, migration)In ProgressHalf compliant12 September 2017 19:48:30 Identified and documented critical processes that affect its ability to comply with its mandatory responsibilitiesIn ProgressHalf compliant12 September 2017 19:48:40 Documented change management process that identifies changes to critical processes that potentially affect the repository's ability to comply with its mandatory responsibilitiesIn ProgressNot compliant8 September 2017 16:37:56 Process for testing and evaluating the effect of changes to the repository's critical processesIn ProgressHalf compliant12 September 2017 19:49:12
5.1.2 Manage the number and location of copies of all digital objectsIn ProgressHalf compliant12 September 2017 19:54:09 Mechanisms in place to ensure any/multiple copies of digital objects are synchronizedIn ProgressHalf compliant12 September 2017 19:54:35
Christian-overview13 June 2017 20:28:29
Christians pageReady for reviewSlightly compliant25 September 2017 19:07:06
Sample tdrsection5 June 2017 20:51:17
Trusted Digital Repository25 September 2017 17:43:02