Item states (status) (UXPROD-1321)

[UXPROD-2606] Item status: Check in - Customize behavior in Check in app Created: 30/Jul/20  Updated: 06/Jan/23

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

Type: New Feature Priority: P3
Reporter: Emma Boettcher Assignee: Unassigned
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-3908 Customize built-in item statuses: cus... Open
Defines
is defined by UICHKIN-184 Custom item status: check in settings Open
Duplicate
is duplicated by UXPROD-3859 Item status: Check in - Customize ite... Closed
Gantt End to Start
has to be done after UXPROD-1535 Item status: Create interface to crea... Draft
Issue split
split to UXPROD-3898 Customize built-in item statuses: Dat... Open
Relates
relates to UX-369 Mockup for CRU custom item statuses Open
relates to UXPROD-2636 Item Status: If an item status is mar... Draft
relates to UXPROD-3935 Item Status: If an item status is mar... Draft
Epic Link: Item states (status)
Development Team: None
Kiwi Planning Points (DO NOT CHANGE): 1
PO Rank: 78
Rank: Cornell (Full Sum 2021): R1

 Description   

Current situation or problem:
Many apps can change item status, but tenants cannot control how these apps interact with built-in item statuses.

In scope

  • For a defined category of item status, customize whether or not an item with that status can be checked out in FOLIO.
  • For a defined category of item status, customize whether a warning modal is presented when the item is checked out in FOLIO.
  • 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

  • Changes 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, if there is a conflict where one piece allows a workflow and another doesn't, the workflow is not allowed. This is desired behavior and should not change.

Assumptions

  • We assume that UXPROD-1927 Draft is implemented and that item statuses can have attributes as part of their record;
  • We assume that an item status has an attr

Use case(s)

  • By default, the item status Restricted allows checkout with a warning message. A library wants to use that status for items that should not be loaned at all, so they want to change the check out behavior to disallow loan without an override.
  • By default, the item status Withdrawn allows checkout with a warning. A library wants to disallow loans of withdrawn items because they want to correct their holdings information before the item circulates.
  • 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

  • UX story for UXPROD-1535 Draft has a mockup of how this could look (for both built-in and custom item statuses)

Links to additional info

Questions



 Comments   
Comment by Karen Newbery [ 24/Sep/20 ]

Important-can do it now and need to continue to be able to do it. Permissions around this also have to be broken down to view only, create/edit, and create new only/

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