OAI Documentation Working Group Call 2023-05-15

Owned by Annamarie Klose
Last updated: Jul 12, 2023
2 min read

Time: May 15, 2023, 2-3 pm Eastern

Call-In Info: Join our Cloud HD Video Meeting

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

 

Facilitator: @Annamarie Klose

Notetaker:

 

Attendees:

  • @Annamarie Klose (Ohio State University)

  • @Nora Zimmerman(Lafayette)

  • Christine Peterson (Amigos)

  • Amanda Hurford (PALNI)

 

Agenda:

  • Meeting frequency: Regular meetings on the third Monday of every month from 2-3 pm Eastern until Samvera Connect (October 23-26, 2023).

  • Goals:

    • Documenting common workflows and issues.

    • Share resources

    • Amanda agreed that we just need something simpler on the Samvera side about OAI and support for it. Would also like to share examples. Can note the DPLA question and sharing stories about how work was done. Work towards a consistent way of doing it.

  • Is Knowledge Base still a good place to put this information?

  • Information sharing

    • Nora noted support for OAI in a config file

    • Lafayette and OSU use simple Dublin Core for harvesting in Hyrax. The former is trying to also use the OAI feed in Ebsco’s OneSearch. Ebsco only wants to host base Dublin Core. OSU using a standard OAI transformation. The two OAI feeds are configured differently in terms of metadata. Anna said OSU’s OAI mappings were customized for DPLA. Nora noted various harvesting use cases for arranging an OAI feed. She feels it's important to note where and how the OAI feed is customizable. Nora says Lafayette looked to Science History Institute and their developer Jonathan Rochkind (sp?) in terms of how their OAI feed works.

    • OAI does not provide a standard way to provide links to thumbnails. Lafayette and OSU had to create a thumbnail link in the OAI feed. Nora discussed that certain issues like this might be out-of-scope for this WG. Anna agreed and said we could just note it briefly. Nora noted the set spec in the code.

    • The Samvera MAP (https://samvera.github.io/metadata_application_profile.html ) includes both Dublin Core and non-Dublin Core fields. Nora believes the simple Dublin Core fields automatically map to OAI. However, she noted the cherry picking of various namespaces in Samvera is weird.

    • Amanda showed Hyku OAI feed. SoftServ is working on the backend. Softserv is working on a prefix oai_hyku. This is a matter of the metadata mappings and the file URL. They have to test this out. She showed notes about SoftServ’s OAI work for various organizations. Their goal is to get all the metadata in the OAI feed. OAI Feeds  

    • Amanda noted also the possibility of setting up an OAI feed but there is a port where data is changed with a .csv to suit a service provider. Typically, OAI feeds are configured in one way for all uses. Amanda noted the Indiana DPLA hub mapping (https://dplaind.files.wordpress.com/2019/06/non-contentdm-mapping-for-dpla.pdf). 

    • Christine discussed community issues with getting Hyrax and Hyku code aligned. We all agreed that there is a concern about siloed code and configurations. Amanda mentioned too about the impact of this on efficiency.

  • Homework:

    • Check with developers about how OAI is configured.

    • Gather information about ongoing needs

  • Scheduling

    • WG is skipping June meeting since it falls on Juneteenth.

 

Next meeting: July 21, 2-3 pm Eastern