2017-12-04 Resource Access Meeting Notes

Date

04 Dec 2017

Attendees

• Cate Boerema (Deactivated)
• David Bottorff
• Ginny Boyer
• Darcy Branchini
• Mark Canney
• Tania Fersenheim
• Deb Lamb
• Joanne Leary
• Cheryl Malmborg
• Holly Mistlebauer
• Carsten Schwill
• William Weare
• Wendy Wilcox

Discussion items

Notes

Andrea Loigman out; Cate Boerema facilitated.

1. Tania Fersenheim

Request details screens—questions

Nov—we talked about the request details screen

Left column: 

Added Request Status (Request Type already there):

1 Open – not yet filled
2 Open – awaiting pickup
3 Closed – filled

Right column:

Added request status

Item status is now a link so that status is one screen away
Number of requests: this number is now linked as well
Position in queue is in request details section

Should the request details section be at the top?
Suggested order:

• Request details
• Item info
• Requestor info

Note: we are not looking at a version that a designer or UX person has seen; this will be cleaned up; Tania is verifying that the data elements are right.

Tania will let UX people know how we would like these grouped/ordered.

Questions, re: closed request:

Is there any data on request details that is problematic on a closed request?

• Discussed scrubbing of data, re: patron information; can we leave out name of requestor?
• How much information do we want to keep, re: closed, filled; closed, cancelled, etc.?

On a closed request, is there any data that should be editable?
No.

Can we added notices info, notices sent, some access to information about notices?

2. Holly Mistlebauer

Currently researching automated fees & fines, but went through parking lot issues.

Patron block specs:

What types of blocks?

• Too many books checked out; too many of this item/any item checked out for anyone/patron (automated)
• Too many items have fines owed (automated)
• Fine balance is too large (automated)
• Patron record is expired
• Overdue recall (separate from overdue book)
• Lost book block (automated) – too many items lost
• ILL/ILS block
• Generic manual block (manually supply the reason)
• Mail block (manual)—address doesn’t work anymore
• Five level system: fine amount, number of fines
• Need to be able to override these – and capture who did the override. Leave blocks in place after override. Each block needs to be overridden.

Need to set limits for institution as a whole or unit libraries?Both. Can do for entire library or unit libraries.

What type of automated blocks? How do they get set?

What type of manual blocks? How do they get set?

What do blocks do? Stop checkout. What else?

• Stop placements of requests (holds/recalls)
• Stop renewal (eventually)
• (Depends on library and type of block)

Where should blocks be displayed? (“Blanket block” vs. “item level block”)

• User details
• Checkout (patron data)

How is block removed?

• Automated
• Manual

Allowed to renew items that were checked out before the block went into effect? Yes, for too many items checked out, but maybe no for others. Library needs to be able to specify if this is allowed. (Loan policy has Y and N for renewals).

Need to provide very clear explanation to staff and patron as to why the transaction is being blocked.

Holly will set up this information as a table so we can review this more easily.

Meeting ended at 10:55. No kidding.