Item states (status) (UXPROD-1321)

[UXPROD-3859] Item status: Check in - Customize item status behavior Created: 19/Oct/22  Updated: 30/Nov/23  Resolved: 21/Dec/22

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

Type: New Feature Priority: TBD
Reporter: Erin Nettifee Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Cloners
clones UXPROD-3653 Item status: Requests - Customize ite... Draft
Duplicate
duplicates UXPROD-2606 Item status: Check in - Customize beh... Draft
Relates
relates to UXPROD-3653 Item status: Requests - Customize ite... Draft
relates to UXPROD-3860 Item status: Checkout - Customize ite... Draft
Epic Link: Item states (status)
Development Team: None
PO Rank: 0
Rank: Cornell (Full Sum 2021): R2

 Description   

Current situation or problem: Libraries would like to be able to create custom item statuses to support specific workflows. This feature is meant to encompass work for custom item statuses specifically for check in workflows.

In scope

  • An item's status controls whether an item can be checked in. If the item is not allowed to be checked in, the app presents an appropriate modal.
  • An item's status controls whether an item check in must be confirmed. If the item allows check in with confirmation, the app presents an appropriate modal, and the FOLIO staff user must click the appropriate button to continue the check out transaction.
  • An item's status controls whether a warning is presented if the item is suppressed from discovery. If the item is suppressed from discovery, and the option is chosen to notify the FOLIO staff user, the Check in app presents an appropriate modal when the item is checked in, and the FOLIO staff member must click the appropriate button to continue the check out transaction.

Out of scope

  • Change in circ rule behavior. Currently, if the circ rule allows something but the item status doesn't, the item status wins. If the circ rule doesn't allow something but the item status does, the circ rule wins. Essentially, a conflict defaults to not allowing.

Use case(s)

  • A library wants to implement a custom item status to indicate that an item was lost and the patron provided a replacement copy. They call this item status "Lost and replaced." Essentially, once this happens, the patron "owns" the lost and replaced item and the library doesn't want it back. In these cases, if the book happens to reappear and be scanned in the check in app, the library wants to deny check in and present an appropriate message to the library staff member so they know what is happening and why.
  • A library implements an item status for controlled digital lending. When an item is out on controlled digital lending, the physical copy is held in inaccessible storage since the digital copy is "circulating." When the CDL loan is complete, the library wants the physical item to become available again, but they also want to make the staff member confirm the check in of the item so that they are consciously choosing to change the item status to "Available".

Proposed solution/stories

Links to additional info

  • This work and associated stories was broken off from the original feature UXPROD-1535 Draft so that the circulation work and the inventory work are represented separately. When the inventory work is done in UXPROD-1535 Draft , this work should be assessed as the stories are likely not complete.

Questions

  • Permission controls for the confirmation piece - how could they be implemented?

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