Bindery Support
- UXPROD-4093Getting issue details... STATUS
Problem(s)
Libraries that receive or act as a primary repository for printed serials often bind single issues into hardcover volumes once certain criteria have been satisfied (typically the receipt of a fixed number of pieces or a complete logical volume.) These libraries need to identify pieces to send to the bindery, update item and holdings statuses accordingly, and receive and process the condensed bound volumes.
Use Cases & Requirements
Requirement | Status | Use cases |
---|---|---|
Specify the criteria for identifying when a group of pieces should be sent to the bindery | PENDING |
|
Identify pieces that are ready to be sent to the bindery | PENDING | A library needs to know when a full set of pieces is ready to be bound, and needs a mechanism for identifying the specific pieces to be pulled (if needed) and bound. |
Update public display to reflect unavailable pieces | PENDING | Pieces that have been sent to the bindery should have some sort of status or setting in the public display indicating they are unavailable. |
Condense holdings to reflect bound status | PENDING |
|
Requirements Board
Questions
Question | Status | Conclusion | Comments |
---|---|---|---|
Is there a case where the unit to be bound will be determined by number of pieces rather than chronology and enumeration? | OPEN | ||
Is bindery typically treated as a subset of receiving, or is it an entirely distinct workflow? | OPEN | ||
What additional output is required from the LSP to send to the bindery, and what format does that output take? | OPEN | ||
Do we need to account for monographs/paperbacks? | OPEN |