2019-9-12 Resource Access Meeting Notes

2019-9-12 Resource Access Meeting Notes

Date

Sep 12, 2019

Attendees

  •  

    • @Andrea Loigman

    • @Cate Boerema (Deactivated)

    • @Cheryl Malmborg

    • @Mark Canney

    • @Andy Horbal

    • @Schwill, Carsten

    • @Laurence Mini

    • @Cornelia Davis

    • @Darcy Branchini

    • @David Bottorff

    • @David Larsen

    • @Donna Minor

    • @Elizabeth Chenette

    • @Emma Boettcher

    • @(OLD ACCOUNT) Erin Nettifee

    • @Kai Sprenger

    • @Kimie Kester

    • @Rameka Barnes

    • @William Weare

    • @Holly Mistlebauer

    • @Joanne Leary

    • @mey

    • @Catherine Smith

Discussion Items

 

Time

Item

Who

Description

Goals

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.

 

Meeting Outcomes

Functional Area

Product Owner

Planned Release (if known)

Decision Reached

Comments

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.)

 

Notes

Andrea: Link to MVP review in agenda. What is not MVP that we need to discuss? Please get back with Andrea about any gaps ASAP.

Cate: Discussed performance goals for barcode scanner and RFID scanner. Barcode scan should be well under 1 second; at or near 1 full second would be too slow.

Emma: Renewing Lost Items. If loan policy is set to renew from due date rather than system date and new due date would be in the past, loan should be renewed through modal. What if multiple items are being renewed and one of the items would be past dated? Not clear which partners would prefer renewal from due date.

Holly: In "lost item returned" configuration there are two options: 1. charge overdues. 2. remove overdues. What about "lost item renewed"? Should there be the options? Most on the call would set them the same but minimal development work to seperate two scenarios.

Emma: 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.