2023-02-27 Resource Access Meeting Notes
Date
Recordings
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
Paivi Rentz
Discussion Items:
Time | Item | Who | Description | Goals/Info/notes |
---|---|---|---|---|
5min | Administrivia | Bugfest starting next week, please claim test cases! | ||
55Mi | Recalls | Show & Tell Questions & Discussion | Anyone else willing to share how recalls work in your library?
Looking for VuFind users! |
Meeting Notes
Five Colleges: only pages and recalls. no holds, currently no TLR, choice of first available or specific volume on EDS, long loan periods for everyone. Hope that TLR may make requesting process more efficient, if issues with multi-volume fixed. Would like to see due dates revert if a recall is cancelled (see UXPROD-2826 and UXPROD-2689).
Chalmers: similar situation, want to switch to automatic renewals and holds
Duke doesn't want automatic renewals anymore, before they don't see stuff never again, Chicago has automatic renewals by scripts because renewal by patrons was too much load. Susan (5C): EDS not allowing batch renewals is problem for e.g. faculty who may have 700 items to renew....
Brooks: edge-API selects request type, tries page first, then hold, then recall - if both holds and recalls are allowed in one policy, a recall will never be placed, for TLR it's recall first, then hold
Cornell: allows both holds and recalls (don't use edge-api with Blacklight), but pushes patrons to ILL options first
some libraries would use holds for staff processes only
problems with multi-volume-items requests were discussed
Julie tries to determine when recall notices should be sent: see discussion on Slack. Add any comments. Julie will write up Jira tomorrow unless anyone raises concerns / complicating factors.