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 compliant23 April 2018 17:27:12
3.1.2 Preservation strategic planReady for reviewFully compliant23 April 2018 17:28:14
3.1.2.1 Succession, contingency, escrow plansReady for reviewFully compliant23 April 2018 19:04:13
3.1.2.2 Monitor environment for time to deploy succession, contingency, escrowReady for reviewMostly compliant23 April 2018 16:22:02
3.1.3 Collection policyReady for reviewFully compliant23 April 2018 17:50:54
3.2.1 Identified duties and appointed staffReady for reviewMostly compliant25 April 2018 18:03:54
3.2.1.1 Identified and established dutiesReady for reviewFully compliant23 April 2018 16:51:41
3.2.1.2 Appropriate number of staffReady for reviewMostly compliant18 April 2018 19:21:40
3.2.1.3 Professional development programReady for reviewFully compliant17 April 2018 20:52: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
3.3.2.1 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 ProgressFully compliant23 April 2018 16:19:23
3.4.2 Financial transparency, compliance, and auditsIn ProgressMostly compliant23 April 2018 16:16:56
3.4.3 Risk, benefit, investment, expenditureIn ProgressMostly compliant9 April 2018 19:56:41
3.5.1 Contracts or deposit agreements for contentReady for reviewFully compliant27 April 2018 14:35:55
3.5.1.1 Contracts or deposit agreements for preservation rightsReady for reviewFully compliant6 November 2017 18:29:24
3.5.1.2 Completeness of agreements with depositorsReady for reviewMostly compliant26 April 2018 10:50:34
3.5.1.3 Policies about preservation responsibilityReady for reviewFully compliant26 April 2018 10:57:06
3.5.1.4 Policies about liability and rights challengesReady for reviewFully compliant6 November 2017 18:31:22
3.5.2 Track and manage property rights/restrictionsReady for reviewFully compliant6 November 2017 18:31:46
4) Digital Object Management19 September 2017 20:03:27
4.1.1 Content information and information propertiesReady for reviewFully compliant27 April 2018 13:43:46
4.1.1.1 Identification of information propertiesReady for reviewFully compliant26 April 2018 11:03:28
4.1.1.2 Record of content information and information propertiesReady for reviewFully compliant26 April 2018 11:09:14
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.Ready for reviewFully compliant26 April 2018 11:11:32
4.1.3 Recognition and parsing of SIPsReady for reviewFully compliant26 April 2018 11:12:13
4.1.4 Verification of ProducerReady for reviewFully compliant26 April 2018 11:12:56
4.1.5 Verification of SIPReady for reviewFully compliant26 April 2018 11:13:45
4.1.6 Control over digital objectsReady for reviewFully compliant26 April 2018 11:14:14
4.1.7 Communication with producer/depositorReady for reviewFully compliant26 April 2018 11:15:14
4.1.8 Acquisition recordsReady for reviewFully compliant26 April 2018 11:18:23
4.2.1 Associated definition for each AIP or class of AIPsReady for reviewFully compliant9 March 2018 18:06:52
4.2.1.1 Identify which definition applies to which AIPReady for reviewFully compliant27 April 2018 14:19:44
4.2.1.2 Definition of each AIPReady for reviewFully compliant27 April 2018 14:22:46
4.2.10 Contemporaneous records of actions and administration processes relevant to AIP creationReady for reviewFully compliant27 April 2018 18:01:17
4.2.2 Description of how AIPs are constructed from SIPsReady for reviewFully compliant27 April 2018 14:27:26
4.2.3 Document final disposition of all SIPsReady for reviewFully compliant27 April 2018 14:29:46
4.2.3.1 Procedures if a SIP is not incorporated or discardedReady for reviewFully compliant27 April 2018 14:42:16
4.2.4 Convention that generates persistent, unique identifiers for AIPsReady for reviewFully compliant27 April 2018 15:01:34
4.2.4.1 Uniquely identify each AIPReady for reviewFully compliant27 April 2018 15:05:16
4.2.4.1.1 Have unique identifiersReady for reviewFully compliant27 April 2018 15:07:40
4.2.4.1.2 Assign and maintain persistent identifiers of the AIP and its componentsReady for reviewFully compliant27 April 2018 15:13:49
4.2.4.1.3 Describe any processes for changes to identifiersReady for reviewFully compliant27 April 2018 16:18:05
4.2.4.1.4 Provide a list of all identifiers and check for duplicationsReady for reviewFully compliant27 April 2018 15:59:42
4.2.4.1.5 System of identifiers is adequate now and in the futureReady for reviewFully compliant30 April 2018 17:14:28
4.2.4.2 System of reliable linking/resolution services in order to find identified objectsReady for reviewFully compliant30 April 2018 17:25:03
4.2.5 Tool and resources to provide authoritative Representation Information for all objectsReady for reviewFully compliant30 April 2018 17:40:18
4.2.5.1 Tools or methods to identify the file types of all objectsReady for reviewFully compliant30 April 2018 17:47:06
4.2.5.2 Tools or methods to determine what Representation Information is necessary for understandabilityReady for reviewFully compliant30 April 2018 17:50:11
4.2.5.3 Have access to the requisite Representation InformationReady for reviewFully compliant30 April 2018 17:54:40
4.2.5.4 Tools or methods to ensure that Representation Information is persistently associated with objectsReady for reviewFully compliant30 April 2018 17:58:12
4.2.6 Documented processes for acquiring PDI for associated Content InformationReady for reviewFully compliant27 April 2018 17:59:23
4.2.6.1 Documented processes for acquiring PDIReady for reviewFully compliant30 April 2018 18:02:19
4.2.6.2 Execute documented processes for acquiring PDIReady for reviewFully compliant30 April 2018 18:08:09
4.2.6.3 PDI is persistently associated with Content Information of AIPReady for reviewFully compliant30 April 2018 18:10:44
4.2.7 Content Information is understandable for Designated Community at the time of AIP creationIn ProgressHalf compliant30 April 2018 18:18:11
4.2.7.1 Processes for testing understandability for Designated Community of the Content Information of AIPsIn ProgressNot compliant27 April 2018 18:15:40
4.2.7.2 Execute testing process of Content Information of AIPsIn ProgressNot compliant27 April 2018 18:16:01
4.2.7.3 Bring Content Information of AIP up to level of understandability if it fails testingIn ProgressNot compliant27 April 2018 18:16:22
4.2.8 Verify each AIP for completeness and correctnessReady for reviewFully compliant30 April 2018 18:20:18
4.2.9 Independent mechanism for verifying the integrity of the contentReady for reviewFully compliant30 April 2018 18:21:44
4.3.1 Documented preservation strategies relevant to its holdingsIn ProgressMostly compliant27 April 2018 14:39:16
4.3.2 Mechanisms for monitoring its preservation environmentIn ProgressMostly compliant27 April 2018 13:45:09
4.3.2.1 Mechanisms for monitoring and notification when Representation Information is inadequate for the Designated Community to understand the data holdingsIn ProgressMostly compliant9 March 2018 18:45:56
4.3.3 Mechanisms to change preservation plans as a result of its monitoring activitiesReady for reviewFully compliant26 April 2018 13:58:23
4.3.3.1 Mechanisms for creating, identifying or gathering any extra Representation Information requiredReady for reviewFully compliant18 April 2018 21:49:35
4.3.4 Provide evidence of the effectiveness of its preservation activitiesReady for reviewFully compliant18 April 2018 16:45:55
4.4.1 Specifications for how the AIPs are stored down to the bit levelReady for reviewFully compliant12 March 2018 18:17:08
4.4.1.1 Content Information preservationReady for reviewFully compliant12 March 2018 18:19:51
4.4.1.2 Monitoring integrity of AIPsReady for reviewFully compliant12 March 2018 19:13:24
4.4.2 AIP storage and preservation recordsReady for reviewFully compliant12 March 2018 19:15:21
4.4.2.1 AIP proceduresReady for reviewFully compliant23 April 2018 17:57:41
4.4.2.2 Compliance with specificationReady for reviewFully compliant23 April 2018 18:02:53
4.5.1 Specify minimum information requirements to enable the Designated Community to discover and identify materialReady for reviewFully compliant27 April 2018 14:39:07
4.5.2 Capture or create minimum descriptive information for each AIPReady for reviewMostly compliant27 April 2018 15:08:40
4.5.3 Create bi-directional linkages between each AIP and its descriptive informationReady for reviewMostly compliant27 April 2018 15:48:39
4.5.3.1 Maintaining AssociationsReady for reviewMostly compliant10 April 2018 19:17:55
4.6.1 Comply with Access PoliciesReady for reviewFully compliant23 March 2018 20:47:16
4.6.1.1 Log and review all access management failures and anomaliesReady for reviewFully compliant19 April 2018 16:00:48
4.6.2 Follow policies and procedures that enable the dissemination of digital objects that are traceable to the originalsReady for reviewFully compliant25 March 2018 22:39:53
4.6.2.1 Record and act upon problem reports about errors in data and responses from usersReady for reviewFully compliant19 April 2018 16:07:31
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 infrastructureReady for reviewFully compliant27 April 2018 14:38:06
5.1.1.1 Employ technology watches or other technology monitoring notification systemsReady for reviewFully compliant6 November 2017 15:24:48
5.1.1.1.1 Hardware technologies appropriate to the services it provides to its designated communitiesReady for reviewFully compliant6 November 2017 15:33:34
5.1.1.1.2 Procedures in place to monitor and receive notifications when hardware technology changes are neededReady for reviewFully compliant6 November 2017 15:35:07
5.1.1.1.3 Procedures in place to evaluate when changes are needed to current hardwareReady for reviewFully compliant6 November 2017 15:36:43
5.1.1.1.4 Procedures, commitment and funding to replace hardware when evaluation indicates the need to do soReady for reviewFully compliant6 November 2017 15:41:30
5.1.1.1.5 Software technologies appropriate to the services it provides to its designated communitiesReady for reviewFully compliant23 April 2018 16:50:41
5.1.1.1.6 Procedures in place to monitor and receive notifications when software changes are neededReady for reviewFully compliant6 November 2017 16:59:26
5.1.1.1.7 Procedures in place to evaluate when changes are needed to current softwareReady for reviewFully compliant6 November 2017 17:00:21
5.1.1.1.8 Procedures, commitment and funding to replace software when evaluation indicates the need to do soReady for reviewFully compliant6 April 2018 19:24:41
5.1.1.2 Adequate hardware and software support for backup functionality sufficient for preserving the repository content and tracking repository functionsReady for reviewFully compliant6 November 2017 17:58:17
5.1.1.3 Effective mechanisms to detect bit corruption or lossReady for reviewFully compliant23 April 2018 16:59:04
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/replaceReady for reviewFully compliant23 April 2018 17:00:36
5.1.1.4 Process to record and react to the availability of new security updates based on a risk-benefit assessmentReady for reviewFully compliant6 November 2017 16:40:03
5.1.1.5 Defined processes for storage media and/or hardware change (e.g., refreshing, migration)In ProgressFully compliant27 April 2018 15:06:41
5.1.1.6 Identified and documented critical processes that affect its ability to comply with its mandatory responsibilitiesIn ProgressHalf compliant27 April 2018 15:03:03
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 responsibilitiesIn ProgressNot compliant27 April 2018 14:56:42
5.1.1.6.2 Process for testing and evaluating the effect of changes to the repository's critical processesFully compliant27 April 2018 14:51:41
5.1.2 Manage the number and location of copies of all digital objectsIn ProgressHalf compliant27 April 2018 15:14:43
5.1.2.1 Mechanisms in place to ensure any/multiple copies of digital objects are synchronizedIn ProgressHalf compliant12 September 2017 19:54:35
5.2.1 Maintain a systematic analysis of security risk factors associated with data, systems, personnel, and physical plantReady for reviewFully compliant25 April 2018 17:57:09
5.2.2 Implemented controls to adequately address each of the defined security risksReady for reviewFully compliant25 April 2018 17:59:05
5.2.3 Staff shall have delineated roles, responsibilities, and authorizations related to implementing changesReady for reviewFully compliant25 April 2018 19:50:02
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)In ProgressHalf compliant25 April 2018 19:54:01
Christian-overview13 June 2017 20:28:29
Christians pageReady for reviewSlightly compliant25 September 2017 19:07:06
Trusted Digital Repository23 April 2018 19:36:23