2023-01-09 Item State Working Group

Administrivia and settling in

(reminder to Erin - enable subtitles and turn on recording)

Resuming discussion about use cases for orders and receiving.

General interest in being able to track items through workflow stages. 

Lots of questions here about how things could potentially work, but also revealing the gaps of talking about these things without a workflow engine.

Resuming discussion of handling patron requests and rush requests. No infrastructure currently exists to meaningfully support rush requests. There is a checkbox on the order form, but no workflow behind that checkbox that does anything.

Item status could potentially provide information that would prompt the staff member doing the receiving to take a different action than normal.

General sense that implement(ed) libraries wanted to prioritize not  adding steps and making things more click-heavy for staff. Reinforce need to support individual tenant customization so libraries can decide what is important for them.

Also important to not introduce extra issues with batch loading. Lots of complexity here in desired behavior that libraries might want. E.g., an order is loaded and an item created, and later a record is overlayed that changes the item status. Might be desired, might be a big problem. Hard to say without more use cases.

Not able to necessarily determine what type of overlay might be fine, what type might warrant a notification, what type might warrant a stop/error message so the record isn't actually changed.