2024-06-13 - OA SIG meeting

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

Meeting URL: Join our Cloud HD Video Meeting (Password required)

OA Working Group Wiki: Open Access SIG Home

Google Drive Folder: Open Access Working Group - Google Drive

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.

Agenda items

• Any news from the group?

• Demo of OA in Reporting app (@Stefan Dombek)

Minutes

• @Christina Prell reports that Bavarian Libraries are checking a Gaplog with regard to a potential implementation of the OA App, they would like to discuss remaining open issues in the SIG in one of the next meetings

• @Owen Stephens: reviews permissions of OA app with K-Int-> asks if there is a need for more granular permissions (edit publication request - not charges; create charges not delete charges), at the moment it is “everything or nothing”

• @Peter Sbrzesny: deletion should be an extra permission (compared to create and edit) -> would be possible according to @Owen Stephens

• Feedback from the group regarding permission levels is welcome via Slack or in the next SIG meeting

• @Owen Stephens: new Permission structure + bug fixes in charges constitute new Poppy Release which is soon to be finalized, next step: new release for Quesnelia which entails upgrade to Grails 6

• Demo of OA in Reporting app (@Stefan Dombek)

  • Presentation slides:

  • In-App Reporting (predefined function in the UI) vs Individual Reports (customizable reports with the help of the Reporting App and SQL) in Folio

  • Underlying the OA-App is a pure relational data-schema

  • @Stefan Dombek has created 5 views that represent data from the OA App in a coherent manner -> those views can be combined and filtered in the Reporting App

  • Requirements for using the Reporting App: MetadDB, Repositories - currently Github, Gitlab will be supported in the future

  • Repositories can be local or shared with other institutions, they host the definitions, filters and metadata fields of defined reports

• Discussion

• @Martin Bauschmann : reporting examples are reports on charges, request reports and cross-app reports with integration of data from the Invoice/Finance App

• cross-app reports are possible with Reporting App, those cannot be implement with the Lists App because reporting definitions are “hard-coded” into the app and local dependencies may vary

From the chat

Attendees