[Archivesspace_Users_Group] issues with MARCXML import to AS

[AAR Website]

For clarification, in case anyone else needs it. The identifier is built
from the 852$ k,h,i and m subfields, not 856$. Line 532 in
https://github.com/archivesspace/archivesspace/blob/master/backend/app/converters/lib/marcxml_base_map.rb



On Mon, Apr 21, 2014 at 6:56 AM, Chris Fitzpatrick <
Chris.Fitzpatrick at lyrasis.org> wrote:

>
>  Hi Jason,
>
>
>
>  We have actually done quite a bit of work recently on agents and agent
> names, particularly to ensure that name values are unique. This will all be
> included in the next release (v1.0.9) that should be out shortly.
>
>
>  In regards to the identifier issue, looking at the MARCXML importer (
> https://github.com/archivesspace/archivesspace/blob/master/backend/app/converters/lib/marcxml_base_map.rb#L530-L542
>  )
>
>
>  The identifier is being built by the first concating the 856$k, 856$h,
> 856$i , and 856$m. If there are no values there, it uses values from the
> 090 field. If there are not any values in that field, it generates a random
> string, which is what you are seeing you your records.
>
>
>  If you want to customize the id that is being generated by the MARCXML
> importer, you can modify the marcxml_base_map.rb file in a plugin. Let me
> know if you need any help with that and I can write something to show you
> how to get started on that...
>
>
>  b,chris.
>
>
>
>
>
>
>  Chris Fitzpatrick | chris.fitzpatrick at lyrasis.org
> Developer, ArchivesSpace
> http://archivesspace.org/
>   ------------------------------
> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org <
> archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of AAR
> Website <website at aarome.org>
> *Sent:* Friday, April 18, 2014 1:31 AM
> *To:* archivesspace_users_group at lyralists.lyrasis.org
> *Subject:* [Archivesspace_Users_Group] issues with MARCXML import to AS
>
>  I am having trouble understanding the import process from MARCXML to
> AS.
>
>  Beginning with the simplest possible use-case:
>
>  1. I have 2 MARCXML records that describe 2 separate archival resources.
> Both record 1 and record 2 contain markup referring to the creator and
> former owner of their respective archival resources.
>
>      <datafield ind1="1" ind2=" " tag="100">
>       <subfield code="a">Smith, John</subfield>
>       <subfield code="e">creator</subfield>
>     </datafield>
>
>      <datafield ind1="1" ind2=" " tag="700">
>       <subfield code="a">Doe, Jane</subfield>
>       <subfield code="e">former owner</subfield>
>     </datafield>
>
>  Following import, my agent list contains two (2) instances each of John
> Smith and Jane Doe.
>
>  What's happening there?
>
> Successive imports containing either John Smith or Jane Doe add additional
> ids and rows to the name_person mysql table. In other words, it appears
> that during the import process there's no validation routine against
> human-readable values. Is there an additional marker or indicator I can
> enrich the metadata with to indicate that it is a controlled value in the
> agent list?
>
>  2. Each record has a unique identifier that's relevant to the
> organization's administrative cataloging system, that is, a series of
> locally developed pseudo-call numbers. Here's an example:
>
>      <datafield ind1=" " ind2=" " tag="852">
>       <subfield code="a">Repository: name</subfield>
>       <subfield code="b">name of collection</subfield>
>       <subfield code="c">NVB.0028.H-30.M.XLV.12A-13A</subfield>
>     </datafield>
>
>  Following import, the value contained by the 852$c tag is replaced with
> a hash:
>
> imported-43bf7690-4aa6-471d-a3a1-21e18f9002c7
>  Is this desired behavior?
>
>  Any clarification would be appreciated.
>
>  Best regards,
>
>  Jason Loeffler
> American Academy in Rome
>
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20140531/47888958/attachment.html>