Curate ISO 16363 Guide
Penwern Curate ISO 16363 Guide
Penwern is supportive of customer’s attainment of ISO 16363 via self or external certification in requirements where support from the software platform is required. It is a strategic aim of the Curate platform to support attainment by our customers of standards such as ISO 16363 and generic functionality to support this will be road-mapped (if not available). Applicable requirements of ISO 16363 can be found below (download this guide here):
| Metric No. | ISO 16363 Metric | Support from Penwern |
|---|---|---|
| 3.3.3 | The repository shall have a documented history of the changes to its operations, procedures, software and hardware. | A detailed log is maintained of changes to the hardware and software environment of any instance and is available to customers on request. |
| 3.3.4 | The repository shall commit to transparency and accountability in all actions supporting the operation and management of the repository that affect the preservation of digital content over time. | Customers are notified ahead of time of all changes to the system that could impact preservation of digital content over time via software release notes. |
| 3.3.5 | The repository shall define, collect, track and appropriately provide its information integrity measurements. | Curate checks file integrity on upload and clearly reports any damage or corruption to users, compromised files can be retained for validation of a complete upload or removed. Users can also easily view the checksum for any object via the information panel inside Curate for manual verification of any object. The S3 storage backend also maintains file integrity by performing routine checks and silently managing any damage. Curate re-generates an object’s checksum during preservation actions to allow users to completely guarantee its integrity during transformation into an Archival package. |
| 3.5.2 | The repository shall track and manage intellectual property rights and restrictions in use of the repository as required by deposit agreement, contract or license. | Curate supports managing rights through the available elements in the Dublin Core and ISAD(G) metadata schemas. We have a road-mapped feature to create PREMIS files from the preservation actions performed within Curate and we could also provide a way to add PREMIS rights statements to PREMIS files that are exported to integrated systems. |
| 4.1.3 | The repository shall have adequate specifications enabling recognition and parsing of SIPs. | Curate supports creation of SIPs for Archivematica (transfer) and a roadmap capability to create EARK SIPs. Curate can potentially create and validate any SIP format if the specification is well documented and preferably open such as for those available from the EARK project. We will support workflows with EARK SIPs and together with Archivematica as a preservation engine. |
| 4.1.4 | The repository shall have mechanisms to appropriately verify the depositer of all materials. | Uploads through user accounts or private links can be verified in Curate through system logs. We also have a road mapped feature for presenting accession forms to 3rd party producers who can upload content via the private link feature. |
| 4.1.5 | The repository shall have an ingest process which verifies each SIP for completeness and correctness. | SIP validation is possible as an added microservice in Curate if validation tools are available. Again, for any organisation looking to gain ISO 16363 compliance we would recommend looking at the specifications and software tools (including validators) available from the EARK project. |
| 4.1.8 | The repository shall have contemporaneous records of actions and administration processes that are relevant to content acquisition. | Curate keeps comprehensive system logs and a file activity log visible in the file info area. We also create PREMIS3 events from all preservation events and allow export of PREMIS files for example to Archivematica. |
| 4.2.1 | The repository shall have for each AIP or class of AIPs preserved by the repository an associated definition that is adequate for parsing the AIP and for long-term preservation needs. | Curate supports creation of Archivematica AIPs, EARK AIPs or even EARK AIPs containing Archivematica AIPs. We can integrate to EARK compatible repositories or preservation engines such as RoDA. |
| 4.2.2 | The repository shall have a description of how AIPs are constructed from SIPs. | A description of how Archivematica AIPs are constructed can be assembled from examples and the documentation. Full specifications are available and are maintained for EARK AIPs. |
| 4.2.3 | The repository shall document the final disposition of all SIPs. | Curate keeps comprehensive system logs and a file activity log visible in the file info area. Curate also creates PREMIS3 events from all preservation events and allows export of PREMIS files for example to Archivematica. |
| 4.2.4 | The repository shall have and use a convention that generates persistent, unique identifiers for all AIPs. | Curate generates unique, persistent identifiers for every file and folder in the system. These unique identifiers are held in internal data management and also embedded in METS and PREMIS files created by the system. Identifiers are passed to Archivematica via PREMIS on ingest. |
| 4.2.5 | The repository shall have access to necessary tools and resources to provide authoritative Representation Information for all of the digital objects it contains. | |
| 4.2.8 | The repository shall verify each AIP for completeness and correctness at the point it is created. | |
| 4.2.10 | The repository shall have contemporaneous records of actions and administration processes that are relevant to AIP creation. | |
| 4.4.1 | The repository shall have specifications for how the AIPs are stored down to the bit level. | |
| 4.4.1.2 | The repository shall actively monitor the integrity of AIPs. | |
| 4.4.2 | The repository shall have contemporaneous records of actions and administration processes that are relevant to storage and preservation of the AIPs. | |
| 4.5.2 | The repository shall capture or create minimum descriptive information and ensure that it is associated with the AIP. | |
| 4.5.3 | The repository shall maintain bi-directional linkage between each AIP and its descriptive information. |
Curate, Preserve, Protect.
Preservica and the Preservica logo are trademarks of Preservica Ltd.
Artefactual, Archivematica and the ‘a’ logo are trademarks of Artefactual Systems Inc.
Curate™ is a trademark of Penwern Limited.