Item states (status) (UXPROD-1321)

[UXPROD-2635] Item status: Orders - Customize item status behavior Created: 26/Aug/20  Updated: 24/Jan/24

Status: Draft
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: Item states (status)

Type: New Feature Priority: TBD
Reporter: Emma Boettcher Assignee: Thomas Trutt
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Cloners
is cloned by UXPROD-3928 Item status: Receiving - Customize it... Draft
Defines
is defined by UIOR-573 Custom item status: orders and receiv... Open
is defined by UIOR-1033 Customize orders and receiving behavi... Closed
Gantt End to Start
has to be done after UXPROD-1535 Item status: Create interface to crea... Draft
Relates
relates to UX-369 Mockup for CRU custom item statuses Open
Epic Link: Item states (status)
Development Team: None
PO Rank: 79
Rank: Chicago (MVP Sum 2020): R3
Rank: Cornell (Full Sum 2021): R3
Rank: 5Colleges (Full Jul 2021): R3
Rank: GBV (MVP Sum 2020): R3
Rank: U of AL (MVP Oct 2020): R2

 Description   

Current situation or problem:
Orders and Receiving apps can change item status, but only in certain cases:

  • When the order with an attached instance/holding/item is closed prior to the item being received, the item status changes from On order to Order closed
  • When an item with the item status On order is received, the item status changes to In process

Closing orders and receiving items does not affect the item status of items with any other statuses besides the ones listed above.

In scope

  • Configure what item status change happens when an order with an attached instance/holding/item is closed prior to the item being received.

Out of scope

  • Changes to receiving app (covered in separate feature)
  • Changes to serials app (covered in separate features)

Use case(s)

  • A library wants to implement a process whereby, if an order is closed prior to the item being received, the items are reviewed for open requests and then withdrawn. Instead of having the item status of Order closed, they want the Orders app to change the item status from On order to a custom status, Never received, after which they review the items and the mark them as withdrawn.
  • A library wants to be able to have orders create items, but have some types of orders create items with a status of "On order", and some types of orders create items with a status of "Unavailable", and some types of orders create a status of

Proposed solution/stories

Links to additional info

Questions



 Comments   
Comment by Jacquie Samples [ 30/Sep/20 ]

If we are talking about adding a local item process (aka item status), and not adding a new type of item state, then we do agree that this functionality should be developed. However, this should not be contained to just orders and receiving. This is cross-app functionality, not one that is only applicable to the Orders and Receiving Apps. We (Duke Metadata Team) are not ranking this Jira today since we prefer that time be spent on creating the 3-part item state over customizing the current model's item status.

Comment by Kristin Martin [ 23/Oct/20 ]

From Chicago: At this point, we are not planning to use custom item statuses for real items that will be ordered or received and will initially limit our use of custom item status to DUMMY items (like for analytics or other items where we have an intellectual representation but not a true item). So I don't think we'll initially be using custom item status in the acquisitions workflow, but I might be missing a use case.

Generated at Fri Feb 09 00:25:36 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.