Bug #5209

Add support for <extref> EAD tag on AtoM import

Added by Dan Gillean almost 9 years ago. Updated almost 9 years ago.

Status:Won't fixStart date:06/10/2013
Priority:MediumDue date:
Assignee:José Raddaoui Marín% Done:

0%

Category:EAD
Target version:Release 1.4.0
Google Code Legacy ID: Tested version:
Sponsored:No Requires documentation:

Description

Currently attempts to import an EAD record that includes an <extref> will drop the link contained in the EAD tag.

Description of the <extref> element from the EAD Tag Library (2002)

A linking element that can include text and subelements as part of its reference to an electronic object that is external to the EAD document.

Use the ENTITYREF or HREF attribute to identify the external object.

Use the <ref> element to point to another location within the EAD document.

While XML Linking Language (XLink) Version 1.0, which is the basis for EAD linking elements, is a stable document, examples of EAD usage are hypothetical and have not been tested in real XLink-based applications. Those wishing to use XLink are encouraged to consult the specification available online at <http://www.w3.org/TR/xlink/>.

My recommendation is that it will be extremely complicated to support @ENTITYREF attributes when importing into AtoM. Our main goal is not to lose links included using @HREF. AtoM cannot at this time support complex XLink telationships, so when encountering an <extref> element nested inside another element, AtoM will simply pull out the URL and place it in the description, in the related element's field in ISAD etc. The end user can then make decisions about presentation (i.e., whether to shorten the URL, whether to add a line break before or after it, whether to move it to the bottom of the description, etc.).

History

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

Hi Dan,

Where should I look for it?

The EAD Tag Library says that it can be inside: "abstract, archref, bibliography, bibref, container, creation, descrules, dimensions, emph, entry, event, extent, item, label, langmaterial, langusage, materialspec, origination, otherfindaid, p, physdesc, physfacet, physloc, ref, relatedmaterial, repository, separatedmaterial, unitdate, unitid and unittitle".

Should I search it inside all? Or only inside events, for authority records, and inside unitdate, unitid or unittitle (for example, I don't really know) for archival descriptions.

Also, did you mean description identifier field for saving the value?

Thanks! :)

#2 Updated by Dan Gillean almost 9 years ago

  • Status changed from New to Won't fix

Hi Radda,

Sorry, I hope you haven't started working on this yet. This issue was based on a review of EAD import for a client. After reviewing the complications of implementing <extref> support throughout AtoM via EAD, we spoke further with the client, and it turns out they were only using it in one record. Consequently, they have decided to change how they import that one bit of information.

In light of this, and all the potential complications with all the different ways that people could try to use <extref> elements, I am going to mark this issue as "won't fix" for now, unless we receive strong feedback from our community that support for this is important.

Thanks, and sorry for the confusion.

Also available in: Atom PDF