| |
Status |
Compliance Rating |
Last modification date |
| 3.1.1 Mission statement |
Ready for review |
Fully compliant |
14 September 2018 21:31:56 |
| 3.1.2 Preservation strategic plan |
Ready for review |
Fully compliant |
14 September 2018 21:32:19 |
| 3.1.2.1 Succession, contingency, escrow plans |
Ready for review |
Fully compliant |
14 September 2018 21:34:27 |
| 3.1.2.2 Monitor environment for time to deploy succession, contingency, escrow |
Ready for review |
Fully compliant |
14 September 2018 21:35:04 |
| 3.1.3 Collection policy |
Ready for review |
Fully compliant |
14 September 2018 21:35:25 |
| 3.2.1.1 Identified and established duties |
Ready for review |
Fully compliant |
14 September 2018 21:37:00 |
| 3.2.1.2 Appropriate number of staff |
Ready for review |
Fully compliant |
14 September 2018 21:37:22 |
| 3.2.1.3 Professional development program |
Ready for review |
Fully compliant |
14 September 2018 21:37:45 |
| 3.3.1 Designated community |
Ready for review |
Fully compliant |
13 January 2020 21:54:38 |
| 3.3.2 Preservation policies |
Ready for review |
Fully compliant |
14 September 2018 21:39:02 |
| 3.3.2.1 Review and update preservation policies |
Ready for review |
Fully compliant |
15 July 2019 19:33:55 |
| 3.3.3 Documented history of changes |
Ready for review |
Fully compliant |
14 September 2018 21:41:27 |
| 3.3.4 Commit to transparency |
Ready for review |
Fully compliant |
1 July 2019 17:33:17 |
| 3.3.5 Information integrity measurements |
Ready for review |
Fully compliant |
14 September 2018 21:43:12 |
| 3.3.6 Self-assessment and external certification |
Ready for review |
Fully compliant |
14 September 2018 21:43:31 |
| 3.4.1 Business planning processes |
Ready for review |
Fully compliant |
14 September 2018 21:44:40 |
| 3.4.2 Financial transparency, compliance, and audits |
Ready for review |
Fully compliant |
15 August 2018 22:02:39 |
| 3.4.3 Risk, benefit, investment, expenditure |
Ready for review |
Fully compliant |
14 September 2018 21:45:36 |
| 3.5.1 Contracts or deposit agreements for content |
Ready for review |
Fully compliant |
14 September 2018 21:46:24 |
| 3.5.1.1 Contracts or deposit agreements for preservation rights |
Ready for review |
Fully compliant |
26 August 2019 18:21:07 |
| 3.5.1.2 Completeness of agreements with depositors |
Ready for review |
Fully compliant |
14 September 2018 21:46:57 |
| 3.5.1.3 Policies about preservation responsibility |
Ready for review |
Fully compliant |
26 August 2019 18:22:15 |
| 3.5.1.4 Policies about liability and rights challenges |
Ready for review |
Fully compliant |
14 September 2018 21:47:29 |
| 3.5.2 Track and manage property rights/restrictions |
Ready for review |
Fully compliant |
14 September 2018 21:47:45 |
| 4.1.1 Content information and information properties |
Ready for review |
Fully compliant |
14 September 2018 20:34:10 |
| 4.1.1.1 Identification of information properties |
Ready for review |
Fully compliant |
14 September 2018 20:34:24 |
| 4.1.1.2 Record of content information and information properties |
Ready for review |
Fully compliant |
14 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 review |
Fully compliant |
26 August 2019 18:19:57 |
| 4.1.3 Recognition and parsing of SIPs |
Ready for review |
Fully compliant |
14 September 2018 20:35:03 |
| 4.1.4 Verification of Producer |
Ready for review |
Fully compliant |
14 September 2018 20:35:37 |
| 4.1.5 Verification of SIP |
Ready for review |
Fully compliant |
30 April 2020 18:48:02 |
| 4.1.6 Control over digital objects |
Ready for review |
Fully compliant |
26 August 2019 18:20:41 |
| 4.1.7 Communication with producer/depositor |
Ready for review |
Fully compliant |
14 September 2018 20:36:31 |
| 4.1.8 Acquisition records |
Ready for review |
Fully compliant |
14 September 2018 20:36:47 |
| 4.2.1 Associated definition for each AIP or class of AIPs |
Ready for review |
Fully compliant |
14 September 2018 18:27:48 |
| 4.2.1.1 Identify which definition applies to which AIP |
Ready for review |
Fully compliant |
16 August 2018 00:18:39 |
| 4.2.1.2 Definition of each AIP |
Ready for review |
Fully compliant |
14 September 2018 20:38:05 |
| 4.2.3 Document final disposition of all SIPs |
Ready for review |
Fully compliant |
14 September 2018 20:39:02 |
| 4.2.3.1 Procedures if a SIP is not incorporated or discarded |
Ready for review |
Fully compliant |
14 September 2018 20:45:22 |
| 4.2.4 Convention that generates persistent, unique identifiers for AIPs |
Ready for review |
Fully compliant |
14 September 2018 20:45:55 |
| 4.2.4.1 Uniquely identify each AIP |
Ready for review |
Fully compliant |
14 September 2018 20:46:57 |
| 4.2.4.1.1 Have unique identifiers |
Ready for review |
Fully compliant |
14 September 2018 20:48:04 |
| 4.2.4.1.2 Assign and maintain persistent identifiers of the AIP and its components |
Ready for review |
Fully compliant |
14 September 2018 20:48:25 |
| 4.2.4.1.3 Describe any processes for changes to identifiers |
Ready for review |
Fully compliant |
14 September 2018 20:49:20 |
| 4.2.4.1.4 Provide a list of all identifiers and check for duplications |
Ready for review |
Fully compliant |
14 September 2018 20:49:35 |
| 4.2.4.1.5 System of identifiers is adequate now and in the future |
Ready for review |
Fully compliant |
14 September 2018 20:49:53 |
| 4.2.4.2 System of reliable linking/resolution services in order to find identified objects |
Ready for review |
Fully compliant |
14 September 2018 20:50:46 |
| 4.2.5 Tool and resources to provide authoritative Representation Information for all objects |
Ready for review |
Fully compliant |
14 September 2018 20:51:25 |
| 4.2.5.1 Tools or methods to identify the file types of all objects |
Ready for review |
Fully compliant |
14 September 2018 20:53:41 |
| 4.2.5.2 Tools or methods to determine what Representation Information is necessary for understandability |
Ready for review |
Fully compliant |
14 September 2018 20:54:04 |
| 4.2.5.3 Have access to the requisite Representation Information |
Ready for review |
Fully compliant |
14 September 2018 20:54:18 |
| 4.2.5.4 Tools or methods to ensure that Representation Information is persistently associated with objects |
Ready for review |
Fully compliant |
14 September 2018 20:54:39 |
| 4.2.6 Documented processes for acquiring PDI for associated Content Information |
Ready for review |
Fully compliant |
14 September 2018 20:56:45 |
| 4.2.6.1 Documented processes for acquiring PDI |
Ready for review |
Fully compliant |
14 September 2018 20:59:40 |
| 4.2.6.2 Execute documented processes for acquiring PDI |
Ready for review |
Fully compliant |
14 September 2018 20:59:08 |
| 4.2.6.3 PDI is persistently associated with Content Information of AIP |
Ready for review |
Fully compliant |
14 September 2018 21:00:08 |
| 4.2.7 Content Information is understandable for Designated Community at the time of AIP creation |
Ready for review |
Fully compliant |
26 August 2019 18:30:45 |
| 4.2.7.1 Processes for testing understandability for Designated Community of the Content Information of AIPs |
|
Fully compliant |
14 May 2019 18:17:19 |
| 4.2.7.2 Execute testing process of Content Information of AIPs |
Ready for review |
Fully compliant |
28 May 2020 19:44:49 |
| 4.2.7.3 Bring Content Information of AIP up to level of understandability if it fails testing |
Ready for review |
Fully compliant |
25 June 2019 21:55:03 |
| 4.2.8 Verify each AIP for completeness and correctness |
Ready for review |
Fully compliant |
29 April 2019 19:44:48 |
| 4.2.9 Independent mechanism for verifying the integrity of the content |
Ready for review |
Fully compliant |
29 April 2019 19:47:18 |
| 4.2.10 Contemporaneous records of actions and administration processes relevant to AIP creation |
Ready for review |
Fully compliant |
29 April 2019 19:47:18 |
| 4.3.1 Documented preservation strategies relevant to its holdings |
Ready for review |
Fully compliant |
26 August 2019 18:42:14 |
| 4.3.2 Mechanisms for monitoring its preservation environment |
Ready for review |
Fully compliant |
30 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 holdings |
Ready for review |
Fully compliant |
26 August 2019 18:31:53 |
| 4.3.3 Mechanisms to change preservation plans as a result of its monitoring activities |
Ready for review |
Fully compliant |
14 September 2018 21:23:33 |
| 4.3.3.1 Mechanisms for creating, identifying or gathering any extra Representation Information required |
Ready for review |
Fully compliant |
14 September 2018 21:24:10 |
| 4.3.4 Provide evidence of the effectiveness of its preservation activities |
Ready for review |
Fully compliant |
5 October 2018 21:08:34 |
| 4.4.1 Specifications for how the AIPs are stored down to the bit level |
Ready for review |
Fully compliant |
16 August 2018 01:18:14 |
| 4.4.1.1 Content Information preservation |
Ready for review |
Fully compliant |
14 September 2018 21:26:55 |
| 4.4.1.2 Monitoring integrity of AIPs |
Ready for review |
Fully compliant |
26 August 2019 18:37:48 |
| 4.4.2 AIP storage and preservation records |
Ready for review |
Fully compliant |
14 September 2018 21:27:22 |
| 4.4.2.1 AIP procedures |
Ready for review |
Fully compliant |
14 September 2018 21:27:40 |
| 4.4.2.2 Compliance with specification |
Ready for review |
Fully compliant |
14 September 2018 21:27:58 |
| 4.5.1 Specify minimum information requirements to enable the Designated Community to discover and identify material |
Ready for review |
Fully compliant |
26 August 2019 18:33:42 |
| 4.5.2 Capture or create minimum descriptive information for each AIP |
Ready for review |
Fully compliant |
14 September 2018 20:08:56 |
| 4.5.3 Create bi-directional linkages between each AIP and its descriptive information |
Ready for review |
Fully compliant |
28 June 2019 19:58:40 |
| 4.5.3.1 Maintaining Associations |
Ready for review |
Fully compliant |
14 September 2018 20:32:49 |
| 4.6.1 Comply with Access Policies |
Ready for review |
Fully compliant |
14 September 2018 21:28:52 |
| 4.6.1.1 Log and review all access management failures and anomalies |
Ready for review |
Fully compliant |
14 September 2018 21:29:07 |
| 4.6.2 Follow policies and procedures that enable the dissemination of digital objects that are traceable to the originals |
Ready for review |
Fully compliant |
14 September 2018 21:29:25 |
| 4.6.2.1 Record and act upon problem reports about errors in data and responses from users |
Ready for review |
Fully compliant |
14 September 2018 21:29:46 |
| 5.1.1 Identify and manage the risks to its preservation operations and goals associated with system infrastructure |
Ready for review |
Fully compliant |
27 August 2018 18:05:08 |
| 5.1.1.1 Employ technology watches or other technology monitoring notification systems |
Ready for review |
Fully compliant |
27 August 2018 18:22:36 |
| 5.1.1.1.2 Procedures in place to monitor and receive notifications when hardware technology changes are needed |
Ready for review |
Fully compliant |
27 August 2018 18:27:33 |
| 5.1.1.1.3 Procedures in place to evaluate when changes are needed to current hardware |
Ready for review |
Fully compliant |
16 August 2018 15:25:23 |
| 5.1.1.1.4 Procedures, commitment and funding to replace hardware when evaluation indicates the need to do so |
Ready for review |
Fully compliant |
14 September 2018 18:04:24 |
| 5.1.1.1.5 Software technologies appropriate to the services it provides to its designated communities |
Ready for review |
Fully compliant |
27 August 2018 18:45:02 |
| 5.1.1.1.6 Procedures in place to monitor and receive notifications when software changes are needed |
Ready for review |
Fully compliant |
16 August 2018 15:43:24 |
| 5.1.1.1.7 Procedures in place to evaluate when changes are needed to current software |
Ready for review |
Fully compliant |
28 August 2018 18:51:49 |
| 5.1.1.1.8 Procedures, commitment and funding to replace software when evaluation indicates the need to do so |
Ready for review |
Fully compliant |
29 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 functions |
Ready for review |
Fully compliant |
26 August 2019 18:23:04 |
| 5.1.1.3 Effective mechanisms to detect bit corruption or loss |
Ready for review |
Fully compliant |
29 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/replace |
Ready for review |
Fully compliant |
28 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 assessment |
Ready for review |
Fully compliant |
28 August 2018 19:24:36 |
| 5.1.1.5 Defined processes for storage media and/or hardware change (e.g., refreshing, migration) |
Ready for review |
Fully compliant |
28 August 2018 19:30:56 |
| 5.1.1.6 Identified and documented critical processes that affect its ability to comply with its mandatory responsibilities |
In Progress |
Half compliant |
19 November 2019 17:27:33 |
| 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 |
In Progress |
Not compliant |
30 July 2019 15:08:29 |
| 5.1.1.6.2 Process for testing and evaluating the effect of changes to the repository’s critical processes |
Ready for review |
Fully compliant |
16 August 2018 16:40:18 |
| 5.1.2 Manage the number and location of copies of all digital objects |
Ready for review |
Fully compliant |
30 August 2018 16:15:51 |
| 5.1.2.1 Mechanisms in place to ensure any/multiple copies of digital objects are synchronized |
Ready for review |
Fully compliant |
16 August 2018 16:51:58 |
| 5.2.1 Maintain a systematic analysis of security risk factors associated with data, systems, personnel, and physical plant |
Ready for review |
Fully compliant |
16 August 2018 17:26:14 |
| 5.2.2 Implemented controls to adequately address each of the defined security risks |
Ready for review |
Fully compliant |
16 August 2018 17:28:37 |
| 5.2.3 Staff shall have delineated roles, responsibilities, and authorizations related to implementing changes |
Ready for review |
Fully compliant |
10 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 Progress |
Half compliant |
1 July 2019 17:23:08 |
| Mandatory Responsibilities |
|
|
26 August 2019 18:59:09 |
