2023-03-06 Resource Access Meeting Notes

Time	Item	Who	Description	Goals/Info/notes
5min	Administrivia	Jana Freytag	WOLFCon23 Survey Update 20th March Title level requests testing environment Title level requests Slack channel Bugfest	Note Taker: Laurence Mini meeting_saved_chat.txt meeting_saved_closed_caption.txt
55Min	Open Discussion Round

Meeting Notes

Adminstrivia:

WOLFCON 2023 is being planned. Good time to start thinking of topics we want to see or present.
Survey: Jana and Cornelia will discuss results of the survey in the 3/20 meeting – how to use feedback to make RA SIG more effective
TLR: Stephanie announced that a dedicated FOLIO environment for testing TLR is ready, and volunteers to try to break TLR, discover missing use cases, etc. are wanted. Testing will begin after Bugfest is over. Contact Steph if interested!
Also, the current, closed Slack TLR channel will be archived and a new open TLR Slack channel created. Steph will put a link in the RA Slack channel.
Bugfest has started! Ask people at your institution if they are interested/able to participate. Good way to become more familiar with FOLIO. Cornelia: There are a lot of patron block tests begging for testers!

Open Discussion:

Laurence: Looking for comments / edits / questions regarding UITEN-245 and UICHKIN-376 user stories related to Alert staff to special location at checkin (UXPROD-1353).
Magnus: Asked about implementers experience with issue of fees/fines. Whether there are any problems with going with no fees/fines initially (using overdue and lost item policies with fee of 0), and then changing this later. Already lost items will be handled manually. Susan described experience at 5C, which migrated loans and wanted the new FOLIO policies to apply to the migrated loans. Changeover was smoother due to emails having been turned off, so patrons did not get spammed with large number of notices. Magnus said they plan to re-start all loans and eliminate old fees, so that will not be a problem for them.
Laurence: Asked about way to search for items missing only at a specific location A, and not showing items that are, e.g., not missing at location A but are missing at location B. No way currently to do this in the UI. Erin said Postman API call would be able to do this. Susan said LDlite, in process of being implemented, would also be a way to do this. The lack of being able to export search results from Inventory (unlike with, for ex., Requests, where you can export and the export shows information not in the UI, such as the item's owning library) doesn't help either.