[Archivesspace_Users_Group] Error with import of EAD <index> element data

[Dallas Pillen]

Hi Megan,

We noticed a similar issue with our <indexentry> elements being split into
separate index items when importing from EAD. The reason seems to be with
this block of code in the EAD Converter:

https://github.com/archivesspace/archivesspace/blob/master/backend/app/converters/ead_converter.rb#L273-305

This imports <persname>, <corpname>, etc. elements from within each
<indexentry> element as one index item, and each <ref> element as a
separate item.

We put together this plugin that imports each <indexentry> element as one
index item, with the Value, Type, and Reference Text as you described:

https://github.com/bentley-historical-library/bhl-ead-importer/blob/master/backend/model/bhl_ead_converter.rb#L38-121

We've only tried it out with a few EADs so it might not work 100% of the
time, but we've had some preliminary success with it so far. It might be
worth a shot!

Dallas


On Wed, Mar 18, 2015 at 4:07 AM, Megan Williams <MWILLIAM at nla.gov.au> wrote:

>  We have many EAD finding aids that we’re intending to import into
> ArchivesSpace.  Generally this is working very well, except for any finding
> aids that have an <index> element, e.g.:
>
> <index>
> <indexentry>
>   <persname>DEGARIS, Leo</persname><ref>emph
> render="underline">1/9459</emph></ref>
> </indexentry>
> <indexentry>
>   <persname>DELMONT, S.R.</persname><ref>1/2369, <emph
> render="underline">1/2370</emph>, 4/22</ref>
> </indexentry>
> </index>
>
> When we import this data into ArchivesSpace, we’re expecting that each
> <indexentry> element will translate into an Index note entry containing a
> Value (derived from the name element content), Type (derived from the type
> of name element) and Reference Text (derived from the <ref> element
> content).  Instead, we’re finding that each <indexentry> element is being
> split into two separate entries, one with the name element content and type
> in the Value and Type fields respectively, followed by one with the <ref>
> content repeated in the Value and Reference Text fields.
>
> For example, the encoded data given above was imported as:
>
>
> Instead of:
>
>
> I’m not sure if this is a known issue (forgive me if it’s been raised
> before) – but we’d appreciate any advice/assistance!
>
> With thanks,
>
> Megan
>
> *Megan Williams* *|* A/g Assistant Curator *|* Pictures & Manuscripts
> Branch *|* National Library of Australia* |* Canberra ACT 2600
>
>
>
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
>


-- 

*Dallas Pillen*Project Archivist


  Bentley Historical Library <http://bentley.umich.edu/>
  1150 Beal Avenue
  Ann Arbor, Michigan 48109-2113
  734.647.3559
  Twitter <https://twitter.com/umichBentley> Facebook
<https://www.facebook.com/bentleyhistoricallibrary>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20150325/57bc85ec/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Picture (Device Independent Bitmap) 2.jpg
Type: image/jpeg
Size: 9463 bytes
Desc: not available
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20150325/57bc85ec/attachment.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Picture (Device Independent Bitmap) 1.jpg
Type: image/jpeg
Size: 15892 bytes
Desc: not available
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20150325/57bc85ec/attachment-0001.jpg>