2026-03-23 Resource Access Meeting Notes

Date: Mar 23, 2026 

Recordings

NOTE: RESOURCE ACCESS SIG USES EITHER ZOOM’S AI NOTES FUNCTIONALITY OR GOOGLE GEMINI TO PROCESS THE TRANSCRIPT. If you would prefer that we do not use AI any session you attend, we are happy to! Please alert the convener at the start of the meeting.

Find all recordings here: https://recordings.openlibraryfoundation.org/folio/resource-access-sig/ (pw: folio-lsp)

Zoom

https://zoom.us/j/337279319 (pw: folio-lsp)

Attendees

@Katie Rahman

@Scott Peterson

@Martina Schildt

@Steve Strohl

@Magnus Andersson

@Cornelia Awenius

@Olga Kalachinskaya

@Erin Weller

@Susan Kimball

@Heather

@Thomas Trutt

@David Bottorff

@Anja Kakau

@Joseph A Molloy

@Robert Heaton

@Karen White

@Jamie Jesanis

@Jacob Dudley

Discussion Items:

Meeting Notes

Martina described the process of how ERM (and Acquisitions SIG) does prioritization

AI-Generated minutes (pardon any errors)

Based on the combined audio and chat transcripts from March 23, 2026, here is the summary and analysis of the Resource Access SIG meeting.

📄 Meeting Minutes

• Date: March 23, 2026

• Context: The RA SIG is transitioning from a year-long effort of cleaning up and refining their JIRA backlog to a new phase focused on community-driven prioritization of features.

📄 Discussion Points

• Announcements and Scheduling (00:04:21 – 00:13:57)

  • The meeting opened with a review of upcoming schedule changes, including "Calendar Calming Week" next week, which will result in no meetings on Monday or Thursday.

  • A German holiday on April 6th will also cancel that day's meeting, with the group next reconvening on April 9th for a JIRA ticket review.

  • The Fee/Fines subgroup is scheduled to meet this coming Thursday, pending any last-minute cancellations via Slack.

  • Amelia Sutton has posted a User Acceptance Testing (UAT) opportunity regarding the display of custom fields on the checkout screen. Members are encouraged to provide feedback before the April 1st deadline.

  • Steph Buck is seeking volunteers for a small subgroup to define workflows for SMS messaging. This group will likely meet a few times to establish requirements and then review the resulting documentation.

• ERM SIG Prioritization Framework (00:13:57 – 00:37:35)

  • Martina Schildt presented the process used by the ERM SIG to handle community requests. It begins with an "Implementers Topics" page on Confluence where any user can add a "wish" or requirement.

  • Each topic undergoes a discussion phase in the SIG or a relevant subgroup so the Product Owner (PO) can understand the use cases and determine if mock-ups are needed.

  • Once a topic is understood, the PO creates a JIRA ticket and applies the label "erm-sig-topics".

  • The SIG uses a JIRA dashboard to track these tickets, allowing the community to vote on them. The number of votes helps the development teams determine which features to pick up when they have capacity.

  • Discussion statuses used to track these items include "Open," "Blocked," "In Progress," "Voting," and "Closed".

  • The ERM SIG selects five top priorities to submit to the Product Council, distributed across their various focus areas like e-holdings, e-usage, and agreements.

• Adapting the Process for Resource Access (00:37:35 – 01:00:25)

  • Susan Kimball expressed concern that opening all 500+ existing RA JIRA tickets for voting would be a "non-starter" and overwhelming for the community.

  • She recalled the "mind-boggling" complexity of the original MVP (Minimum Viable Product) spreadsheets and argued for a more streamlined approach.

  • The group discussed breaking the backlog into sub-areas (e.g., Requests, Loans, Fees/Fines) to allow for focused voting sessions rather than presenting the entire list at once.

✅ Decisions Made

• Sub-Area Breakdown: The SIG will categorize JIRA tickets into functional areas (Requests, Loans, etc.) before presenting them for community voting to prevent information overload.

📄 Action Items and Follow-up

• SMS Subgroup Volunteers: Interested members should submit their names to Susan Kimball (via chat or Slack) to be added to Steph Buck’s SMS messaging workflow group.

• Custom Fields UAT: Members are to review the custom fields checkout testing opportunity and provide feedback by April 1st.

• Fee/Fines Meeting: The Fee/Fines subgroup will meet this Thursday to continue their specific work.

• JIRA Review: The next full SIG JIRA review is scheduled for April 9th, following the calendar break.