Versions Compared

Old Version 4

changes.mady.by.user Dennis Bridges

Saved on

compared with

New Version Current

changes.mady.by.user Dennis Bridges

Saved on

Key

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

Table of Contents

Problem(s):

  1. Adding titles to package POLs is not an intuitive user experience. User are getting lost between the orders app and the receiving app before completing the creation of the package POL

  2. Needing to add pieces one at a time is very cumbersome given the number of pieces that need to be created and received

  3. Informing receiving librarians of what is expected next and what has already been received
  4. Managing changes in expected material when things are merged or skipped

Use Cases & Requirements:
Jira Legacy
serverSystem

Jira

JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-194

RequirementStatusUse cases

Status
colourYellow
titlePending



Status
colourYellow
titlePending


Use Cases & Requirements:
Jira Legacy
serverSystem

Jira

JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-1581

RequirementStatusUse cases
  • Ability to add title to receiving with no link to POL
    • Ability to add pieces as needed for that title
    • Ability to create inventory records to represent these things

Status
colourYellow
titlePending

  1. Library receives a gift or MECAP or SACAP (PL480) material. This was never ordered but we want to receive to make sure it is managed correctly.
    • Can receive 30,000 of these pieces a year at large institutions. This could mean thousands of orders a year. And materials are both electronic and physical but the vast majority are physical
If no order was present there may be information that would have been captured there that needs to be added to the piece for reporting purposes (Eg. acquisition method, Material type)

Status
colourYellow
titlePending

  1. Receiving Back issues of a periodical (Could be 100s could be 1) and there was no order specifically put in for this but it must be received.

Use Cases & Requirements:
Jira Legacy
serverSystem

Jira

JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-2894

RequirementStatusUse cases

Status
colourYellow
titlePending


Use Cases & Requirements:
Jira Legacy
serverSystem

Jira

JIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-3385

RequirementStatusUse cases

Status
colourYellow
titlePending


Use Cases & Requirements:
Jira Legacy
serverSystem

Jira

JIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-3179

RequirementStatusUse cases
Add a filter to the receiving area so users can filter for materials that were orders as "Rush"

Status
colourGreen
titleValidated

As an acquisitions staff member, I want to filter my receiving records by expected receipt date and whether rush is selected to ensure that I'm prioritizing the processing of these materials first.

As an acquisitions staff member, I want to be able to know if the invoice I am paying covers any materials that require rush processing.



Proposed workflow:

  •  (TBD)

Questions for Users:

Question

Status

Conclusion

Comments


Status
colourBlue
titleopen




Questions for Vendors:

Question

Status

Conclusion

Comments


Status
colourGreen
titleCLOSED



Questions for Developers:

Question

Status

Conclusion

Comments


Status
colourBlue
titleOpen



Work Breakdown Structure:

Features:

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
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-194

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
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-1581

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
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-2894

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-3385


UI Stories

MOD Stories