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


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.


Andrew Morrison
February 18, 2020, 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.

Maggie Hughes
January 5, 2021, 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