once we get to title level requests (not V1), some mechanism to alert library with another copy on hold as to what they need to do
in general we think no messages on screen if operator does not need to take action
too much noise causes you to tune out important alerts "alert fatigue" (hospital community)
reports for patterns of mistakes, etc.
needs to be routed to another library for another patron
system needs to know it's traveling again, but can checkout app do that or do you need to check it in again?
check in from failed checkout is okay if technically possible but not a priority
David W - what about overrides? vs going into request queue and fixing issue, ability to roll back an awaiting pickup to existing request; which should we ask for now?
Andrea-we should fix requests.
David-the same business logic would apply, so build the manual logic for rolling back to unfulfilled, notifying the patron, etc. almost like building a macro
group agrees to thisĀ
in transit to this location for a different patron - similar issues, requires check-in
item is not awaiting for pickup but has another request. Tell the operator and allow checkout or not? what about how to deal with requests for course reserves, could checkout be blocked by borrower type in rules? that would mean no need for special "staff request" type
tania-this exercise has been enlightening about details of workflows, fascinating
5 min
Wrap-up
All
Next steps / homework (no homework)
Action items
Create a wiki.folio account if you don't already have one