2019-4-15 Resource Access Meeting Notes

Date

15 Apr 2019

Time	Item	Who	Description	Goals
5min	Housekeeping		Notetaker -
30min	Item records	Cate Boerema (Deactivated) and Ann-Marie Breaux (Deactivated)	Items for electronic resources	- Some institutions will be creating item records in inventory for their electronic/online resources. - Institutions plan to create location(s) to assign to these (eg. "online" or "electronic") - Since locations require service points, they will probably create a dummy SP too - Do these need to be filtered out at checkout and request creation? Anywhere else? Anything we need to consider here. - Would be good to invite Ann-Marie Breaux to this meeting so let's plan this agenda item in advance so we can check with her - Definitely want Emma on this call, as well - Reference: https://issues.folio.org/browse/FOLIO-1891
10min	Renewals	Emma Boettcher	Renewal failure overrides	Answer the question: when an item is not renewable, is it also useful to check whether any due date schedule associated with its loan policy is valid?

Functional Area	Product Owner	Planned Release (if known)	Decision Reached
e.g. loans, fees/fines	Name	e.g. Q4 2018, Q1 2019	Clearly stated decision
Misc	Cate Boerema (Deactivated)	TBD	We will want to be able to prevent checkout and requesting of electronic items Can create an "electronic resources" loan policy which is loanable = N and associate it with the electronic location(s) though circ rules Can create an "electronic resources" request policy which disallows all requests and associate it with the electronic location(s) through circ rules In discovery, you will probably not want the item status "Available" to display, as the resource may not be available. Might need another item status for these resources to make it simpler for discovery to display the correct status. It would be technically possible to do this without a dedicated status, but less efficient to code discovery to display something special when Item status = Available AND Item location = Electronic. Could be an argument for getting started on custom statuses. NEED TO DISCUSS FURTHER WHEN WE HAVE REPRESENTATIVES OF INSTITUTIONS THAT PLAN TO USE ITEMS FOR E-RESOURCES.

Organization	Average Number Open Requests	Average Request Queue Length	How Many Newly Expired and Cancelled Requests per Day	How Many Newly Expired and Cancelled Requests per Hour (assuming we keep the short-term expiry periods for reserve items, equipment etc)
University Library Marburg	up to 1033 (2018-03-13)	about 130 requests	up to 1302 (2018-04-12)	per hour: about 29
Cornell University	244 requests placed per day (1 year average 4/10/2018 - 4/10/2019); current number of OPEN requests = 1,433	1.04 (current max=13)	Average per day: 13 cancelled; 29 expired; 202 charged	n/a

requests on loan details screen - do we want to display all requests or only those that impact due date?

yes we want all of the requests to show up as an action
also confirming that count of requests on item record takes you to list of all requests on item

original idea for expired was for request status and item status awaiting pickup by filtering
how do you come up with the complicated query logic for finding expired holds that need to be grabbed? logic is complicated by outstanding open requests
a new item status of "pickup expired" that is updated when request is expired or cancelled would simplify the discovery of these items
item status of "pickup expired" and necessary request info (patron name, barcode)
obviously need to limit by service point
report needs requestor, item barcode, title, item call number
assumption is that item state, etc. should be configurable at discovery layer level for display

the challenge is that the batch process or other query, how often does it need to happen?

current implementation is that the system checks every hour, not a batch job (right now)

probably do need minutes/hours for reserves, equipment, etc.
need to do performance testing - estimates on average numbers posted as table, please contribute your institutions estimates
Chicago - 20-25% of requests expire or are cancelled

How many newly expired requests might there be per day