2019-9-30 Resource Access Meeting Notes

2019-9-30 Resource Access Meeting Notes

Date

Sep 30, 2019

Attendees

  •  

    • @Andrea Loigman

    • @Holly Mistlebauer

    • @Kelly Drake

    • @(OLD ACCOUNT) Erin Nettifee

    • @Mark Canney

    • @Andy Horbal

    • @Schwill, Carsten

    • @Cate Boerema (Deactivated)

    • @Cheryl Malmborg

    • @Cornelia Davis

    • @David Bottorff

    • @Donna Minor

    • @Elizabeth Chenette

    • @Jana Freytag

    • @Kai Sprenger

    • @Kimie Kester

    • @Magda Zacharska

    • @Rameka Barnes

    • @William Weare

Discussion Items

 

Time

Item

Who

Description

Goals

Time

Item

Who

Description

Goals

5min

Housekeeping 

@Andrea Loigman

 

  • Notetaker - @Kelly Drake

  • October 3 is Unity Day Germany - no meeting. 

    • What about October 24?

30min

Patron blocks

@Holly Mistlebauer

Automated patron blocks

An understanding of how automated patron blocks should work for the MVP and whether patron notices are needed.

Reviewed original google doc listing various automated blocks required by institutions.

Patron blocks could be added to Patron group setting

Patron Blocks Action Table. - sets whether or not library blocks particular function Patron Blocks Limits Table indicated the actual block configuration when required

Blocks need to be set in real time.

Requirement as outlined is good for FLO and U of C. 

Holly felt it went really well. 

20min

Item blocks

@Holly Mistlebauer

Automated item blocks

An understanding of how automated item blocks work, so I know how to approach them (I've already seen Voyager).

Holly reviewed loan limits policy option as integrated into Circulation rules. 

  • Controlled by patron group and item types.

  • Need to set max checkouts by patron group

  •  - then subset by item type

  • And both need to be considered in each calculation.

  • Discussion of where and how best to configure item max blocks.

Alternate configuration would be an Item Blocks Limits table.

  • Might cause too much conflict with Circulation rules

Questions of system speed, ability to test policies, rule priority

There should also be a mechanism to limit the number of requests. 

Holly will continue talking with dev's to see what works best. 

 

Meeting Outcomes

Functional Area

Product Owner

Planned Release (if known)

Decision Reached

Comments

Functional Area

Product Owner

Planned Release (if known)

Decision Reached

Comments

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Notes