...
Time | Item | Who | Notes |
---|---|---|---|
5min | Housekeeping |
| |
10min | WOLF-Con recap | types of item statuses | |
30min | Item statuses | Slides |
Notes
Housekeeping: Andrea
Announcements:
Mark Canney: demo of loans + fees & fines (Holly & Emma); August 15
Andrea Loigman: Next week includes July 4; we will meet on July 2 and July 5
Discussion:
WOLFcon Recap: types of item statuses (Emma Boettcher)
Item statuses (Emma Boettcher, Tania Fersenheim)
From WOLFcon discussion:
- Move away from compound statuses
- How this will be implemented
- What’s missing from just these two pieces of information (availability, needed for request)
[Three columns/lists]
Availability | Needed for [request] | Process
Availability—examples:
- On order
- In process
- Expected
- Available
- Checked out
- In transit
- Recently returned
- Claim returned
- Awaiting pickup
- Aged to lost/grossly overdue
- Lost (declared lost)
- Missing (from the shelf)
- Long missing (from the shelf)
- Withdrawn
Discussion:
What’s missing? Suggestions:
Reserves process status(es)
Available
Processing (recall, request for purchase, etc.)
Flagged as needed for reserve (to prevent checkout)
Item status specific to acquisitions
Could we change “needed for request” to just “needed for” to accommodate other types of requests?
Request has many complicated components;
Needed for: preservation, cataloging, etc.
Needed for means needed for a workflow;
Process means item in the workflow
Needed for—examples:
- Patron request
- Reserve
- Cataloging
- Preservation
- ILL
- Digitization
- Individual staff member
- Access service review
- Exhibit (internal, external)
- Special shelving (new books, spotlight)
- Transfer to off-site (“re-homing”)
- Weeding
- Bindery
Process ("in the middle of")—examples:
- Preservation
- Binding
- Search
- ILL
- Accessioning
- Claimed (not claimed returned)
- On exhibit
- Special shelving
Nearly everything in the second column would have a corresponding process in the third column.