Child pages
  • TRAC Audit
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

This page will be used to build up our case as part of a TRAC audit.

Governance and organizational viability

A1. Government and organization viability

A2. Organizationl structure and staffing

A3. Procedural accountability and policy framework

A4. Financial sustainability

A5. Contracts, licenses, and liabilities

Digital Object Management

For much of this, the process will be to identify the informal way we comply, formalize it and move it closer to the repository when possible. The "trusted repository" consists of pre-ingest routines, HPSS, backed-up spreadsheets and other workflow documents on elm, wiki documentation of collections, xubmit, fedora, and our purl resolution service.

B1. Ingest: acquisition of content

B1.1 Repository identifies properties it will preserve for digital objects.

This is largely specified on the wiki, in historical ingest routines in SVN, and increasingly by using better content models.

B1.2 Repository clearly specifies information that needs to be associated with digital material at the time of its deposit (i.e., SIP)

This is largely specified on the wiki, in historical ingest routines in SVN, and increasingly by using better content models.

B1.3 Repository has mechanisms to authenticate the source of all materials

B1.4 Repository's ingest process verifies each submitted object (i.e., SIP) for completeness and correctness as specified in B1.2

ImageProc verifies image integrity.
The ingest routine chokes requiring manual intervention if a critical file for a given collection is missing, misnamed or invalid.
Before any ingest files are removed from disk, they are compared with the data pulled off of fedora.

B1.5 Repository obtains sufficient physical control over the digital objects to preserve them.

B1.6 Repository provides producer/depository with appropriate responses at predefined points during the ingest processes.

Image processing/HPSS processing sends an e-mail for success and for failure?
Automatic ingest sends out a report.
Users from the lilly, routinely verify their ingested objects by requesting the PDF as a PURL.

B1.7 Repository can demonstrate when preservation responsibility is formally accepted for the contents of the submitted data objects

The final ingest of a collection, indicated by the removal of the ingest files from the to-fedora directory indicates this, as well as when a file is put into the Archiver database.

B1.8 Repository has contemporaneous records of actions and administration processes that are relevant to preservation (Ingest: content acquisition).

B2

  • No labels