| No Product Council Meeting | | Vision & Strategy working group met. Nothing yet to report. |
| Subgroup & other updates/announcements? |
| - Bound-with Update: A small group met with developers to convey idea of single item to multiple holdings. While the developers understood the model proposed and called it "elegant" and it is possible, it would mean a lot behind the scenes. Proposing a different model - item for each bib, but properties like barcode would not stay in all items, there would be a "super-item" - multiple items united in some way.
- https://docs.google.com/drawings/d/1y8tdyNXjsGKT6QFJWPajMjH5kNYDdyVU5aXaXAskfd4/edit?ts=5f4553f0 (Super Item, model 2)
|
| Printing Use Cases, Next Steps? |
| https://docs.google.com/document/d/17yBc6YvJqjmoiu-GVTxxn4isesE_XX2dgHqCudn2Um8/edit Can there be a FOLIO wide solution? Should discussions with app interaction group be considered? Please add use cases to the document linked above. PDF is desired formatted formatted outcome. |
| Data Import Development Update | Ann-Marie Breaux (Deactivated) | Slides: https://docs.google.com/presentation/d/16ulhbwArz2OzRSNKLIkZw8coQe9ks2frUoYU51KXfHw/edit?usp=sharing - Need ability to do a batch checkin or other protected fields that may need to be changed in batch. (Batch check in use case - if items are being withdrawn, they may need to be checked in first.) Maybe be out of scope for data import.
- Jen (via chat) - "When we talked about this in the little group we talked about batch circ operations being part of the circ apps"
- Status changes can be done through APIs - noted by Christie Thomas.
- Charlotte (via chat)
|
| Future MM meetings (ongoing) |
| Add ideas here https://docs.google.com/document/d/1u1tvfVxn6i3fTImrWWCYHlh7RT5cf3_G7YgDuxKob4M/edit
|