2019-9-12 Resource Access Meeting Notes

Date

12 Sep 2019

Time	Item	Who	Description	Goals
5 min	Housekeeping	Andrea Loigman		Notetaker - Mark Canney MVP review - homework - review and determine what non-MVP items you want to discuss. Let Andrea know so that I can try to make sure the appropriate capacity team folks can be at our meeting.
5min	Performance	Cate Boerema (Deactivated)	Update on check in/check out performance	Conveyed the performance goals discussed in the Sept 5 meeting to the developers. They are interested in keeping the barcode scanner and RFID scanner use cases separate for now. Depending on how staff need to interact with check in popups when using RFID scanners, we may need to make other adjustments to API. I've requested a screencast of current system from Carsten. Anton has created a wiki page to document our performance SLAs: Performance requirements for daily operation of the FOLIO system
10min	Lost	Holly Mistlebauer	Lost item return messaging	Asking if setting "If lost item returned" should be changed to "If lost item returned or renewed."
10min	Lost	Emma Boettcher	Lost renewals	Decide whether renewing lost items should follow loan policy, or ask user to choose new due date.
20min	Claims returned	Emma Boettcher	bulk claims returned	Decide whether to use existing patterns for bulk claim returned, or to introduce new pattern.

Functional Area	Product Owner	Planned Release (if known)	Decision Reached	Comments
Loans	Emma Boettcher	Q4	Renewing lost items: calculate the due date, and ask user to manually select due date if it is in the past	Cannot always ask user to manually select due date, because that is inconvenient for loan policies that renew from system date
Loans	Emma Boettcher	Q4	Claim returned: can use bulk renewal/change due date pattern when changing multiple items to claim returned. When resolving a claim returned item as Missing or Declared lost, include space for notes to be stored on user record (not loan), and store some information, like how the claim was resolved, automatically.	Decisions made without visuals; may need to confirm with visuals (separate comments fields for patron or staff-only, e.g.)