2023-03-23 Resource Access Meeting Notes

Offcially announced RA SIG is piloting the prioritization process with Airtable - more info following
New Circ-PO Anne Ekblad
- In addition to my work with Steph and others, I'm currently working on expanding Title Level Request permissions, as well as functionality related to new library patron accounts creation (e.g., potential new patron request for an account to new user accounts creation) and access levels.

Magnus Andersson

meeting_saved_chat.txt meeting_saved_closed_caption.txt

30Min

TLR recalls

Stephanie Buck

TLR recalls

Currently implemented item statuses

User acceptance test for TLR beginning of May – We will have a kick-off Meeting here in the SIG to get infos to the testers and discuss issues !

Meeting Notes

Stephanie asks the question “should recalls, apply to items with statuses other than checked out” and there is discussion surrounding what statuses can be recalled and what it is written in the whitelist: https://folio-org.atlassian.net/wiki/display/FOLIOtips/Request+Type+Whitelist+Table+-+behavior+of+Recall%2C+Hold+and+Page.

Thomas asks if recalls are only possible on items that are checked out and the reason for asking is that ILR only allow certain recalls on certain statuses and TLR should be the same. If you can’t place an ILR recall on something that is available, you shouldn’t be able to place TLR recall on something that is available.

Thomas says that there should be some kind of load balancing when you place a general request, it should place a page if there are available items and then if there are no items available then it would place a recall, and if it can’t place a recall, it places a hold and so on.

Julie adds that for ILR there was hardcoded solutions for specific behaviors and the behaviors for page, hold and recall were supposed to cover the expected needs for most libraries. With TLR there are some different needs, and we are starting to outgrow the fixed behaviors.

David asks why Chalmers doesn’t use both hold and recall and one of the theories why a library might not use holds/recalls together put forth by David and collaborated by Mark is that EDS has limitations where it is not possible to use both request types, you must choose either hold or recall.

A decision is made for a new feature/enhancement. “Load balancing”, recalls will be spread out more. Try to adjust the way recall requests are placed among recallable items on more than the item most likely to be returned first. Look at how long an item has been checked out, how many request there are on the item and so on and try to find more balance that way. Thomas will help write an initial feature draft.

Stephanie asks what items should be recallable, should it follow how it works for ILR? There is agreement that if we want to keep the existing behaviors for request types, we should try and keep them consistent. Stephanie with the help of Vega will look over if there are gaps in how recalls are placed in ILR vs TLR.

Marie mentions and get agreement that it is good that this work is being done now but in the long run we need to take a deeper look at what behaviors we expect from page, hold and recall for FOLIO to be as great as it can be.

David and Thomas make a plug for the three-part item state

Stephanie wants the group to help with User acceptance testing for TLR in May. If as many people as possible could help and try to break it. Stephanie will let us know when the TLR only environment is available and in May it should hopefully have Orchid. There will be a small kick off meeting in May.