2026-03-05 Resource Access Meeting Notes

Date: Mar 5, 2026 

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

@Scott Peterson

@Jacob Dudley

@Heather

@Steve Strohl

@Katie Rahman

@Thomas Trutt

@Robert Heaton

@Erin Weller

@Susan Kimball

@Martina Tumulla

@Cornelia Awenius

@Olga Kalachinskaya

@Anja Kakau

Discussion Items:

Meeting Notes

Zoom AI Companion Summary

Quick recap

The team met to review and discuss JIRA tickets, working through various items to determine which ones should be closed or require further refinement. They examined several tickets including storing effective copy numbers, error message styling, phone number fields for SMS messaging, three-part item status functionality, and item anonymization features. The group reached consensus to close multiple tickets including the phone number field enhancement, three-part item status customization, item status notification when items become available, and retaining last borrower information after anonymization. They identified one ticket requiring further refinement regarding course item inventory data synchronization, and two tickets needing testing of existing functionality. The team noted significant progress in closing tickets, with only a few remaining items to address in future meetings.

Next steps

• Cornelia: Add a note to the spreadsheet to check whether the effective call number appears on all relevant reports; if so, recommend closing the related JIRA tickets as redundant.

• Cornelia: Test if error message styling (bolding, etc.) is already implemented in modals and pop-ups, and report back to determine if the ticket can be closed.

• Susan: Send out the list of proposed ticket closures to the group for final review and allow others to speak up if they wish to keep any tickets.

• Katie: Investigate and share the required permission/capability for printing single pick slips in the requests app, and message Susan or the group on Slack with the details.

• Susan: Translate the identified pick slip printing permission/capability to the appropriate capability set and share with the group.

Summary

Meeting Documentation and Ticket Review

The team discussed meeting documentation tools, with Susan explaining she uses Gemini for local transcript analysis while Tom previously used Copilot. They confirmed that AI meeting summaries are generated automatically when the feature is turned on, as previously demonstrated by Peter Murray. The meeting focused on reviewing JIRA tickets, with Susan indicating they have 2-3 more meetings worth of tickets remaining to address.

Effective Call Number Redundancy Review

The team discussed a ticket about storing the effective copy number, which appears to be redundant since the copy number is already part of the effective call number. Robert confirmed that the copy number is indeed included in the effective call number. Cornelia suggested checking if the effective call number is displayed in all relevant reports, after which they may close the ticket if it is already being handled. Susan agreed to review the reports and make a decision about closing the ticket.

Error Message Styling Ticket Review

The team discussed an old ticket from 2019 about styling error messages, with Susan questioning whether the styling had already been implemented. Thomas and Cornelia noted that error messages use a common dialog box and suggested checking if the styling was already included in that system. They agreed to test it and potentially close the ticket if the styling was already in place. The conversation then shifted to a new topic about making phone numbers a repeatable field with type labels.

Phone Number Fields Discussion

The team discussed the need for multiple phone number fields in the user record, particularly for SMS messaging capabilities. While Susan and Thomas agreed that the current system with two phone fields (phone and mobile phone) might be sufficient, Jacob mentioned that carrier information was previously required for SMS messaging. The team decided to close the ticket as the SMS messaging functionality was being actively worked on by another team, with Steph Day involved in the editing of related tickets.

System Redesign and Inventory Updates

The team discussed several items, including the decision to kill a three-part item state proposal and redesign it as a two-part system focusing on process states. They also agreed to close a notification feature request for items on order, as Susan explained this functionality has never been implemented in their systems and the wording on order forms was recently changed from "notify me" to "place on hold." The team further discussed a course reserves issue where item inventory data is not synchronized after being associated with a course, which Olga identified as a problem requiring further refinement.

Item Status Customization Decision

The team discussed item status customization in the check-in app, with Susan and others agreeing that customizing item status behaviors was not recommended as it could create more problems than solutions. Erin shared that MSU had previously used restricted status for non-circulating items due to EDS display issues, but had recently switched to using loan types instead after EDS was updated to allow loan type display. The team decided to mark the customization ticket as closed, with Thomas noting that new work would be needed to address item status customization requirements and expected behaviors.

Barcode Scan Logging Feature Rejected

The team discussed a proposed feature to log barcode scans even when no transaction occurs, with concerns raised about its utility and implementation challenges. While Katie shared a potential use case from her institution where check-ins weren't being recorded, the group ultimately decided against implementing this feature, with Anja and others agreeing it wasn't worth the effort given the potential for data clutter and confusion. The team concluded that anyone who wants to keep the feature should provide specific use cases and refine it themselves, with Susan suggesting this could be a prerequisite for keeping it in the product.

Library Data Anonymization and Pick Slips

The team discussed two main topics: anonymization of library borrower data and printing pick slips. For anonymization, they agreed to close a feature proposal that would retain item history after anonymization, with Thomas and others expressing concerns about defeating the purpose of anonymization and potential legal consequences. Regarding pick slips, they confirmed that functionality was already developed but needed to be enabled through specific permissions, with Katie agreeing to investigate and share the required permission settings.