Feature

As an Archivist, I would like to be able to link AOs to existing digital objects (DOs) when using the bulk import or update spreadsheets.

Background

We create digital objects during the accession process. When processing a collection, we often want to link newly-created AOs to the existing DOs created during accessioning. So far this has been a many-to-one/few relationship (all of the new AOs are linked to 1-5 existing DOs).

Top containers already display the desired behavior. For example, when uploading a bulk-import spreadsheet, “the ingester will try to find an already-created Top Container in the database” before creating a new one (source). Until today, I had assumed that the same held true of DAOs, since both are instances of AOs.

Behavior scenarios

Scenario: As an Archivist, I want to be able to link to existing DOs when importing new AOs

Given that a DO already exists

When its identifier is entered in the digital_object_id column of the AO bulk import spreadsheet

Then upon the AO’s creation, it should be linked to the DO

But a new DO should not be created

Scenario: As an Archivist, I want to be able to link to existing DOs when updating AOs in bulk

Given that a DO already exists

When its identifier is entered in the digital_object/0/digital_object_id column of an AO bulk update spreadsheet

Then the corresponding AO should be linked to the DO

But a new DO should not be created