Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Current »

Problem(s):

  1. Identify the status of all related orders for a specific title requires too many clicks if user needs to navigate to Holdings.

  2. Identifying what other users/units have order the instance already.
  3. For someone with only cataloging permissions it can be difficult and time consuming to retrieve acquisition information from ACQ apps.

Instance - Use Cases & Requirements: 

RequirementStatusUse cases

Include a column for Order status

Include a column for Location

VERIFIED

  • Being able to quickly identify the status of pending, open or closed orders for a specific title and also to see what location they relate to. This would allow user to quickly see if someone else is already planning to order, has ordered, or is waiting for an order to be filled for this title.
Include a column for Acquisition unit

VERIFIED

  • For libraries that leverage acquisition units it would be ideal to see that data on the instance with order info. Making it clear whether other institutions in the system have already ordered something.
POL number is hyperlink. Clicking it takes user to the POL  view in the orders tab of the orders application

VERIFIED

  • Important to show POL number as a hyperlink so it is easy to retrieve more information if user has permission to

Include column for Date ordered

Include column for Order type

Include column for Receipt date

VERIFIED

  • Need to be able to identify when the order was sent, what type of order it is and what the receipt status is. 

Item - Use Cases & Requirements: 

RequirementStatusUse cases

POL number is hyperlink. Clicking it takes user to the POL  view in the orders tab of the orders application

VALIDATED

  • As a circulation staff I want to have easy access to order information relevant for any given search in Inventory.
    When I find what I'm looking for - the given patron request - then I want to have easy access coming from the Inventory, item record and do not want to repeat my search in another app, e.g. the the Order app..
  • Where searching criteria is different seeing information from acquisitions in inventory may allow you to find acq information more efficiently than you could by searching orders directly.
Include column for POL Receipt Status

VALIDATED

Receipt status of the POL may not indicate that the actual piece related to this item has been marked as received.
Include column for Acquisition unit

INVALID

Generally there are other data points at the item level that clearly communicate which group is responsible for an item. Location, holding etc.
Include column to Display Vendor code

VALIDATED

I may have items on the same instance ordered through different vendors

Include column for Subscription Y/N

VALIDATED

Investigating whether this was a firm order or a standing order. Helpful to see Subscription Y/N so that user knows whether an ongoing order is a standing order vs. subscription. This may change the way they follow up on the order.

Include column for "Piece Receipt date"

VALIDATED

When viewing the item it would be helpful to see when something has been received. Specifically that item not the POL in general. This also implies whether it is expected or not. 
Provide hyperlink to the receiving history

VALIDATED

To make it easier to access receiving information and confirm what other "Pieces" have been received. Prevent the need for users to go and run a separate search in the receiving app

Proposed workflow:

  • Display Acquisition accordion on Instance record
  • Populate accordion with order information from all POLs that contain a reference to that instance. Ie. All POLs connected that that instance

  • Display Acquisition accordion on Item record
  • Populate accordion with order information from Piece that contains a reference to that Item.


Questions for Users:

Question

Status

Conclusion

Comments


OPEN







Questions for Vendors:

Question

Status

Conclusion

Comments


CLOSED



Questions for Developers:

Question

Status

Conclusion

Comments


OPEN



Work Breakdown Structure:

Features:

UXPROD-3344 - Getting issue details... STATUS

UXPROD-1995 - Getting issue details... STATUS



UI Stories

MOD Stories

  • No labels