2023-07-24 Resource Access Meeting Notes

Vacation Jana in September
Cancelling Meetings during WOLFCon?
Please note this message from Khalilah Gambrell : Hello all. Team Bama development has made bursar exports much more flexible to support most configurations. The goal is to release these updates for the Poppy release. In a few days, @sjturner1 will post details asking for folks to help with user acceptance testing (UAT). For more details on this UAT effort, please review https://folio-org.atlassian.net/browse/UIPBEX-48. If you can participate and/or have questions, please contact Steven via slack.
Laurence Mini took over RA documentation for Erin Nettifee

Open Discussion round

all

Gaps that came up during the meeting

TASK

See RA Gap list and enter your 3 major gaps: Gap list RA SIG

Meeting Notes

Open Discussion round

Magnus brought up title level requesting and page functionality as potential topic for discussion at WOLFCon

A few different scenarios have revealed issues, such as a staff member trying to locate a paged book, they can't find that copy, so they want to move the request to another copy but can't move a page to a hold in TLR
They have to use pages with TLR, so they can't select any available copy to fill the request
Tom mentioned that if we have an open page, we can move the request to another item on the same instance record for item-level requests; is this a missing requirement for TLR?
Laurence said that he helped with user acceptance testing, and it is possible to move TLR page request to a checked out item and change to recall (believes this bug has been fixed: CIRC-1831 - Getting issue details... STATUS )
Tom suggested the following first steps: go through and document what part of the system you're using, outline user scenarios, and then describe what it is you would like to be able to do
Tom also mentioned a possible workaround, which requires extra steps but does make this possible: cancel the initial request and then duplicate the request
Jana mentioned the WOLFCon discussion around TLR would be two parts: first is an update on where development stands, and second is a discussion of "pain points" or suggested improvements
Jana suggested Magnus talk to Steph about how to incorporate this discussion into the session

Gaps we would like to address

Brainstormed existing gaps (see list in table above)
Jana mentioned these are very broad topics, and it might be helpful to figure out what are the top three priorities for each institution
Julie pointed out it is good to identify these gaps, but that there is still a lot of work that needs to be done in terms of working out the details before it can be considered for development, get a PO, etc.
We decided to go through the gaps on the Gap list RA SIG to update the list for your institution and vote for your 3 priorities
Jana will post the top three selections in Slack
Tom also talked about also maintaining a list of what parts of the system each institution is using, e.g. who is using TLR and who would like to use it? Who is using actual cost vs. set cost?

Other business

Magnus: Linköping University went live with FOLIO last week
David: Put in a plug for the CDL subgroup, which needs to figure out how best to move forward with Duke/Andrea leaving