2026-02-09 Resource Access Meeting Notes
Date: Feb 9, 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
@Susan Kimball
@Thomas Trutt
@Kajsa Bäckius
@Martina Tumulla
@Olga Kalachinskaya
@Tobi Hines
@Heather
@Cornelia Awenius
@David Bottorff
@Anja Kakau
Discussion Items:
Time | Item | Who | Description | Goals/Info/notes |
|---|---|---|---|---|
5Min | Administrivia | @Susan Kimball @Cornelia Awenius | Upcoming meetings:
| Note Taker: AI (@Thomas Trutt) |
15Min | RA SIG Charge | @Susan Kimball @Cornelia Awenius | RA SIG Charge/Description - let’s take a look and see if it still reflects our work |
|
10Min |
| @Scott Peterson | Are item limit blocks working properly? Not clearing when an item is checked in. |
|
Meeting Notes
Consider making a bulleted list.
Consider adding courses, remote storage, circulation log
Interactions with other SIGs
Remove words relating to defining essential functions - based on initial development of FOLIO
Ongoing development and refinement
Condense recalls and holds to requests
Remove loan type and patron group definitions
Consider integrations with external
Aim for more broad definitions
Advises on resource sharing, remote storage,
Perhaps something like: The resource access SIG touches on all areas of folio. that concerns access services, circulation, Including loan policies, fees, fines, remote storage, notices.
etc. The scope changes to meet the needs of the application and user base?
Claimed returned does sometimes not clear blocks on suspended fines
Olga asked at User Management SIG, but referred here. When equipment is returned in person, staff often want to know if there is anything outstanding (overdue) or blocks cleared. Interested in having user information about blocks and outstanding overdues visible immediately upon check-in. Serious privacy concerns were raised. Perhaps permissions could allow some to see the information and others could not. Concerns around impact on performance were also expressed. Perhaps a report that would show when automatic blocks are removed or added.