2026-02-19 Resource Access Meeting Notes

Date: Feb 19, 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

@Magnus Andersson

@David Bottorff

@Katie Rahman

@Stephanie Buck

@Steve Strohl

@Thomas Trutt

@Jacob Dudley

@Scott Peterson

@Jamie Jesanis

@lisa perchermeier

@Martina Tumulla

@Olga Kalachinskaya

@Nina Morgenstern

@Erin Weller

@Stephanie Kaceli

@Susan Kimball

@Cornelia Awenius

@Kara Hart

@Anja Kakau

@Heather

Discussion Items:

Meeting Notes

Circulation Log

Early work, long before Lists was available. Look at original intent and think together about how to move forward into future development and avoid duplication of work. See UXPROD-1704. How are people using Circ Log? Not talking about Circ Log going away

• Not really a reporting tool but rather used on an hourly basis for troubleshooting. Where is a book, what about a fee/fine, notice.

• Use it to check against reporting numbers

• Find out who on staff did something

• Checking for items returned in a particular date range

• How often has an item been checked out?

Issues with Circ Log

• Actual cost transactions are not logged in Circ Log

• Circ Log uses barcodes for items and users, not UUID. People want UUID in the background to get to the user and item records

Circ Log gaps

• Ask for the list that Laurence Mini generated during documenting Circ Log functionality and make sure they have tickets

• Anonymization can be a problem because some data is captured in text fields

• Make related tickets children of UXPROD-1704

Not a tight timeline, likely not until after Umbrellaleaf

Fees/Fines for Lists in Trillium, Requests after that

Tom Trutt and Anne Ekblad are working with Magda Zacharska (Bulk edit) related to UXPROD-3805 (Bulk edit - Loan due dates). Firebird is planning for U. We'd appreciate any thoughts related to the following questions that are also listed in the Feature:

This would be a new category for loans in Bulk Edit. Across the board it should behave the same way single due date change works

1. Should the loan’s due date change be allowed for overdue loans?

   1. Yes, since you can include or exclude overdue loans in the query. Include loan status as part of the query

2. How should Recalls be handled in case of changed loan’s due date?  What would be the impact on other request types?

   1. Yes

3. Any loan statuses should be prevented from their due date being updated?

   1. Aren’t there only Open and Closed loan statuses? Only open loans should be

4. Any item statuses should prevent loan’s due date to be updated? (including declared lost, claimed returned, aged to lost?)

   1. Due date change is currently not allowed for a single loan so no.

5. What would be expected behavior when the entered data is invalid?

   1. Perhaps this relates to uploaded ID numbers.

   2. If it relates to the bulk edit data entered, it would have to be a date. Does it check the calendar and that is where the invalid data comes in?

6. What should be specified as a loan action and how this value is being used in FOLIO?

   1. Make the loan action reflect that it was done by Bulk Edit. “Chainge due date via bulk edit”

   2. Include in loan details and circ log

7. How should the change in loan’s due date impact fees and fines?

   1. Overdue fines and replacement fees would not yet be applied if the loan had not aged to lost or been declared lost.

   2. Overdue fines and reminder fees stay open on the loan when it is done for a single loan.

8. Would the change of the loan’s due date impact loan policies? If yes, how?

   1. No. Doesn’t currently now when performed on a single loan

9. Should loans with a fixed calendar due date be updated?

   1. Yes