The following specifications were used to guide work during the development/build phase.

• System Overview (not an official spec but a summary of information in the ones linked below)
• High-Level Functional Requirements

Detailed specifications for:

Main Modules:
represent the most important functional areas of the application and are the areas where most staff and public users will interact with the system

1. Archival Object Specification (March 23, 2012 draft)
2. Accessions (September 23, 2011 draft) / Deaccessions Specification (November 8, 2011 draft)
3. Resource Specification (November 14, 2011 draft)
4. Digital Object Specification (October 11, 2011 draft)

Supporting Modules:
allow for the creation of  supporting records that sit in many-to-many relationships with accession resource, resource components, digital objects, and digital object component records.

1. Agent Specification (March 23, 2012 draft; replaces name specification)
2. Repository Specification (September 11, 2011 draft)
3. Staff User Specification (September 11, 2011 draft)
4. Location Specification (September 11, 2011 draft)*
5. Subject Specification (September 12, 2011 draft)
6. Event Specification (March 23, 2012 draft)

Sub-Record Definitions:
can be created only in the context of an open accession, resource, or digital object record, and they are linked to the parent record in a one-to-one relationship.

1. Date Specification (April 4, 2012 draft)
2. Extent Specification (September 26, 2011 draft)
3. External Document Sub-Records (November 14, 2011 draft)
4. Rights Management Specification (March 23, 2012 draft)
5. Collection Management Specification (March 23, 2012 draft)

Interface Design Principles

Technical Discussion Documents/Position Pieces

1. Provisional Data Model (November 7, 2011 draft)
2. Position Statement on Multitenancy (November 11, 2011 draft)
3. Position Statement on Reporting (March 23, 2012 draft)
4. Position Statement on Deployment (March 23, 2012 draft)