2025-06-16 Resource Access Meeting Notes

Date: Jun 16, 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

@Franziska Lehmann

@lisa perchermeier

@Amelia Sutton

@Catherine Tuohy

@Claire Hoag

@David Bottorff

@Laurence Mini

@Magnus Andersson

@Mark Canney

@Martina Tumulla

@Olga Kalachinskaya

@Paivi Rentz

@Shirley Moentnish

@Thomas Trutt

@Tobi Hines

@Tobias Gostomsky

@Cornelia Awenius

@Susan Kimball

Discussion Items:

Meeting Notes

Lisa Perchermeier joined to review some patron notice work they are hoping to begin development on. Met with Julie Bickle, PO for patron notices and staff slips. Three ideas for future work to get the feedback from the group. Already discussed with the German library group. Franziska Lehmann is the product owner

New notice use cases:

Hold request: no renewal possible - currently no triggering event in FOLIO. They are only working with item level holds in their current environment. Need to create a new trigger when a hold request is placed on an item on loan. Not clear if this was extended to TLR who would receive the notice when multiple copies are checked out.

Pre-reminder expiration date user account - Send notice to a user when their expiration date is approaching. Need to add a new category of user notices, perhaps General user notices. Need to add the user.expirationDate token to the notice templates. New triggering event of Expiration date. May need new category in patron notice policy of General user notices. German libraries suggested that this is not really a loan-related notice so perhaps it shouldn’t be included in the regular notice policies. Perhaps it could go into the Patron Group settings page? What other use cases might inform where the configuration should live in settings?

Notification regarding outstanding fees, even if there are no new fees - Periodic reminder about outstanding fees/fines. Proposing to add to General user notices since it is periodic and not triggered by a fee/fine. No need for additional tokens. Triggering event would be user has open fees/fines. This and the above should be run on a daily basis rather than constant checking for triggers.

Jira Ticket review:

The group of folks reviewing 4-year-old Vega tickets in Jira has completed the initial review and identified 27 tickets that can be closed because they are either no longer needed or need to be rewritten. SIG members were asked to review the list of tickets proposed for closure by June 30th.