Additional comments re: <otherrecordid>

[rockivist]

Submitted on Monday, August 26, 2013 - 1:17pm
Submitted values are:

Name: Kate Bowers
Affiliation: Harvard University
Does this represent an official comment from your affiliated group? Yes
Comment:

1. Please make <otherrecordid> legal in <c> and<c#>`

I was happy to see this concept included in EAD3, but our original proposal
was for a an element more broad in meaning, closer to the MARC 035 field than
what now appears to be its use in EAD3, but with the difference that it would
identify any other valid descriptions, not necessarily 'the same record' in
the other system.

We are hopeful that I'll be able to use this in any <c> to place system
numbers for analytic descriptions of the same component so that they can be
interchanged with other systems. For example, we have graphic materials
described in a separate system. In order to make data sharing between
systems possible, we need to store the database identifiers for the component
metadata from other systems. Metadata may move from the graphic catalog into
a finding aid, or from finding aids into the graphic catalog. I hope it is
obvious that having the database identifier of the foreign database is key to
interoperabilty/interchange of this kind.

2. I sent this comment in, I'm pretty sure, in response to the Alpha testing.
   I'm not sure if it was considered and rejected, or simply not considered in
   the flurry of activity. If it was considered and rejected, could you explain
   why?

3. Please review the tag library and consider the text I suggest below,
   especially if <otherrecordid> is made valid in <c>s.

(Also, I'm lower-casing the element your existing example)

START OF TAG LIBRARY TEXT SUGGESTION_______________

<otherrecordid>

Other Record Identifier

Description:

Use <otherrecordid> to encode associated, additional, related, or alternative
record identifiers for records that describe the same unit of description.

Within <control>, this presents alternatives to the mandatory identifier in
<recordid>. These might include identifiers from systems used to generate the
EAD instance or that are no longer current but had some part in the history
and maintenance of the EAD instance and identifiers from systems in which
associated records exist, such as bibliographic database record numbers for
MARC records that describe the same collection that the EAD instance
describes.

Within <c>, this presents alternatives to the identifer encoded as the @id
attribute value. These might include identifiers from systems used to
generate the component metadata and identifiers from systems in which
associated records exist, such as bibliographic database record numbers for
MARC records that describe the same component that the EAD <c> describes or
ArtStor record numbers for graphical resources.

The @localtype attribute can be used to identify the kind of institution or
service responsible for each associated record identifier if not the same as
that given in the <maintenanceagency> element for this EAD instance.

Examples:

`
mferd907e3
http://hdl.loc.gov/loc.mss/eadmss.ms001033
,,,

008490961 ... olvwork365152 ... `

END OF TAG LIBRARY TEXT SUGGESTION_______

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

[rockivist]

See also #166

[rockivist]

My inclination is not to add <otherrecordid> at the component level. To address this use case, however, I would recommend the use of <relation>. Just a preliminary thought.

[rockivist]

I discussed this on the phone with Kate Bowers on 2013-12-04. I suggested and she agreed that this was a good potential use of <relation>.

Closing.