Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

TBD

Problem(s):

  1. Users are not able to see expected or received pieces for multiple titles at one time, in one place

Use Cases & Requirements:

RequirementStatusUse cases
Ability to export pieces directly to csv file

Status
colourYellowGreen
titlePendingVerified

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

Status
colourYellowGreen
titlePendingVerified

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

Status
colourYellowGreen
titlePendingVerified

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

Status
colourYellowGreen
titlePendingVerified

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

Status
colourYellowGreen
titlePendingVerified

To support workflow for received pieces we would need to include Barcode and Call number, Enumeration, Chronology, Caption, Copy number, Location.


Proposed workflow:

Miro
AccessLinkhttps://miro.com/app/live-embed/uXjVO2BTKtw=?boardAccessToken=675D9NgTnOrl6Qppyv1EnNqfxHcadWiH&autoplay=true
Height360
BoardTitleExport pieces in delimited file formate
Width640


Questions:

Questions

Status

Conclusions

Comments


Status
colourBlue
titleopen




Work Breakdown Structure:

Features:


UI Stories

Jira Legacy
serverSystem JiraJIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQuery(issuekey in linkedIssues("UXPROD-3435") AND project in (UIOR, UIREC, UIV, UIF, UINV, UIORGS, STFORM, UIAC, UIPFO, UIPFCONT, UIPCITEM, UIPFINT, UIPFPOL))
serverId01505d01-b853-3c2e-90f1-ee9b165564fc

MOD Stories

Jira Legacy
serverSystem JiraJIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQuery(issuekey in linkedIssues("UXPROD-3435") AND project in (MODORDERS, MODVEND, EDGOAIPMH, EDGORDERS, MODCRED, MODFISTO, MODFUND, MODGOBI, MODINVOICE, MODINVOSTO, MODOAIPMH, MODORDSTOR, MODREC, MODORGS, MODINV, MODCONF, EDGOAIPMH, mod-organizations-storage, mod-organizations, MODEBSNET))
serverId01505d01-b853-3c2e-90f1-ee9b165564fc