Tufts University Logo SITE_NAME

Search  GO >

this site tufts.edu people
SITE_NAME SITE_NAME SITE_NAME  
 
SITE_NAME SITE_NAME 6
Printer-friendly version

Deliverables

The deliverables for the TAPER project are associated with two major tasks that the DCA described in its revised plan of work: Create a submission agreement builder tool and produce records context records.

Submission Agreements

The DCA developed two types of submission agreements that work together to generate machine-readable documentation of archival transfers. A standing submission agreement defines the terms and conditions of a specific records creator transferring a specific type of records to an archives. A regular submission agreement documents the specific transfer instance, inheriting the terms and conditions of the corresponding standing submission agreement and adding details specific to a particular transfer, such as the date of transfer and the extent of materials.

The DCA created four deliverable components for the submissions agreement: a set of XML schemas, a submission agreement builder tool (SABT), a Fedora Commons content model, and user instructions. The DCA uses the schemas, SABT, and user instructions as production tools. The DCA does not use the content model because its manages its completed submission agreements in its collections management tool rather than its Fedora Commons-based repository as originally intended. All four deliverables are available for free use and modification.

1. Submission agreement XML schema
Standing Submission Agreement Schema
Regular Submission Agreement Schema
Standing and Regular Common Elements Schema
All three schemas listed at http://dca.lib.tufts.edu/schema/er/.

2. Submission agreement builder tool (SABT)
SABT code

3. Submission agreement content model
Fedora Commons content model for submission agreements

4. Submission Agreement & SABT Instructions
The DCA uses the term “Transfer Agreement Form” at Tufts as a more user-friendly and intuitive term of art than “submission agreement builder tool” or “submission agreements.”

For Tufts employees: Using the Tufts University Transfer Agreement Form
Video | PDF Instructions

For archivists: Setting up Tufts University Transfer Agreement Forms
Video | PDF Instructions

For archivists: Finalizing the Tufts University Transfer Agreement Form
Video | PDF Instructions

Records Context Records

The DCA uses EAC-CPF to encoded its records context records. The DCA uses the EAC standard as a production-level tool to encode its description of entities and people. It also produced local procedures for encoding records context records in EAC.

By the close of the TAPER Project the DCA had created 51 EAC-encoded records context records.

1. Records context record XML schema
The DCA adopted EAC-CPF for its RCR XML schema.

2. Records context record builder tool
The DCA uses its collections management tool to create RCRs.

3. Records context records content model
Fedora Commons content model for records context records.

4. Records context records procedures.
These are local procedures that meet the particular needs of the DCA. While these procedure may be a useful illustration of how one archives implements EAC, these procedures are not designed to serve as a de-facto set of EAC best practices for the archival community.
DAT-040 DCA Best Practices for EAC
PRO-001 Writing an authoritative history of Tufts Units
PRO-002 Writing an authoritative biography