2025-12-01 Resource Access Meeting Notes

2025-12-01 Resource Access Meeting Notes

Date: Dec 1, 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

@Thomas Trutt

@Steve Strohl

@Karen White

@David Bottorff

@Scott Peterson

@Erin Weller

@Olga Kalachinskaya

@Jacob Dudley

@Tobi Hines

@Kajsa Bäckius

@Mark Canney

@Martina Tumulla

@Kimie Kester

@lisa perchermeier

Heather

@Susan Kimball

@Cornelia Awenius

@Amelia Sutton

@Jamie Jesanis

 

Discussion Items:

Time

Item

Who

Description

Goals/Info/notes

Time

Item

Who

Description

Goals/Info/notes

5Min

Administrivia

@Susan Kimball

@Cornelia Awenius

Winter Break from December 22-January 5. Resume meetings on Thursday, January 8.

Thursday, December 4 - Fee/Fine Working Group

Thursday, December 11 - Backlog ticket review

Note Taker: AI (@Thomas Trutt)

25Min

Restricted Status

@Thomas Trutt

Define expected behavior for Restricted Status - Item Status Documentation

https://folio-org.atlassian.net/wiki/spaces/RA/pages/318473855

25Min

Triggering event naming

@Magnus Andersson

{If time allows] Decide on naming for triggering events in circ log & notice policies: https://folio-org.atlassian.net/browse/UXPROD-5618 .

 

Meeting Notes

previously discussed:

  • UIREQ-581 - Allow requests for items that have item status as Restricted Closed - finished in 2021

  • https://folio-org.atlassian.net/browse/UIIN-1306

  • Cornelia verified that in Nolana it was possible to put a Hold request on a restricted item status, whereas in Poppy and Quesnelia requests on restricted item status items are no longer possible.

  • Mark in Chat: UXPROD-3860 says "A library implements Controlled Digital Lending and decides to use the built-in item status of Restricted to represent when the digital copy of the item is circulating. They change the behavior of the Restricted item status such that they are not able to circulate the physical copy while the digital copy is on loan."

  • This ticket references a spreadsheet that describes the functionality associated with Item statuses https://folio-org.atlassian.net/browse/UXPROD-3469
    https://docs.google.com/spreadsheets/d/19_aA7bhRIxhcC6Gz-rK_LrfOtz8F5VaOmOcsFsdGU8I/edit?gid=745971866#gid=745971866

  • from CDL subgroup meetings:
    The item status 'restricted' (can be checked out with a warning message)

    1. physical item: access to the CDL then flipped to restricted

    2. physical item: when returned then flipped back to available
      CDL item status was to use 'restricted', similar as the Hathi-trust. Andrea mentioned that we need to be able to solve multiple copies, move them around (logic similar to TLR routing).  
      The restricted Item Status was implemented for the CDL Workflow but currently does not work like required
      This status is used in different scenarios as well

      (CDL MVP document)

  • https://folio-org.atlassian.net/wiki/spaces/FOLIOtips/pages/5670059

  • https://folio-org.atlassian.net/wiki/spaces/RA/pages/2252483 : Change status of CDL items to an existing or or new status that is requestable + loanable with confirmation

  • holds or recalls: https://folio-org.atlassian.net/browse/UIREQ-760

Decisions Made:

  • Restricted item status will allow Holds and Recalls to support Controlled Digital Lending (in the future) and maintain a distinction from Unavailable item status. Loan Type and Material Type can be used to control requestability in the circulation rules. Workarounds for EDS display reasons are no longer needed since the Loan Type now displays in the RTAC.

  •