[Archivesspace_Users_Group] marcxml import/export mappings

Maderik, Rachel A. maderikra at vmi.edu
Mon Sep 8 07:50:12 EDT 2014

Hi Ben, we also had this problem when importing MARCXML records (all of our call numbers were in the 099 field). I reported it on PivotalTracker in July (https://www.pivotaltracker.com/story/show/75698122), but in the meantime you could do a search and replace on the MARC records before importing, changing 099 to 090 (that was what I did to get them to import).

Rachel Maderik
Metadata Librarian
401 Preston Library
Virginia Military Institute
Lexington, VA 24450

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Ben Goldman
Sent: Friday, September 05, 2014 4:21 PM
To: Archivesspace Users Group
Subject: [Archivesspace_Users_Group] marcxml import/export mappings


We have been testing the MARCXML importer in ASpace, and found that, despite ASpace mapping Resource identifiers to MARC 099 on export, it does not map 099 to resource identifier on import. Is there a reason for this? If so, is there a recommended way to ensure that resource records created using this method get the appropriate local collection number assigned?


Ben Goldman
Digital Records Archivist
Penn State University Libraries
University Park, PA

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20140908/5adfc920/attachment.html>

More information about the Archivesspace_Users_Group mailing list