Curate TRAC Guide

Penwern Curate TRAC Guide

Penwern is supportive of customer’s attainment of the Trustworthy Repositories Audit and Certification (TRAC) 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 TRAC and generic functionality to support this will be road-mapped (if not available). Applicable requirements of TRAC could include: 

Download this guide as a PDF
   
Metric No.   		    
TRAC Metric   		    
Support from Penwern   
   
A3.6   		    
Repository has a documented history of the changes to its operations,   procedures, software, and hardware that, where appropriate, is linked to   relevant preservation strategies and describes potential effects on   preserving digital content.   		    
A detailed log is maintained of changes to the hardware and software   environment of any instance and is available to customers on request.   Releases of Curate will also be accompanied by release notes.   
   
A3.7   		    
Repository commits to transparency and accountability in all actions   supporting the operation and management of the repository, especially those   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.   
   
A3.8   		    
Repository commits to defining, collecting, tracking, and providing, on   demand, 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.    
   
A5.1   		    
If repository manages, preserves, and/or provides access to digital   materials on behalf of another organization, it has and maintains appropriate   contracts or deposit agreements.   		    
Curate supports managing rights through the available elements in the   Dublin Core and ISAD(G) metadata schemas. PREMIS   files from the preservation actions performed within Curate are also   generated and we could also provide a way to add PREMIS rights statements to   PREMIS files that are exported to integrated systems.   
   
B1.2   		    
Repository clearly specifies the information that needs to be   associated with digital material at the time of its deposit (i.e., SIP).   		    
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.   
   
B1.3   		    
Repository has mechanisms to authenticate the source 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.   
   
B1.4   		    
Repository’s ingest process verifies each submitted object (i.e., SIP)   for completeness and correctness as specified in B1.2   		    
SIP validation is possible as an added microservice in Curate if   validation tools are available. Again, for any organisation looking to gain   TRAC compliance we would recommend looking at the specifications and software   tools (including validators) available from the EARK project.   
   
B1.5   		    
Repository obtains sufficient physical control over the digital objects   to preserve them.   		    
Curate operates on an object first basis; with records, description and   other metadata being associated with the persistent unique object identifier   generated for that object. In most cases, this means that metadata   referencing any object inside Curate will link to the physical bits and bytes   of the referenced object.   
   
B1.7   		    
Repository can demonstrate when preservation responsibility is formally   accepted for the contents of the submitted data objects (i.e., SIPs).   		    
Curate specifically records the assumption of responsibility for the   preservation of every object in PREMIS metadata associated with the object.   
   
B1.8   		    
Repository has contemporaneous records of actions and administration   processes that are relevant to preservation (Ingest: 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.   
   
B2.1   		    
Repository has an identifiable, written definition for each AIP or   class of information preserved by the repository   		    
Curate AIPs are constructed according to tested, standards-based   frameworks including: Archivematica and EARK structures. Each of these is   maintained and thoroughly described and documented by external specifications   and guidelines.   
   
B2.3   		    
Repository has 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.   
   
B2.4   		    
Repository can demonstrate that all submitted objects (i.e., SIPs) are   either accepted as whole or part of an eventual archival object (i.e., AIP),   or otherwise disposed of in a recorded fashion.   		    
Curate keeps comprehensive system logs and a file activity log visible   in the file info area. When a file is marked for deletion, it is de-accessioned   and the event is marked in PREMIS. Curate also creates PREMIS3 events from   all preservation events and allows export of PREMIS files for example to   Archivematica. Both of these sources will account for all content that has   been ingested to Curate, whether is has eventually comprised a whole or part   of an AIP, is still in the SIP stage, or has been deaccessioned.    
   
B2.5   		    
Repository has and uses a naming convention that generates visible, persistent,   unique identifiers for all archived objects (i.e., 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.
   

   
   
   
B2.6   		    
If unique identifiers are associated with SIPs before ingest, the   repository preserves the identifiers in a way that maintains a persistent   association with the resultant archived object (e.g., AIP).   		    
Curate stores the persistent identifier of a SIP as a metadata variable   associated with the resultant AIP produced from it. This identifier can   easily be viewed by the user or accessed through the data model.    
   
B2.7   		    
Repository demonstrates that it has access to necessary tools and   resources to establish authoritative semantic or technical context of the   digital objects it contains (i.e., access to appropriate international   Representation Information and format registries).   		    
Curate directly implements tools that rely on the PRONOM format   registry to provide its file characterisation and format identification   information. The PRONOM identifier is easily viewable for every appraised   file inside Curate.    
   
B2.8   		    
Repository records/registers Representation Information (including   formats) ingested.   		    
Representation and format information is collected by Curate throughout   the ingest and appraisal process and is easily available through each objects   file information.    
   
B2.9   		    
Repository acquires preservation metadata (i.e., PDI) for its   associated Content Information.   		    
Curate records PREMIS and other preservation metadata formats   throughout the lifecycle of a digital object stored inside Curate.    
   
B2.11   		    
Repository verifies each AIP for completeness and correctness at the   point it is generated.   		    
Curate verifies SIP and AIP integrity before and after preservation   processing, it also records detailed logs of the transformation process to   verify no errors occurred.    
   
B2.13   		    
Repository has contemporaneous records of actions and administration   processes that are relevant to preservation (AIP creation).   		    
Curate records PREMIS metadata for each object before and during AIP   creation.    
   
B4.4   		    
Repository actively monitors integrity of archival objects (i.e.,   AIPs).   		    
Curate uses md5 checksums to maintain the structure of its datamodel,   so each object is implicitly checksummed. Users can export manifests of their   object checksums to compare to future manifests to verify continued   integrity.    
   
B4.5   		    
Repository has contemporaneous records of actions and administration   processes that are relevant to preservation (Archival Storage)   		    
Curate records actions relating to an object in PREMIS, including when   an object has been placed in Archival Storage.   
   
B5.2   		    
Repository captures or creates minimum descriptive metadata and ensures   that it is associated with the archived object (i.e., AIP).   		    
Curate allows users to capture Dublin Core and ISAD(G) descriptive   metadata for all objects, including at the AIP level, and when included in an   AIP wraps the descriptive metadata for each object in the AIPs METS document.   
   
B5.3   		    
Repository can demonstrate that referential integrity is created   between all archived objects (i.e., AIPs) and associated descriptive   information.   		    
Descriptive metadata for each object inside a Curate AIP is wrapped   exclusively inside the AIP METS document.   
   
C1.1   		    
Repository functions on well-supported operating systems and other core   infrastructural software.   		    
Curate is built upon trusted, well-supported software and   infrastructural software. Key components include: Ubuntu Linux, Golang,   React, HTML, CSS, Javascript and Python. Curate is developed to rely on   external or 3rd party dependencies outside of this core stack as   little as possible. Full software stack diagrams are available on request.   
Sign-up now.
Share by: