...
| Product Council Update | Meeting minutes: https://docs.google.com/document/d/1SI5b0xZ6Hs2RpadVG043omIiN9_zJAJTEdYNXu1Q1Yg/edit Dracine suggested reading the minutes - there are many helpful links in the minutes. | |||||||||
| Subgroup & other updates/announcements? | No updates | |||||||||
| Item Status Subgroup Update | recent decisions 3-part item status (item state): availability (currently called item status) – not repeatable, required process – what are staff doing with this item? not repeatable, not required needed for – what processes should this go into? repeatable, not required see Emma's slides for details and examples process & needed for are not necessarily intended to be used for routine workflows; values for these are configured by individual institution, as are some of the behaviors (e.g., pop-up notifications) -why is this being developed rather than just using holds? it gets rid of need for "dummy" user records, keeps some staff (e.g., catalogers) from needing access to circulation functionality & user data, and is better for reporting, plus will interface better with workflow engine (in future) epic for item states:
Tracking status history (proposed functionality) – would be helpful to know if a change was made via batch process | |||||||||
| Bound-with Subgroup update | Basic idea of proposed model: single shared item for volume, can be linked to multiple holdings records Lots of other options & possible ways to treat these This is not the same as the instance-instance linking for analytics (though analytics may also be bound-with) | |||||||||
| Future MM meetings (ongoing) | Add ideas here https://docs.google.com/document/d/1u1tvfVxn6i3fTImrWWCYHlh7RT5cf3_G7YgDuxKob4M/edit |
...