Go through use cases for Availability, Needed for, Process
Notes
Use Case: Item is checked out to a patron and is needed by staff for some process (e.g., cataloging)
Options: 1. Check-in does nothing, 2. Check-in moves item to In Process, 3. Check-in places item In-Transit
Are there confidentiality issues?
What about simplicity issues? Whatever cataloging does needs to be simple/easy
MM-workflow/functionality needs to be built into inventory, like a button that says "start cataloging"
Christie likes in transit-could let you know that items are in backlog
What about use cases where staff would not be going into inventory (e.g., preservation, digization, etc.)
what about the need from a specific staff member, how do we indicate who are what unit? need for staff request? need to record the reason why the staff member requested it (they may not remember why)
Need to track the who, when, why, note field for the why (possibly optional)?
Needs to as low friction as possible
select a needed for with an optional note field for why?
something cannot be "needed for" a specific process and then also be in the "cataloging" process
pop up displaying the "needed for" note when placed into cataloging process would be helpful
Use case:What happens when cataloging process is done?
do cataloging staff have to sign off that a process is complete?
does it happen automatically when item is checked in?
Is it going back on the shelf or does it go to unit for physical marking? that would be a different needed for and a different process
Laura likes ides of cataloger signing off that cataloging process is done, but could also see an issue if it's not completed consistently
Erin feels as though the process needs to be started AND ended
David-What are we willing to live with before a fully fleshed out end state? Would it be better to have a process that ends automatically at check-in or no process at all (just fulfilling needed for)?