2025-01-09 - 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
Presentation/Discussion Folio Prioritization Process
Minutes
Guest Attendees/Speakers
@Alexis Manheim (Stanford University Library): Product Council (PC) Chair, PC Liaison for OA SIG
@Kristin Martin (University Library Chicago): PC Member
@Martina Schildt (GBV): PC Member, Member of FOLIO Prioritization Process Working Group
@Jesse Koennecke (Cornell University Library): PC Member
Presentation
Kristin presents the current Folio Roadmap (see: FOLIO Roadmap ) and stipulations from the Prioritization Working Group
Kristin and Martina outline the prioritization in the Aqcuisitions SIG:
Feature ideas come from topics discussed at the Acquisitions SIG and are listed on the Acquisitions/Resource Management implementers wiki page
Topics are then converted to features in Jira Tickets, searchable via tag "acq-sig-topics"
voting system for Jira tickets -> click "thumbs up" in the side bar to vote for the issue (Atlessian Account necessary)
Pro’s -> clear quantitative designation of demand; easier prioritization for developers
Con’s -> expectation management: high scores lead to
Discussion
@Owen Stephensdescribes prioritization process in OA SIG which is not entirely different from the initial process in Acquisitions SIG:
Wiki Page for implementer‘s topics (gaps, feature requests etc.) at OA Implementers' topics
Topics from the wiki page along with unfinished business from first development wave of the OA App are derived into Jira tickets, searchable via tag „open_access_management”
no voting system in place
Owen points to the current problems with regard to app development in the OA App:
OA App is not part of the regular flower release cycle
no standard development process for those apps as opposed to the apps in flower releases which have dedicated Development Dashboards as part of the FOLIO Roadmap
OA App has approval from product council but not from technical council for incorporation in flower releases
Kristin: raises the question of future interaction problems with other apps
Jesse interjects that the OA App might be a case for microservice infrastructure outside of flower releases
Owen: sees work towards integration in flower release as long-term community issue because there is no development of new functionality entailed
Martin: focus of future funding from Leipzig University lies on functional app development accompanied by maintenance contracts that assure compatibility with flower releases
Martina: proposes the idea for new approval process in technical council with potential joint funding from the community
Kristin: supports the idea of joint funding using the example of the Courses App
Group agrees that more marketing for OA App is necessary in order to attract further support/funding from the Folio community
PC Meeting as a starting point: Martin will present OA App in one of the next meetings to extend the outreach