2025-12-15 Resource Access Meeting Notes

Date: Dec 15, 2025 

Recordings

NOTE: RESOURCE ACCESS SIG USES EITHER ZOOM’S AI NOTES FUNCTIONALITY OR MICROSOFT COPILOT 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

@Magnus Andersson

@Scott Peterson

@Erin Weller

@Steve Strohl

@Jana Freytag

@Claire Hoag

@Charlotte Whitt

@Olga Kalachinskaya

@Cornelia Awenius

@David Bottorff

@lisa perchermeier

@Anja Kakau

@Kimie Kester

@Martina Tumulla

Discussion Items:

Meeting Notes

AI-Generated minutes (pardon any errors)

Discussion Points:

• Product Council "Calendar Calming" Proposal (00:07:18 – 00:15:36)

  • Jana Freytag introduced a proposal from the Product Council to implement "meeting-free weeks" to improve work-life balance and provide dedicated time for deep work.

  • Goal: The aim is to make staff more efficient by reducing meeting fatigue. The proposal suggested scheduling these free weeks during the last week of each month, aligning with holidays like Thanksgiving and Christmas.

  • Alternate Viewpoints: Charlotte Whitt mentioned an alternative idea of "meeting-free Mondays," but noted this might just squeeze more meetings into the remaining four days, which is particularly challenging for newer groups like the Linked Data SIG that struggle to find any meeting time.

  • Flexibility: It was clarified that this is not a mandatory freeze; SIGs with urgent topics can still meet, but the community is encouraged to avoid scheduling during these periods to allow for broader participation in non-meeting tasks.

  • Feedback: Anja Kakau expressed strong support for the "free week" over a "free day," noting it allows for better long-term planning of both professional and private appointments.

• Including Title-Level Requests in Request Counts (00:15:37 – 00:22:25)

  • Magnus Andersson led a technical discussion on how to display title-level request (TLR) holds in the requests column of the loans display.

  • The Problem: Currently, TLR holds not yet assigned to a specific item do not appear in the item's request count, even though they successfully block renewals for that item.

  • Proposed Solutions:

    • Option 1 (Preferred): Implement back-end work to check circulation rules for every loan to verify if an item is requestable before including TLR holds in the count. This provides the best user experience but raises concerns regarding system performance for patrons with over 100 loans.

    • Current State Implementation: A simpler front-end-only fix was considered but rejected because it would incorrectly show requests for non-requestable items (like reference-only materials) that happen to be on the same instance.

  • Technical Context: The logic would likely mirror the existing checks used during request creation and loan renewal processes.

✅ Decisions Made:

• Meeting Schedule: The first meeting of 2026 is confirmed for January 8th and will focus on the Fees and Fines subgroup.

• TLR Implementation: The group tentatively favors "Option 1" for TLR counts to ensure data accuracy, pending further performance investigation.

📄 Action Items and Follow-up:

• Calendar Feedback: All members are asked to read the full "Calendar Calming" proposal and provide feedback via Slack by the following Monday.

• Meeting Planning: Members should add topics for January 2026 to the new meeting planning page on the Wiki.

• TLR Performance Review: Development teams (Vega/Volaris) need to assess the performance impact of Option 1 for TLR request counts on large patron accounts