| Jira Legacy |
|---|
| server | System JiraJIRA |
|---|
| columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | UXPROD-4093 |
|---|
|
...
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 | | - A library receiving a serial following a Volume/Issue pattern will typically want to bind all issues associated with that Volume into a single bound volume
- Very large serials may need to be split into multiple bound volumes, requiring distinct enumeration (e.g. Volume/Part)
- A library may choose to bind multiple Volumes into a single bound volume
|
| Identify pieces that are ready to be sent to the bindery | | 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 | | 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 | | - Issue-level holdings should be condensed into a single volume-level holdings statement, accounting for any gaps
- Items associated with individual pieces should be condensed into a single item record reflecting the entire bound volume
|
|
|
|
Requirements Board
| Miro |
|---|
| AccessLink | https://miro.com/app/live-embed/uXjVMavxnKk=/?boardAccessToken=ST8sGdtObkqqLexJa7U4wz49FGjVZWLr&autoplay=true&embedMode=view_only_without_ui |
|---|
| Height | 360 |
|---|
| BoardTitle | Sending serials to be bound |
|---|
| Width | 640 |
|---|
|
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? | |
|
|
| Is bindery typically treated as a subset of receiving, or is it an entirely distinct workflow? | |
|
|
| What additional output is required from the LSP to send to the bindery, and what format does that output take? | |
|
|
| Do we need to account for monographs/paperbacks? | |
|
|