2022-09-15 Resource Access Meeting Notes

Date

15 Sep 2022

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)

Discussion Items:

Time	Item	Who	Description	Goals/Info/notes
5min	Administrivia	Cornelia Awenius	PC is seeking to revitalize SIG relationships, Sharon is our assigned PC member, see 2022-09-15 Product Council Meeting notes	Note Taker: Cornelia Awenius meeting_saved_closed_caption.txt
20 min	different notice policies for recalled items	David Bottorff		UXPROD-2112 - Getting issue details... STATUS
20 min	example feature for learning PO work

Meeting Notes

David: when items are recalled, notices continue on the same notice policy and schedule, so there's no way to either send notices more frequently or with a different text
it an item's due date is changed by a recall so that multiple courtesy or overdue notices would be sent, FOLIO combines those into a single email notice but repeats the loan info for the item as many times as the notice template would be invoked
might be a significant problem to institutions that recall a lot or let patrons do it
Kara: our patrons get recall notice followed by courtesy notice that asks to renew, but renewal won't be possible, and the VuFind message is weird, and patrons can't see which items are recalled in their account
David: that isn't the case in Chicago's Vufind and should be solvalbe, they also don't let patrons renew (automated renewals instead) because renewals through API were too much load on the system
now you have to put all possible scenarios in the notice text while it should be a standard feature to change notice policy and template for recalled items
the only Jira for this problem is UXPROD-2112 - Getting issue details... STATUS , ranked highly by several institutions, it needs more refinement
Andrea suggests taking it as an example for assistance PO work
Thomas favors a subgroup to look at notices in general and identify structure and structural gaps, but noone has the capacity to lead such a group
a PO assistant group was discussed on Monday (see 2022-09-12 Resource Access Meeting Notes), where volunteer SIG members would take on a feature and write and stories and requirements until it's ready for taking it to the devs
we need to wait for Jana returning to move this forward, need a meeting time, could devote some of the regular meetings to it, like CDL subgroup
need to involve more people in our institutions in collecting user stories