...
| 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-4087 |
|---|
|
| 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-4088 |
|---|
|
Background
This workflow is in reference to Acquisitions/Resource Management implementers topic #18, and is intended for requirements analysis. This topic was originally raised by Julie Brannon (old account)
| Requirement | Status | Priority | User story |
|---|
| Piece must be directed to specific users or departments rather than being processed as normal |
|
|
|
| Piece must be receivable as an "office copy" not otherwise accounted for in the broader scope of collections |
|
|
|
| Routing must accommodate both specific persons and locations without specific persons associated |
|
|
|
| Routing slip must be able to include address/office location information |
|
|
|
| Some materials are routed for different handling and processing via process other than the normal collection (common for pieces to be bound) |
|
|
|
| Must support latest to one reference collection and the next-latest gets moved to another collection etc. |
|
|
|
| Extra copies to offices, discarded when new edition comes in (X-copy 1, X-copy 2...) |
|
|
|
| Monograph and serial support |
|
|
|
| Temporary location currently under-utilized in Voyager |
|
|
|
| Routing is a daily workflow and process impacting pretty much all print serials |
|
|
|
| Routing list optionally printable (not always printed but always consulted) |
|
|
|
| Routing currently associated with patrons (CRS). Voyager considers a location as a patron for routing purposes. Collections are effectively patrons. |
|
|
|
| Status management is critical |
|
|
|
| Routing slip criteria... |
|
|
|
|
|
|
|
Description
Libraries may receive periodicals or other pieces which get directly routed to one or more users upon receipt. These materials may or may not be represented in the PAC and may or may not be included in the general collectionvarious collections. Routing often happens outside the normal circulation process, with each recipient receiving the material then passing it on to the next person when they're finished. The process is very informal, and may simply involve attaching a "routing list" to the piece, with the names of the recipients in the order in which they are to be passed along. The routing slip may include check boxes next to names, or recipients may simply cross off their names when they pass it along. When the material has been routed to everyone on the list, the library may then formally add it to the collection, informally place it in a reading room, informally place it in a staff area (most commonly for library-specific trade publications) or discard it.
...