search

SAA-SDT / EAD3

https://www.loc.gov/ead/index.html
Creative Commons Zero v1.0 Universal
81 stars 25 forks source link

<dao> lacks place to record identifier; <relation> could not serve this purpose #401

Closed rockivist closed 9 years ago

rockivist commented 10 years ago

Submitted on Friday, February 28, 2014 - 2:55pm Submitted values are:

Name: Kate Bowers Affiliation: Harvard University Library Does this represent an official comment from your affiliated group? Yes Comment: <dao> lacks place to record identifier; <relation> could not serve this
purpose.

Harvard's third revision comment requested a means to record the digital
archival object identifier. This would contain either a mechanism for
identifying the system in which an object is stored and its system identifier
or a URN that could do both (separate from a delivery URN).

<relation> has the data elements that might be used for such a purpose (see
example below) but it cannot serve this purpose because each <dao> would need
its own identifier and is not valid under <dao>. <relation>
expresses a relationship with the unit of description. Since a digital
object is not necessarily equivalent to the unit of description, there is not
a one-to-one relationship between them. Multiple <dao>s may exist within a
<daoset> within a single component.

`<relation relationtype="otherrelation"
otherrelationtype="digitalObjectIdentifier">

3962141

`

Note: I still think it would be a good idea to be able to record digital
object identifiers for each <dao> in EAD; however, our local need has been
reasonably met by assigning unique EAD component identifiers across all our
EAD instances which can be recorded as part of the digital object's metadata
in our digital repository. The many-to-one possible relationship between
digital objects and components is thus resolved for us.

The results of this submission may be viewed at: http://www2.archivists.org/node/17190/submission/15486

rockivist commented 10 years ago

On the 2014-03-07 TS-EAD conference call @tcatapano suggested adding @identifier to <dao> in order to support assigining non-URL URIs for digital objects. After reviewing the comment above, I support the change.

rockivist commented 10 years ago

Per 2014-03-21 TS-EAD conference call, add @identifier as a optional attribute to <dao>.

rockivist commented 10 years ago

Implemented. Assigning to @kshepher for documentation review.

kshepher commented 9 years ago

TL updated.