Reporting & Auditing

Metadata about content preserved by APTrust is managed in a Fedora Repository with a reporting interface built using the Hydra Rails Engine.  Because the actual preservation files are stored in high latency storage, they are not managed directly by Fedora and pointers are used from Fedora to the associated object in preservation storage as a means to associate the metadata with the relevant files.

Goals

  • To provide a means to search and locate individual Digital Objects and their associated files deposited with APTrust.
  • Establishment of a simple convention based identifier schema to link objects and metadata in APTrust to corresponding objects at the original depositors institution as well as to related objects in DPN.
  • Administrative search and view of descriptive metadata related to submission packages sent to APTrust.
  • Administrative search and view of technical metadata for individual digital files deposited in a submission package.
  • Administrative search and viewing of audit summaries for identified events in the management and

Reporting

description of reporting strategy

Digital Object Modeling

Submission packages are modeled in a local Fedora repository to manage metadata, help provide reporting and managed the preservation lifestyle over time.  Submission Packages are read as part of the APTrust ingestion process, with submission metadata stored on the Intellectual Object, technical metadata and pointers to preservation files stored in a Generic File object.  These ditial objects are purposefully abstract to support the submission format agnostic packages to APTrust, while still allowing the depositor to specify a basic level of relationship by packaging files together or seperatly based on whatever relationship they see fit.

Mapping Submission Bags to Fedora Objects

Bags are a submission package only, the metadata contained in the tag files and manifests are stored in Fedora Objects and the digital files submitted in the bag stored in preservation storage with appropriate metadata and pointers stored in Fedora as well.  The following diagram maps the general relationship between submission bags and the objects that model them stored in Fedora.

Submission Bags mapping to Fedora Objects


Fedora Object Diagram


Institution

This represents basic metadata about a depositors institution.  It is pre-defined by the APTrust staff when the institution joins APTrust and is configured as part of setting up a member for deposit.

Intellectual Object

Intellectual items represent the top level abstraction represented by the submission bag and its primary role is to stored required submission metadata and help mediate access to the underlying digital files represented by Generic File objects .  Since each depositor determines individually what the significance of a particular file grouping is during submission, APTrust uses the Intellectual Item to store the submission metadata and register any top level event related to the files grouped under it.

Generic File

Each digital file included in a submission bags data sub-directory will be represented by a Generic File object to record technical metadata, record data from audited events and contain a pointer to the actual file in preservation storage.

Digital Object Metadata

This spreadsheet documents the current fields kept on the various object datastreams in Fedora.

FedoraDatastreamFields


Object Identifiers

description of the convention for object identifiers for Intellectual Objects and Generic Files

Access Condition Definitions

Note that NO access to raw digital files is permitted to anyone at this time.  Access here ONLY refers to being able to view the metadata and events about items stored in APTrust.  This is a basic description of the general labels used throughout the access schema.  Please refer to the Access Grid below for a detailed matrix of what behaviors are allowed with what combination of permissions, roles and conditions.

Role Types:
  • Anonymous: 
    • A non-authenticated or unidentified visitor to the site. 
    • Only included here to explicitly define no access at all.
  • Authenticated:
    • Able to authenticate with the admin interface but has no user group or a user group not defined below.
    • Only included in table to explicitly define no access at all.
  • APTrust Admin:
    • An administrator of the APTrust application.
    • Needs full access for troubleshooting and management of the application.
    • Will be limited to a few lead or Sr roles in APTrust.
  • Institutional Admin:
    • A user assigned to a particular institution that needs the ability to view, edit, update various metadata for their own institutional.
  • Institutional User
    • A user assigned to a particular institution that only needs to view and discover metadata for their own institutional content.

Definition of Access Types:

  • Discover
    • The ability to see items listed in the abbreviated returns of blacklight search results.
  • View
    • The ability to view all Object Metadata.
  • Edit
    • The ability to update some Object Metadata.

Access Condition Types:

  • Consortial:
    • Allows operations by members of OTHER institutions.
  • Institution:
    • Allows some operations by members of your OWN institution.
  • Restricted:
    • Allows some operations ONLY to your OWN Institutional Admins
  • None:
    • Only included to explicitly define items with missing or undefined condition can only be accessed by APTrust Admins for troubleshooting purposes.

AccessPermissionGrid


Auditing

APTrust will use a subset of fields from the PREMIS metadata schema to record and report event metadata.

Details about the following events should be captured and registered with the Administrative Interface:

  • Ingest
  • Fixity Generation
  • Fixity Check
  • Deletion
  • Identifier Assignment

Premis Events Data Structure

The following subset of PREMIS fields are used to record the event actions and outcomes covered by our auditing requirements.

PREMIS Events Metadata

PREMIS Event Examples

The following are some basic examples of entries for the various PREMIS events tracked in APTrust.

PremisEvents Examples


Comments