2024-03-14 - OA SIG meeting

Meeting time: Monthly meetings, every second Thursday of the month, EST/EDT: 8:30 AM

Meeting URL: https://openlibraryfoundation.zoom.us/j/82643780981 (Password required)

OA Working Group Wiki: Open Access SIG Home

Google Drive Folder: https://drive.google.com/drive/folders/1HR1JyDkUeRE0kL1eBKcu6uIvcNcnn352?usp=sharing

Slack channel: #open-access-management

Mailing list: folio-rm-oa@ole-lists.openlibraryfoundation.org (Subscribe here selecting 'folio-rm-oa' list)

Housekeeping and major community updates

• Please add questions and topics to the OA Implementers' topics page. Topics or questions posted in slack will be added here as well.

Agenda items

• Presentation of gaps and use case analysis /Gaplog from Bavarian team (@Christina Prell )

Minutes

• Bavarian team created user stories from general work day

• started to test user stories; closed stories that already works with OA app

• results listed in a Spreadsheet with priorisation
  

• Use cases:

  • Clear and correctable overview of all article and financial data

    • have an export / spreadsheet for overview and easy checking for missing fields

    • actually task for a reporting solution like metadb

    • no reporting solution existing in Bavaria at the moment

    • possibly solution via Lists app

  • Charges: Allocation to several payers in euros (currently only possible in original currency)

    • OS: why not via Invoices/funds

    • Owen to create a Jira for that

  • need to record more than one receipt ("Beleg")

    • needs to get discussed with Acq SIG

    • or first D-Erwerbung

  • Advanced search with filter option across all fields, but especially invoice number, title, corr.aut., contact person

    • Owen to create a Jira for this

  • record reasons for the rejected (and thus closed) requests in a free text box (e.g. "author not affiliated"/"third party funding"/no response when contacted)

    • closure reason is configurable in Settings

    • to have a free text field high priority in some Bavarian libraries

• A basic finding was that a reporting solution ist needed, like metadb or other FOLIO reporting solution

  • OA data already included in metadb

• We all should have a look at FOLIO Lists app and discuss OA connectivity

• Possible further discussion next meeting

From the chat

Attendees