Date

Time	Item	Who	Description	Goals/Info
2min	Administrivia	Jana Freytag		Notetaker - Laurence Mini
20Min	Claimed returned: search & resolution	Emma Boettcher	Confirm whether rankings on UXPROD-532 - Getting issue details... STATUS are accurate
5Min	Last borrower functionality	Brooks Travis	discuss “last borrower” functionality UXPROD-2634 This feature ticket was created by Ian Walls
20Min	Covid/Corona impact on library circulation	Cate Boerema (Deactivated)	General discussion on how Covid 19 is impacting libraries. What changes have there been in circ operations? Has it impacted features needed and used? How? Any changes you expect might have a permanent impact on operations?

Meeting Outcomes

Functional Area	Product Owner	Planned Release (if known)	Decision Reached	Reasoning	Link to supporting materials
e.g. loans, fees/fines	Name	e.g. Q4 2018, Q1 2019	Clearly stated decision	Because... Because...	e.g. mock-up, JIRA issue
Loans	Emma Boettcher		Prioritize search & filter of claimed list first, then search tracking, then report where you could access all claimed actions	Relatively small volume of claims/year. Searches are trackable on paper, but could provide foundation for sending out notices

Notes

Emma asked SIG members to rank the importance of different element of the UXPROD-532 Claimed Returned list functionality. There was agreement that export, search and filter of the list of Claimed Returned items was the most important. The capability to track the number of times an item was searched for was ranked as the second most important feature. David said that at Texas they have found that sending out notices to patrons telling them that the item has been searched for, and reminding them to do their own search for the item, has been very helpful in getting items returned. The ability to take actions, such as Declared Lost, etc. directly from the list was ranked as the third most important feature.

Emma will do a JIRA for the ability to cancel a Claimed Returned to handle the case when a patron says they returned an item and then a minute later says "Oh, I do have it here after all".

Brooks discussed the desirability of having the last patron who borrowed an item being retained after loans are anonymized. Knowing who last borrowed an item is important in case it is discovered after an item is returned that there is damage to the item, or components are missing. Brooks said that currently the Last Borrower information is retained until the next patron borrows the item. He agreed that it would be nice to have an option where the Last Borrower information is erased after a set amount of time. Joanne agreed that retaining Last Borrower information is important as certain types of items, such as musical scores, are frequently returned with missing pieces. Andrea said retaining Last Borrower would be good to have as an option, where one could choose to have the Last Borrower information either i) immediately deleted; ii) retained for a certain time period; or iii) retained indefinitely. This would help countries that require GDPR compliance. Cornelia mentioned that while their current system has the ability to retain Last Borrower information, they are required to turn this feature off.

Travis asked that this feature be ranked by the different institutions. Jana asked for the SIG members to contact her with any suggestions, issues, etc. and she would put the topic on a future meeting agenda.

Cate introduced the discussion of how the pandemic has changed the way libraries operate, and whether any of the changes may become permanent. Andrea pointed out that after a new service is provided, it can be difficult to take the service away (mentioning mailing books out to patrons, for example). Andy mentioned how often notifications have had to be re-written.

There was discussion over whether FOLIO needs to provide a way of over-riding the request queue. For example, if there is a request on a book, but a patron physically brings the book to the circulation desk, there should be a way to over-ride the request and allow check-out. Currently FOLIO does not allow this.

Cheryl mentioned that the ability to do batch updates of due dates, and reset the number of times an item has been renewed, has been vital. SIG members all agreed that the capability to do batch updates to due dates, etc. is essential when dealing with events that force library closure.

Cate said it would be good to rank the features libraries would like to have for dealing with disruptive events.

Browser not supported