2025-03-13 - 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
Meeting recordings: SIG Meeting Recordings
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.
Organisation: next meeting will be in May (the next regular one would be around Easter)
Agenda items
Review of the issues around invoices
Development of institutional levels (SLUB Dresden)
Minutes
Review of demands relating to Link OA Charge from Invoice and to Commit Money for OA Charges in Invoice App while allowing for subsequent editing of invoice data
Requests from OA SIG group was brought to the Acquisitions SIG group in Jan/Feb 2025 → difficult discussion.
There is a google docs with the description of the problems:
In 2 weeks-time the OA SIG group should attend again in the Acquisitions SIG group to further discuss the issues.
Development of institutional levels
Relevant to
publication monitoring of decentralized funds (TUD/Medical faculty), which the library has to be able to report to the TUD and to the Medical Faculty.
consortium leaders to keep track of the publications published under an agreement by different institutions (aka reporting relevance).
At the moment, this is how SLUB Dresden has this information in its internal database:
By inserting the pure_id numbers in the application form, all other fields are automatically filled out by the system.
Owen: Such a parent-child structure is possible. It is also possible to insert more fields (currently there are 2 fields) for Institution Level. The second solution (with more fields) is not relational - therefore also less good, but also easier.
There seems to be interest for checking if it can be of use for consortium leaders.
Owen: If you used the “Institutional level 1” for the PURE ID it would be like this. Or we could add a new property for this.
Problems: integration, different institutional structures (some institutions use …? and it works already with folio, others do not use it) and budget.
Important in the decision process: do we want to store it in Folio or use an external system?
Owen has created a Jira Ticket with a problem description and potential solutions: UXPROD-5225: Open Access: Extend support for Institutional levelsOpen
Moderation: @Martin Bauschmann
Attendees:
Astrid Orth (SUB Gö)
Christina Prell (UL Regensburg)
Eloísa Deola Schennerlein (SLUB Dresden)
Katrin Gärtner (UB Mainz)
Owen Stephens (K-Int)
Regine Ries (UB Mainz)