OAI Documentation Working Group Call 2023-07-17

Owned by Annamarie Klose
Last updated: Aug 18, 2023
3 min read

Time: July 17, 2023, 2-3 pm Eastern

Call-In Info: https://osu.zoom.us/j/98331051969?pwd=NExOck8walMySHdGcVhId3pMcUJEQT09

Community Notes: https://docs.google.com/document/d/1YgCN88nS2bLdyFqLrhCaCSH69epSSFp87q7ukXGZp5I/edit?usp=sharing

 

Facilitator: @Annamarie Klose

Notetaker:

 

Attendees:

  • @Annamarie Klose (Ohio State University)

  • @Amanda Hurford(PALNI/Hyku for Consortia)

  • @Nic Don Stanton-Roark (PALNI)

  • Anna Malantonio (Lafayette College)

  • @Christine Peterson (Amigos)

  • @Nora Zimmerman (Lafayette College)

  • Braydon Justice (SoftServ)

  • Chris Bartos (Ohio State University)

  • Katherine Van Arnsdale (Andrews University)

 

Agenda:

  • Blacklight OAI used by Lafayette, OSU, and SoftServ to provide OAI with Samvera platforms

  • Braydon Justice SoftServ

    • /catalog/oai

    • Defaults to OAI DC

    • Hyku - Braydon: SoftServ has implemented some code into Hyku for more easy customization in Samvera. By default, there are no additional fields. Now, there is an OAI and Hyku field. However, it doesn’t support “pretty, custom” format. View of raw XML. Can use customizations to add other prefixes with SoftServ. They have made it that there is one file where you can add your header specs. Uses SOLR query. This is all developed by SoftServe. There are other files that need to be edited.

    • Adding a thumbnail link is about 10 lines of code. Would do a SOLR query for that specific field.

    • Use Blacklight OAI gem and make some changes in the Samvera layer

  • Anna Malantonio, Lafayette University

  • Chris Bartos, Ohio State

    • Blacklight 1.4.1 being used. It’s out of date.

    • Controller is used. However, we are using Admin Sets instead of Collections.

    • Solr_document.rb document is similar to Lafayette’s.

    • Because it’s an older version of OAI provider, we have to do some additional work. It doesn’t play nice with Rails.

    • It can be /dc

    • OSU uses handles for OAI identifier

    • Class set to share admin sets 

    • It’s all coming from SOLR

    • Thumbnail link - Get thumbnail path from SOLR. He had to create a way to process thumbnails that didn’t exist yet in SOLR. There was a substitution process for that. That was a little weird.

  • catalog/oai is the default. OSU did dc/api/oai. We’re not putting that code in the cataloging controller. If the prior is the default, we might change that after we upgrade.

  • Prefixes

    • Braydon: SoftServ can do different OAI prefixes easily in Hyku. Clients were interested in Qualified DC.

    • Katherine: Our repository uses a custom prefix created by SoftServ. We've only used OAI to ingest, not export yet.

    • Lafayette and OSU have one, customized prefix. Nora doesn’t expect to create additional prefixes. Current focus is DPLA sharing and EBSCO Discovery Service. Simple Dublin Core supports these purposes even though it does not give a full picture of our metadata. OSU would like to have QDC OAI to support both DPLA and BTAA Geoportal. We currently have customized simple Dublin Core. Collections as objects is also a consideration.

  • Amanda:

    • Are there things we can do in the community to make this process simpler to help folks starting out? Anna noted out-of-the-box, it’s easy to do a certain way. However, there’s not a walk through about setting up other standards that are not DC. Braydon said SoftServ is working on that. There is a hope to add this information as a standard to Hyku and Hyrax.

    • Discussed about maybe providing metadata mapping recommendations with out-of-the-box OAI from Hyrax and Hyku. Amanda noted repository information needing to be there. She suggested deliverables for various aggregators. Katherine said EBSCO Discovery should be added to the list.

  • OAI use cases:

    • DPLA harvesting

    • EBSCO Delivery Service

    • Import with Bulkrax

  • Developers on Slack: Anna, Braydon, and Chris

Next meeting: August 21, 2-3 pm Eastern