Overall TDR Requirement Status

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