Item states (status) (UXPROD-1321)

[UXPROD-3572] Configure item state changes upon check in Created: 21/Feb/22  Updated: 30/Nov/23

Status: Draft
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: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Epic Link: Item states (status)
Development Team: None
PO Rank: 0
Rank: Cornell (Full Sum 2021): R2

 Description   

Current situation or problem:

Currently, when an item is successfully checked back in, its item status changes to one of a few different values:

  • Available - item was checked in at its home service point, no open requests on item
  • In Transit - item has no open requests but was not checked in at its home service point and needs to go back there, or item has an open request at another service point and needs to go there to be put on the hold shelf
  • Awaiting Pickup - item was requested by a patron, checked in at the pickup location where the patron wanted to pick up the item

There is pending development for an item status of Recently Returned (https://folio-org.atlassian.net/browse/UXPROD-527) that when implemented will also be a possible status change that would occur.

Some libraries will want to be able to configure check-in behavior such that different item statuses can be set on check in.

  • If an item with a Withdrawn status is checked in, that usually signals a records issue that needs to be resolved. So rather than the item being immediately made Available or In transit, a library want the status to be set to In process (non-requestable) so that the item can be reviewed.
  • If an item with a status of Intellectual item is checked in, that could also signal a records issue, depending on how a library is using that item status. So as with the above, libraries may want the state change to go to In process (non-requestable) rather than Available.

In scope

Out of scope

  • Changes to item status that require knowledge of an item status prior to a check out. E.g., if a Restricted item is checked out to a patron, the item status becomes Checked out, and when the item is checked back in, the Check in app has no way of knowing that "Hey, prior to loan, this thing was restricted." And an item with a Checked out status presumably has a loan attached to it, and changing item statuses upon return could mess up various things related to loan dependencies.

Use case(s)

Proposed solution/stories

  • Some possible approaches:
    • As part of the development of item state customization, you could incorporate this into that feature, with each item status having a configurable option for "When item is checked in, change status to..."
    • An area could be developed in Settings > Circulation that specified the item state transition for specific scenarios, with settinngs like
      • <If a Withdrawn item is checked in, change the status to ...>
      • <If a Restricted item is checked in, change the status to...>

Links to additional info

  • This feature was added to capture feedback on the "Item Status" document being drafted for the Juniper "Platform Essentials" documentation going onto docs.folio.org. No further conversation has been had about how this could or should be developed.

Questions



 Comments   
Comment by Erin Nettifee [ 21/Feb/22 ]

Charlotte Whitt, just an FYI on this one, I added it to the Item States epic based on feedback from Shelley Doljack in the documentation review.

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