Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

EAD3 exporter should use daoset when there are multiple file versions in a digital object

Description

EAD3 dropped the daogrp and daolink elements that were in EAD2002. The EAD3 exporter in ArchivesSpace correctly does not use those elements, as the EAD2002 exporter does when there are multiple file versions in a digital object. Instead it output multiple dao elements as children of the linked record's did element. That is valid, but not ideal. It means there aren't locations to map both the captions on individual file versions and the title of the parent digital object.

However, daoset has a mandatory attribute coverage attribute, which might require a change to the ArchivesSpace data schema for digital objects.

Complexity

None

Activity

Show:

Angela White September 16, 2021 at 4:59 PM

Passed based on Metadata’s recommendation.

Valerie Addonizio September 16, 2021 at 3:23 PM
Edited

Metadata Standards reviewed this ticket and specifically reviewed the fact that this behavior is supported for EAD2002 exports. Since the precedent was set for this in EAD2002, Metadata agrees that this functionality should be added to EAD3 for consistency. We approve and suggest it be passed.

Maggie Hughes January 5, 2021 at 6:36 PM

Dev Pri reviewed this ticket in their January 2021 meeting and recommends that Metadata Standards review and approve before passing.

Andrew Morrison February 18, 2020 at 3:49 PM

Just to note that the web site I referenced in the above comment is incorrect about daoset requiring a coverage attribute. It is optional.

Details

Assignee

Reporter

Labels

Priority

Parent

Harvest Time Tracking

Open Harvest Time Tracking

Created February 18, 2020 at 12:05 PM
Updated September 16, 2021 at 4:59 PM
Harvest Time Tracking