2020-07-20 Resource Access Meeting Notes

2020-07-20 Resource Access Meeting Notes

Date

Jul 20, 2020

Attendees

  • @Andrea Loigman

  • @Andy Horbal

  • @Emma Boettcher

  • @Holly Mistlebauer

  • @Brooks Travis

  • @Elizabeth Chenette

  • @Joanne Leary

  • @Anya

  • @Mark Canney

  • @David Bottorff

  • @Laurence Mini

  • @Kimie Kester

  • @Monica Arnold

  • @Molly Driscoll

 

Discussion Items

Time

Item

Who

Description

Goals/Info

Time

Item

Who

Description

Goals/Info

2min

Administrivia 

@Andrea Loigman

 

  • Notetaker - @Andy Horbal

15min

Renewals

@Emma Boettcher

Renewals on overdue loans

Decide: when a renewal results in a due date in the past (renewing an overdue loan from current due date), should it fail?

15min

 Circ log

@Emma Boettcher

Recording canceled check ins

When an item is scanned in the check in app but check in is canceled, should that be reflected in last check in date, circ log, in-house use count, others?

30min

Circ log

@Emma Boettcher and @Holly Mistlebauer

Actions in circulation log: Fees/fines

Decide what actions and what information about those actions relevant to fines/fees is worth recording in circ log (are full/partial payment separate actions, which information should be prioritized in description field, should create/update/delete of blocks be recorded as well)

 

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

 

Circulation log

@Emma Boettcher

 

Separate actions for paid fully vs. paid partially (and related)
Thin thread: show fee/fine type on all actions, and owner on the billed action

 

 

 

 

Loans

@Emma Boettcher

 

Fail renewal if it would not extend due date into the future

 

 

 

Loans

@Emma Boettcher

 

Record (and show) canceled check in circ log, check in screen, loan details. Don't count toward in-house use. Not MVP

 

 

 

Notes 

1. Circ log: Actions in circulation log: Fees/fines - Emma Boettcher & Holly Mistlebauer:

Decide what actions and what information about those actions relevant to fines/fees is worth recording in circ log (are full/partial payment separate actions, which information should be prioritized in description field, should create/update/delete of blocks be recorded as well)

Info all already exists, question is just what goes in log.

Payments will be shown in “Action” column as “Payment - Full” or “Payment - Partial” for sorting purposes. SIG agrees that these should be treated as separate actions.

Thin thread = NOTHING in the “Details” column is essential.

For Fees/Fines: type and fee/fine owner are more important than other elements to display and should be part of a thin thread. Waive reason also seen as something that is more important than other elements, but that doesn’t need to be part of a thin thread.

 

2. Circ log: Recording canceled check ins - Emma Boettcher:

When an item is scanned in the check in app but check in is canceled, should that be reflected in last check in date, circ log, in-house use count, others?

Consensus that check in should be shown on circ log, loan details, and check-in screen, provided CANCELED check-in status was very clear on screen.

Note that there is no existing pattern in current systems. Therefore probably doesn’t need to be MVP. Thin thread might consist of just capturing this information somewhere.

 

3. Renewals: Renewals on overdue loans - Emma Boettcher:

Decide: when a renewal results in a due date in the past (renewing an overdue loan from current due date), should it fail?

Example: if item has due date of July 1 and a renewal period of one week, it will renew to July 8 even if renewed on July 20. Should renewal fail? Consensus that renewals should fail if they don’t extend due dates into the future, but allow operator to override. They will be prompted to manually enter a due date.