HM-Yale Branch Descriptions

                                         HM/Yale Branches for Merger into ArchivesSpace

DRAFT DOCUMENTATION

Mike Rush

2014-07-30

Some additional background information can be found on the HM/Yale Pivotal site: https://www.pivotaltracker.com/s/projects/1061368.  

fix-core-plugin-initializer

Fix a bug where plugins weren’t being correctly loaded when running under Windows.

advanced-search-changes-for-core

Introduce advanced search to the staff interface.  Generalize the way advanced search fields are defined and modifies the public and staff applications to use the new mechanism.

In the staff interface, an advanced search can be initiated by clicking on the down arrow button to the right of the basic search box.  This drops down the advances search interface, which by default includes a single text search box, set to keyword.  There is an option to make it a not search. To the right is a red delete button to remove that search option.

There is also a green button to the right, which gives you a choice of adding a Text, Date, Boolean, or Controlled Value line to your search.  All search terms after the first can be added as either AND, OR, or NOT.

accession-to-accession-relationships

Data model change: allow accessions to link to one another with configurable relationship types.

Within an accession record, there is a new subrecord area, called “Related Accessions.”  If a user clicks on “Add Related Accession,” they are first prompted to select a “Relationship Type”.  There are two options: “’Part of’ Relationship” and “Sibling Relationship”.  

When the “’Part of’ Relationship” is selected, the “Part of” Relationship subrecord appears.  There are three subfields: “This Accession,” “Accession,” and “Relator Type.”  There are two possible values for “This Accession”: “Forms Part Of” and “Has Part”.  These values are reciprocal.  If Accession 1 has part Accession 2, then Accession 2 forms part of Accession 1.  “Relator type” is a way to further characterize the nature of the relationship. It has a default value of “’Part’ Relationship.”  Part of relator types can be edited in the controlled value list Accession Parts Relator Type (accession_parts_relator_type).

When the “Sibling Relationship” is selected, the Sibling Relationship subrecord appears. The same three subfields are present.  For Sibling relationships, there is only one value for “This Accession:” “Is Sibling of.”  This relationship is reciprocal as well.  If Accession 1 is sibling of Accession 2, then Accession 2 is sibling of Accession 1.  The default value for Relator Type is “’Bound with’ relationship.”  Sibling relator types can be edited in the controlled value list Accession Sibling Relator Type (accession_sibling_relator_type).

test-for-missing-translations

Small change: improves test coverage of translations, such that the frontend unit tests fail if a developer forgets to add a translation.

spawn-accession

Supports spawning a new accession record from an existing accession record.  When viewing or editing an existing Accession, the “Spawn” menu now has “Accession” as an option (in addition to “Resource”).  Selecting Spawn > Accession will create a new accession and copy some information from the current accession record to a new one.  All Basic Information is copied except for the identifier and accession date.  Other sections copied to the new record include the following: Dates, Extents, Agent Links, and Subjects.  Sections not copied to the new record include Related Resources, Related Accessions, External Documents, Rights Statements, Instances, Deaccessions, Collection Management, and Classifications.

marc-2-accession-rebased

Supports the import of MarcXML records as Accessions rather than Resources. In the “New Import Job” interface, there is a new “Import Type” option, “MarcXML (Accession)”.  MarcXML records imported using this option will create new accession records.  The import mapping is as follows:

These mappings were drawn largely from the MarcXML > Resource mapping.  The only change was adding the 5XX fields.  For those fields, all subfields are included.

Also: the “MarcXML” option in the “Import Type” list has been renamed “MarcXML (Resource).”

permissions-by-record-type

This existing permission:

- create/update accessions, resources, archival objects and digital objects in this repository

Becomes three new permissions:

- create/update accessions in this repository

- create/update resources in this repository

- create/update digital objects in this repository

Where Resources includes 'Archival Objects' and Digital Objects includes Digital Object Components.

There are two new permissions:

- initiate import jobs

- create/update/delete vocabulary records [This is currently permitted under the create/update major record types permission, but should really have its own permission.]