2020-07-06 Resource Access Meeting Notes

2020-07-06 Resource Access Meeting Notes

Date

Jul 6, 2020

Attendees

  • @Andrea Loigman

  • @Holly Mistlebauer

  • @Jana Freytag

  • @Elizabeth Chenette

  • @Donna Minor

  • @Joshua Lambert

  • @Cheryl Malmborg

  • @Cate Boerema (Deactivated)

  • @Emma Boettcher

  • @Joanne Leary

  • @Kimie Kester

  • @Monica Arnold

  • Molly Driscoll

  • @Brooks Travis

  • @(OLD ACCOUNT) Erin Nettifee

  • @Laurence Mini

  • @Anya

  • @Joanne Leary

  • @Karen Mehl

Discussion Items

Time

Item

Who

Description

Goals/Info

Time

Item

Who

Description

Goals/Info

2min

Administrivia 

@Andrea Loigman

 

  • Notetaker - @Mark Canney

  • New convener coming!! - @Jana Freytag

30min

Lost

@Holly Mistlebauer  + @Cate Boerema (Deactivated) & @Emma Boettcher

Discuss priority/timing of finishing 'declared lost using actual cost' versus 'aged to lost.' The Core: Functional Team is working on both so we need to get the timing straight for planning purposes. When is each needed? What work arounds are available?

Decide order of work, if there is a workaround that can be developed to assist, etc.

Slide deck:  https://docs.google.com/presentation/d/10wgFbczVaI_l65PGOCJoVp3ajg90G5fWu34I63PNk60/edit?usp=sharing

 

20min

Searching

@Cate Boerema (Deactivated) & @Kimie Kester

Item search and select popup

https://folio-org.atlassian.net/browse/UXPROD-284

Item search and select popup is like the user search and select but for items. Used to browse and select an item record when you don't have the barcode in hand. This is needed for check out, check in, requests and possibly also acquisitions.

Kimie has a mockup for review and discussion.

 

Meeting Outcomes

Functional Area

Product Owner

Planned Release (if known)

Decision Reached

Reasoning

Link to supporting materials

Comments

Functional Area

Product Owner

Planned Release (if known)

Decision Reached

Reasoning

Link to supporting materials

Comments

e.g. loans, fees/fines

Name

e.g. Q4 2018, Q1 2019

Clearly stated decision

  • Because...

  • Because...

e.g. mock-up, JIRA issue

 

Fee/Fines

Holly Mistlebauer

Purpose of discussion is to decide on release

Order of work will be:  1) Aged to lost set cost; 2) Declared lost actual cost; 3) Aged to lost actual cost

See slide deck at right

https://docs.google.com/presentation/d/10wgFbczVaI_l65PGOCJoVp3ajg90G5fWu34I63PNk60/edit?usp=sharing

 

 

 

 

 

 

 

 

Notes 

@Holly Mistlebauer  presented discussion of Aged to Lost/Declared Lost with actual cost and set cost logic.

Aged to Lost (UXPROD-87) is a go-live requirement for many US Libraries but ranked lower for non-US. The development time is marked "Jumbo > 45 days".

Aged to lost is an item status, system assigned. But not available yet. Other user stories involve notices, fees/fines, blocks, etc. Development is moving from UNAM to Core to improve development velocity. Holly identified four paths for development:

Declared Lost using "set cost". UXPROD-2548. Mostly completed, still need to add impact to fees/fines in case of renewal. Also, need to work on patron notices.
Declared Lost using "actual cost", UXPROD-2391.
Aged to Lost using "set cost". UXPROD-87.
Aged to Lost using "actual cost", UXPROD-87.

Who needs what, when?

1. Declared lost using actual cost
2. Aged to lost using set cost
3. Aged to lost using actual cost

Prioritization from discussion:

#1. Declared lost using actual cost
#2. Aged to lost using set cost
#3. Aged to lost using actual cost

See slides to view/add discussion: https://docs.google.com/presentation/d/10wgFbczVaI_l65PGOCJoVp3ajg90G5fWu34I63PNk60/edit?usp=sharing