| Jira Legacy |
|---|
| server | System JIRA |
|---|
| 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 |
|---|
|
Background
This workflow is in reference to Acquisitions/Resource Management implementers topic #54, and is intended for requirements analysis. The topic was initially raised by Sara Colglazier.
| Requirement | Status | Priority | User story |
|---|
| Library staff must be able to identify titles or pieces to be bound | | | Staff member creating an order knows the material associated must be bound at some point and needs to be able to designate the material appropriately. Staff member receiving a piece may recognize that the material will need to be bound and needs to be able to designate the material appropriately |
| Library staff must be able to designate materials that have been sent to the bindery as being unavailable because they are being bound | | | A set of materials has been identified as being ready to be bound. Staff member pulls the materials and designates them as "unavailable - at bindery" in both staff and public displays. |
| Library staff need a workflow to reduce multiple unbound pieces into a single bound piece | | | Serial comes out quarterly and each issue is barcoded and entered into the system. When final piece of a volume arrives, the 4 issues are pulled and bound together. There should be a means of condensing that volume to a single barcode and single item, and this should also be reflected in staff and public displays. |
|
|
| Handling of incomplete volumes (missing issues, end of run...) |
|
|
| Tracking of staff handling (who handled, when) - audit trail |
|
|
| Monograph handling |
|
|
| Accounting for title changes (supplement, item record goes on later title) - Bound with logic might work here. Share item record between 2 Instances? (Most commonly retrospective cataloging, uncaught title changes) |
|
|
|
|
|
|
|
|
Definitions
- Bound volume - a group of periodical issues of the same title that are bound together after publication. A bound volume may or may not reflect a periodical "volume".
- Bound volume unit - the number of issues/pieces associated with a given volume which are bound together to create a bound volume.
- Volume - the top level of enumeration of a serial (journal or periodical.) Volumes increment on a periodic basis, with annual increments being the most common. Some periodicals use the year in place of the volume number.
- Issue - the second level of enumeration of a serial. When present, issues are associated with a given volume, and reset when the volume increments (e.g. Vol 86 Issue 6 → Vol 87 Issue 1). Some periodicals use the month in place of the issue.
- Supplement - an additional piece associated with a given Volume, but published outside the standard Volume/Issue structure. May or may not be present.
- Index - an index to a given Volume, published outside the standard Volume/Issue structure. May or may not be present.
...