2022-11-03 Resource Access Meeting Notes

Open

Open

Open

Open

Nov 3, 2022

Find all recordings (including chats and captions) here: https://recordings.openlibraryfoundation.org/folio/resource-access-sig/ (pw: folio-lsp)

https://zoom.us/j/337279319 (pw: folio-lsp)

@Elizabeth Chenette 

@Erin Weller 

@julie.bickle 

@Christine Tobias 

@Mark Canney 

@Andy Horbal 

@Thomas Trutt 

@Stephanie Buck 

@Laszlo Jakusovszky 

@David Bottorff 

@Tim Auger 

@Shirley Moentnish 

@Brooks Travis 

@Cornelia Awenius 

@mey 

@Cheryl Malmborg 

@Amelia Sutton 

@Rameka Barnes 

Stephanie began by introducing Tim as a “new-ish” PO who works with dev team Volaris. Tim noted that he has previous library experience in corporate, academic, and public libraries and also with Innovative Services, where he worked on InReach.

Re: UXPROD-1628, Steph and Tim asked how long the request expiration period should be. “Highly variable” was the response, with configurability at the Tenant level or lower (e.g. Service Point) being desirable. This also answered Steph and Tim’s second questions: libraries should be able to configure time period, as opposed to it being set automatically by the system. It might also make desirable to enable override capabilities at the Policy level or to make it configurable at that level as an alternative to the approach outlined above.

Another question from Steph and Tim: should this take into account closed days? Consensus that this is not necessary and might not even be possible for libraries with far-out expiration dates that might not yet have calendars associated with them.

Question that grew out of this conversation: is it desirable for this to retroactively include outstanding requests at time of implementation? Consensus that following the precent of other Settings changes, the answer is no.

NEW BUSINESS:

Difficult to tell from list of open loans screen whether or not an item has been recalled. Has been frustrating for staff at Michigan State. Another SIG member noted that the “Requests” column basically contains this info: if the count is 1 or higher instead of 0, the item has been recalled. Someone else noted that a flag or some other indicator specifically for recalls might still be helpful. We don't know at this time whether or not the counter would go up if a title-level request was placed on an item.