[Archivesspace_Users_Group] marcxml exporter plugin

Brad Westbrook brad.westbrook at lyrasis.org
Thu Aug 11 14:03:26 EDT 2016

Hi, Francis,

I think some deviations from the base MARCXML map occurred before the 1.0 release and some subsequently.  None of the deviations were documented in user stories but not in the base map.

I would think the goal would be to construct a human readable map that indicates how AS should export to MARCXML, and import MARCXML, and the update the importers/exporters accordingly.


From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Lapka, Francis
Sent: Thursday, August 11, 2016 1:54 PM
To: archivesspace_users_group at lyralists.lyrasis.org
Subject: Re: [Archivesspace_Users_Group] marcxml exporter plugin

Thank you Steven. That file is precisely what I hoped to find.

It looks like AS code deviates from the mapping described in the Excel file (perhaps because of changes made in the intervening three years?). To name one example, the exporter maps values for language of the resource to MARCXML fields 040 $b and 049 $a – which is an error (for 040 $b, at least). Such mappings are not described in the 2013 Excel file. I assume the mapping is the outcome of lines 631-634 in export_marc_spec.rb:

it "maps resource language code to 040$b and 049$a" do
      @marc.at("datafield[@tag='040'][@ind1='0'][@ind2=' ']/subfield[@code='b']").should have_inner_text(@resource.language)
      @marc.at("datafield[@tag='049'][@ind1='0'][@ind2=' ']/subfield[@code='a']").should have_inner_text(@resource.language)

So probably it’s fair to say that we don’t have a human-readable mapping that reflects the performance of the current AS MARC exporter? Perhaps my goal should be to revise the Excel file to reflect changes made?



Majewski, Steven Dennis (sdm7g) sdm7g at eservices.virginia.edu <mailto:archivesspace_users_group%40lyralists.lyrasis.org?Subject=Re%3A%20%5BArchivesspace_Users_Group%5D%20marcxml%20exporter%20plugin&In-Reply-To=%3C0269F401-8AFF-4640-A5BC-19AB002DCCB2%40eservices.virginia.edu%3E>
Thu Aug 11 13:06:19 EDT 2016



on page: http://archivesspace.org/importexport

From: Lapka, Francis
Sent: Thursday, August 11, 2016 1:01 PM
To: 'archivesspace_users_group at lyralists.lyrasis.org' <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: marcxml exporter plugin

As one component of a larger project at Yale, I am considering a review of ArchiveSpace’s MARCXML exporter, with the intention of recommending changes to the spec so that it is in full compliance with descriptive conventions in MARC. As noted in the thread below, there are “issues” – at a glance, quite a few. I’m aware that some issues are registered in JIRA (e.g., AR-1189, AR-1187, …). The goal would be to draft a document that comprehensively and precisely documents how AS should map to MARC, for all AS “Resource” fields.


1.       Are there any human-readable documents that already specify the mapping from AS to MARCXML (something other than the export_marc_spec.rb that I find on Github)?

2.      Is anyone else undertaking a similar project (I’d be happy to spare myself the trouble)?

3.      Bonus question: Is anyone planning/devising a spec for mapping from AS to BIBFRAME 2.0?

Answers to any of these questions would be much appreciated.


Francis Lapka  ·  Catalog Librarian
Dept. of Rare Books and Manuscripts
Yale Center for British Art
203.432.9672  ·  francis.lapka at yale.edu<mailto:francis.lapka at yale.edu>


Susan Luftschein luftsche at usc.edu <mailto:archivesspace_users_group%40lyralists.lyrasis.org?Subject=Re%3A%20%5BArchivesspace_Users_Group%5D%20marcxml%20-%20OCLC%20and%20Symphony%0A%09%28catalog%09database%29&In-Reply-To=%3CSN1PR07MB2414536D6BB4501B6B57810DD3BE0%40SN1PR07MB2414.namprd07.prod.outlook.com%3E>
Fri Mar 4 16:36:10 EST 2016

  *   Previous message: [Archivesspace_Users_Group] marcxml - OCLC and Symphony (catalog database)<http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/2016-March/003255.html>
  *   Next message: [Archivesspace_Users_Group] marcxml - OCLC and Symphony (catalog database)<http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/2016-March/003268.html>

Hi Johna,

I do it all the time.  You can export a resource record as MARCXML.  You do it through the Export tab in the top level of the resource record.  I do use OCLC Connexion to catalog, so if that’s what you want to do you have to transform the xml file into MARC21 format.  Terry Reese’s MarcEdit program (free) will allow you to do that.  Then you can just import the transformed MARC record into Connexion.

Be aware that there are still some mapping issues with ASpace elements and MARC fields, so you definitely have to do some manual editing.

Hope this helps,


Sue Luftschein

Archival and Metadata Librarian

USC Libraries Special Collections

University of Southern California

Doheny Memorial Library

3550 Trousdale Parkway, Room 207

Los Angeles, CA 90089-0189



luftsche at usc.edu<http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group><mailto:luftsche at usc.edu<http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group>>

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org<http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group>] On Behalf Of Johna L Von Behrens

Sent: Friday, March 04, 2016 12:48 PM

To: Archivesspace Users Group

Subject: [Archivesspace_Users_Group] marcxml - OCLC and Symphony (catalog database)

Good afternoon AS Users,

We have records in AS that we would like to export and put into OCLC and our catalog.

Has anyone exported a marcxml record and then imported it into OCLC and/or their catalog?

If so, do you have instructions or a workflow?

I am not a cataloger so excuse me if I am not using the correct terminology ☺

Have a wonderful weekend!

Johna Von Behrens, MLIS, CA, MSEd

University<https://urldefense.proofpoint.com/v2/url?u=http-3A__library.sfasu.edu_etrc_academic&d=CwMGaQ&c=clK7kQUTWtAVEOVIgvi0NU5BOUHhpN0H8p7CSfnc_gI&r=G9iOZhE_THmV6rgRVOmCFA&m=3f4IMU_KNQsKJbe0ZpK6Qv5fbUmrkpmPz3h93WmyjWM&s=qRmzyGbR4qhIMwAPEv62UavG6a-HWFMcpTPN89WQIYQ&e=> Archivist and Records Manager

East Texas Research Center<https://urldefense.proofpoint.com/v2/url?u=http-3A__library.sfasu.edu_etrc_&d=CwMGaQ&c=clK7kQUTWtAVEOVIgvi0NU5BOUHhpN0H8p7CSfnc_gI&r=G9iOZhE_THmV6rgRVOmCFA&m=3f4IMU_KNQsKJbe0ZpK6Qv5fbUmrkpmPz3h93WmyjWM&s=J75N0QyhpgtATXsWt3ac5-FL1OtPliQPdhsa1aVYCFk&e=>

Stephen F. Austin State University<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.sfasu.edu_&d=CwMGaQ&c=clK7kQUTWtAVEOVIgvi0NU5BOUHhpN0H8p7CSfnc_gI&r=G9iOZhE_THmV6rgRVOmCFA&m=3f4IMU_KNQsKJbe0ZpK6Qv5fbUmrkpmPz3h93WmyjWM&s=xOeZlWlzMGOYQZ4Fogf1sRgSGJea8mJgtVpwM2TxHZk&e=>

PO Box 13055 SFA Station

Nacogdoches<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.ci.nacogdoches.tx.us_&d=CwMGaQ&c=clK7kQUTWtAVEOVIgvi0NU5BOUHhpN0H8p7CSfnc_gI&r=G9iOZhE_THmV6rgRVOmCFA&m=3f4IMU_KNQsKJbe0ZpK6Qv5fbUmrkpmPz3h93WmyjWM&s=_CQmcRe0YPlZEkilvf0mxD_zZ4wa3e3iYvIB8O6__Pg&e=>, TX  75962

Phone 936.468.1536

Fax 936.468.7610

The views and opinions expressed in this message are my own and do not necessarily reflect the views and opinions of

Stephen F. Austin State University, its Board of Regents, or the State of Texas.

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

More information about the Archivesspace_Users_Group mailing list