TBD
Problem(s):
- Users are not able to see expected or received pieces for multiple titles at one time, in one place
Use Cases & Requirements:
| Requirement | Status | Use cases | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Ability to export pieces directly to csv file |
| We filter receiving records based on what is "past due" (Beyond its expected receipt date). This list of pieces is used to manage follow up with Vendor, claim and troubleshoot so that the library can be sure they have or will receive the ordered material. | ||||||||
| csv file can include pieces from multiple titles |
| Ideally we can produce a list of all Pieces for staff to work through. Staff members are not always focused on one specific title. Often it is a handful of titles that require attention. For larger orders it could be a handful of title from one specific vendor. | ||||||||
| Allow the export of expected pieces |
| Librarian is working on claiming unreceived pieces and must produce a list for the vendor and for keeping track of the effort required to move forward different claims. | ||||||||
| Allow the export of received pieces |
| We would print a list of received pieces for a student and send them to the stacks to collect the material for binding etc. | ||||||||
| include Barcode and Call number, Enumeration, Chronology, Caption, Copy number, Location. Include in the export data |
| To support workflow for received pieces we would need to include Barcode and Call number, Enumeration, Chronology, Caption, Copy number, Location. |
Proposed workflow:
| Miro | ||||||||
|---|---|---|---|---|---|---|---|---|
|
Questions:
Questions | Status | Conclusions | Comments | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
|
Work Breakdown Structure:
Features:
UI Stories
| Jira Legacy | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
MOD Stories
| Jira Legacy | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|