Integrating ArchivesSpace with Voyager: Exploring MARC and Beyond

Slide Note
Embed
Share

Exploring the integration of ArchivesSpace and Voyager, focusing on repurposing finding aid information as bibliographic descriptions. Discusses steps taken, including MARC record review, NYU's MARC export plugin, local transformation files, and the use of MarcEdit. The goal is automation with ongoing adjustments and testing. Includes a demonstration link for further details.


Uploaded on Oct 10, 2024 | 0 Views


Download Presentation

Please find below an Image/Link to download the presentation.

The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. Download presentation by click this link. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.

E N D

Presentation Transcript


  1. ARCHIVESSPACE TO VOYAGER What s MARC got to do with it?

  2. Background When we migrated to ArchivesSpace at Yale in 2015, high on our wish list was integration with Voyager That s not easy, though And we had a lot of other work to work on So we continued with the practice of creating finding aids in one system and a corresponding MARC record for each finding aid in Voyager Now, we are thinking again about how we can integrate ArchivesSpace and our ILS For this first pass, we are looking at how to repurpose finding aid information as the bibliographic description.

  3. First steps We had to review the MARC records that ArchivesSpace is able to export natively Many thanks to Francis Lapka and others in Karen Spicher s Secret Agents / Subjects taskforce for making recommendations to improve ArchivesSpace s MARC exporter

  4. Our approach so far For every ailment under the sun There is a remedy, or there is none; If there be one, try to find it; If there be none, never mind it. First, we have decided to use NYU s MARC export plugin in ArchivesSpace to ensure that we get all of the data that we need, which would not be provided otherwise: eadid (which we add to an 035 field in MARC) Our version: https://github.com/YaleArchivesSpace/yale_marcxml_export_plugin Next, we decided to use a local transformation file to modify the MARC files. We decided to keep all of those modifications external from ArchivesSpace so that we will be able to update it more frequently, easily, and also have more options for customizing the transportation for different repositories, record types, etc. Last, we have opted to use MarcEdit to convert the MARCXML files to binary MARC and combine them together into a single collection Right now, those last two steps are combined into a single process, whereas the rest must be carried out manually (which I will demonstrate shortly)

  5. Next steps Well, the whole thing could / should be automated. That s the goal. But first we have to test out how things work so that we can continue to adjust the local MARC conversion process If you d like to try it out, let me know But first, a demo

  6. Demonstration https://github.com/YaleArchivesSpace/ASpace-plus-MARC

  7. Questions? The more about BIBFRAME the better!

Related


More Related Content