2018-03-15 Resource Access Meeting Notes

Date

15 Mar 2018

Attendees

• Andrea Loigman

• Wendy Wilcox

• Emma Boettcher
• Schwill, Carsten
• Holly Mistlebauer
• Tania Hewes
• David Bottorff
• Joanne Leary
• Deb Lamb
• Mark Canney
• Kimie Kester
• David Larsen
• Darcy Branchini
• Cate Boerema (Deactivated)
• Maria Grzeschniok

Discussion items

Notes

Cancel loan - Emma

• Feature originally brought up in August 2017 - what is it? Is it V1?
• Would be rarely used (mostly to correct items charged in error), would require very strict permissions
• Currently exists in Aleph
• Not a V1 issue - move to parking lot

Request screens - Tania

Request queue

• Post-launch: bulk actions, reordering the queue, implementing something other than a first-in-first-out model
  • Only way to re-rank requests in V1 is to delete & re-add requests
• Discussed having # of copies or presence of available copies on page, but not needed for V1
• Barcode links to the item in the inventory, and could explore other holdings from there
• Hold expiration date should appear - more important than request needed by date, though preference is for both
• Keep requester barcode - important for copy-pasting, which allows viewing data side-by-side
• Group approves with addition of hold expiration date

Cancel requests

• Can edit, cancel & view history of a request
  • viewing history of a request currently appears as "Change History" - needs to be changed to reflect "history of changes"
• Ability to flag a cancellation to notify user, which will be usable for Notifications subgroup

Refunds, patron blocks - Holly

Fines/fees settings at the institution level

• Confirmed: that the maximum fees/fines for a patron that prevents them from checking out items needs to be set by patron group
• "If a lost item is returned X time late, no refund shall be given" - is this a loan policy or a fine/fee policy
  • Decided it was loan policy
• Credits don't need to happen automatically for V1 - instead, system can run a report of "these items that were lost were returned" and staff can deal with that manually
• Discussion of replacement copies - trigger to record a replacement copy is always manual, but system's actions after that can be automatic

Patron blocks

• Too many items overdue
• V1: Fine balance (but not excluding types of fees from that balance)
• Item block, not patron block: patron trying to check out too many items or a type of item. Belongs with loans or item policies)
• Number of days something is overdue (may be equivalent to patron having items that have reached certain statuses - overdue, aged to lost)
• Overdue recall item
• Overdue ILLs - might have to be manual if systems don't circulate through their ILS, but if they do, item type or loan type could effect that

Action items

Emma Boettcher will enter cancel loans feature in parking lot

Tania Hewes will revise wording for "Change History" on cancel request screen and add hold expiration date to Request queue

David Bottorff will send Holly screenshots of the replacement copy process in OLE

Joanne Leary will send Holly config screens for patron blocks; Andrea Loigman and Cheryl Malmborg will see if they can extract information for Aleph and OLE, respectively