[Archivesspace_Users_Group] NACO versus LCNAF

[Steven Majewski]

> On Sep 23, 2015, at 12:54 PM, Susan Luftschein <luftsche at USC.EDU> wrote:
> 
> Hi Karla,
> We are using NACO. I began using NACO for rules because LCNAF was being exported as a subfield 2 with a second indicator of 7.  In the subfield 2 was “Library of Congress Name Authority File”.  I’m pretty sure I reported this at the time (there are still other issues with the MARC export), so I just switched to using NACO (which exports the same way).
>  
> If something has been fixed, I’d appreciate knowing!  (Thanks in advance Chris!).
>  
> Sue


Well, there is something that needs to be fixed. 

locales enum file https://github.com/archivesspace/archivesspace/blob/master/common/locales/enums/en.yml#L286-L295 <https://github.com/archivesspace/archivesspace/blob/master/common/locales/enums/en.yml#L286-L295>, https://github.com/archivesspace/archivesspace/blob/master/common/locales/enums/en.yml#L419-L431 <https://github.com/archivesspace/archivesspace/blob/master/common/locales/enums/en.yml#L419-L431> translates these abbreviations into strings in user interface.  Abbreviated values are initial values in controlled value list, and if you select one of those values from the menu when creating a agent or subject, the menu show the long string, but I believe the value used is the abbreviated symbol. 

However, if you import MarcXML agents or subjects, MarcXMLBaseMap https://github.com/archivesspace/archivesspace/blob/master/backend/app/converters/lib/marcxml_base_map.rb#L4-L25 <https://github.com/archivesspace/archivesspace/blob/master/backend/app/converters/lib/marcxml_base_map.rb#L4-L25>
uses full strings, not abbreviations, so it creates a duplicate looking record that will need to be merged.

Values will read the same in the user interface and menus, but will actually be different and (I believe) export differently. 

[ Yes- there are a whole bunch of other issues with MarcXML import & export. It’s not assigning authority_ids to resources for another example. ]

— Steve. 


>  
> Sue Luftschein
> Archival and Metadata Librarian
> USC Libraries
>  
> Sent using CloudMagic <https://cloudmagic.com/k/d/mailapp?ct=pi&cv=6.4.27&pv=8.4>
>  
> On Tue, Sep 22, 2015 at 4:29 PM, Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org> wrote:
> I have a general question for the group. When creating agent records, are you using the NACO (as provided by ArchivesSpace) or have you added LCNAF to your name_source controlled value list and are using that as your preferred term? 
>  
> We had some EAD legacy data import using LCNAF, which automatically created the LCNAF value. We will have to merge to one or the other, but we would like to hear what others are doing. I recall that Archivists' Toolkit used LCNAF instead of NACO so I imagine we have not been the only institution with this issue.
>  
> Thank you!
>  
> -- 
> Karla Irwin
> Special Collections Technical Services Librarian
> University Libraries, University of Nevada, Las Vegas
> karla.irwin at unlv.edu <mailto:karla.irwin at unlv.edu>
> (702) 895-2245
> _______________________________________________
> 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/20150924/c953a13f/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4943 bytes
Desc: not available
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20150924/c953a13f/attachment.bin>