Feature #4518

EAC/EAD export should should uniquely identify the source of <biogHist>

Added by Jesús García Crespo over 9 years ago. Updated almost 9 years ago.

Status:DuplicateStart date:01/09/2013
Priority:MediumDue date:
Assignee:José Raddaoui Marín% Done:

100%

Category:EAC - Import/ExportEstimated time:2.00 hours
Target version:Release 1.4.0
Google Code Legacy ID: Tested version:
Sponsored:No Requires documentation:

Description

After reviewing the notes on this issue from the CCAD review, it appears that they identify a problem with EAC and EAD export. The exports should have URI/URL (to clarify).

We need to uniquely identify the origination of the <biogHist> to prevent accidently sharing the same biographic history between two distinct entities that share the same name, or in the case of union lists, preserve different biographic histories for the same entity which are maintained by two different institutions.

For AtoM instances, we will use the URL of the original authority record in the EAD and EAC representations to differentiate two or more <biogHist> for enitities that share the same name, or distinct <biogHist> for the same entity.


Related issues

Duplicates Access to Memory (AtoM) - Bug #4267: EAC and EAD export have URI for Authority Records Feedback

History

#1 Updated by Dan Gillean about 9 years ago

  • Assignee changed from David Juhasz to José Raddaoui Marín

#2 Updated by José Raddaoui Marín almost 9 years ago

  • Status changed from New to QA/Review
  • % Done changed from 0 to 100

Using md5 hash. See update 9 in #4845

Applied in changeset atom|commit:04964c4d09aa3cc98c848cdc344fcec3580d61da

#3 Updated by Jesús García Crespo almost 9 years ago

  • Estimated time set to 2.00

#4 Updated by Jessica Bushey almost 9 years ago

I created two authority records for the same corporate body, one is attached to an archival description and therefore associated with an archival institution; but the other authority record is not associated with any institution or archival description.

Checking the EAC.XML export for each record provides the following:

<biogHist id="md5-7d4acc0f9267cd37135e213d04cb67bc"><p>Brothers that founded a studio that makes television shows and movies.</p></biogHist>

and

<biogHist id="md5-36fa239af8a9f4e466818e9b7e8b1b1c"><p>Started in 1900 by three brothers.</p></biogHist>
-This authority record is associated with an archival description and therefore an institution:
<publicationStatus>approved</publicationStatus><maintenanceAgency><agencyName>HTVA</agencyName></maintenanceAgency>

Two tests:

1) Export archival description EAD.XML that has the associated authority record.
2) Delete archival description.
3) Import archival description and AtoM properly associates the correct authority record.

UNFORTUNATELY,
1) If I export the archival description EAD.XML that has the associated authority record.
2) Delete archival description.
3) Export associated authority record EAC.XML
4) Delete authority record.
3) Import archival description.

AtoM DOES NOT populate the database with the associated authority record. Instead, it grabs the existing authority record (which is not associated with any archival description or institution) and makes that the associated authority record. This is evident by having a slightly different biographical history for the two authority records, and seeing that AtoM overwrites the original bioghist with the one that exists for the authority records already sitting in the database.

I think this is a problem for multi-institution portals....

#5 Updated by David Juhasz almost 9 years ago

Jessica, the behaviour you are describing is correct, but the original issue description is wrong. The md5 hash is being generated from the URL of the authority record, not the institution that controls the authority record as was described in the issue description. We need to use the authority record URL because the @id attribute value must be unique within the EAD/EAC document, which is not the case if we use the institution identifier - i.e. there will often be several authority records within an EAD document that are controlled by the same archival institution.

I'll update the issue description appropriately.

#6 Updated by David Juhasz almost 9 years ago

  • Tracker changed from Bug to Feature
  • Subject changed from EAC/EAD export should use URI for institution to EAC/EAD export should should uniquely identify the source of <biogHist>
  • Description updated (diff)

#7 Updated by David Juhasz almost 9 years ago

  • Description updated (diff)

#8 Updated by Jessica Bushey almost 9 years ago

  • Status changed from QA/Review to Feedback

#9 Updated by David Juhasz almost 9 years ago

  • Status changed from Feedback to Duplicate

Also available in: Atom PDF