Item states (status) (UXPROD-1321)

[UXPROD-965] Item status: Missing items Created: 21/Jun/18  Updated: 19/Oct/22  Resolved: 01/Apr/19

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

Type: New Feature Priority: P3
Reporter: Emma Boettcher Assignee: Emma Boettcher
Resolution: Done Votes: 0
Labels: resourceaccess
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Cloners
clones UXPROD-386 Manually change status for item Closed
Defines
is defined by UIIN-487 Item status and item status update fo... Closed
Relates
relates to UICHKIN-58 Check in Missing items Closed
relates to UICHKOUT-480 Prevent check out of Missing items Closed
relates to UIIN-419 Mark item as missing Closed
relates to UIREQ-204 Prevent requests on Missing items Closed
relates to UX-218 UX: mockups for marking items Missing Closed
Epic Link: Item states (status)
Front End Estimate: Small < 3 days
Front End Estimator: Aditya matukumalli
Front-End Confidence factor: Low
Back End Estimate: Medium < 5 days
Back End Estimator: Marc Johnson
Estimation Notes and Assumptions: Assumes decisions have been made about item status and how to manually set them
Development Team: Prokopovych
Rank: Chalmers (Impl Aut 2019): R1
Rank: Chicago (MVP Sum 2020): R1
Rank: Cornell (Full Sum 2021): R1
Rank: 5Colleges (Full Jul 2021): R1
Rank: GBV (MVP Sum 2020): R1
Rank: Lehigh (MVP Summer 2020): R1
Rank: MO State (MVP June 2020): R1
Rank: TAMU (MVP Jan 2021): R1
Rank: U of AL (MVP Oct 2020): R1

 Description   

Items whose location is unknown (e.g., non-loaned items that are not on the shelf) need to be marked in FOLIO, which may affect whether they can be requested or checked out.

Feature includes:

  • Missing item status
  • Interaction to mark an item as Missing (Inventory)
    • Use Pane header menu
    • Reflect change in Inventory app (item status, item status date)
  • Behavior when a Missing item is encountered in Check In or Check Out apps
    • Confirm Check In
    • Prevent Check Out (alert)
  • Prevent creation of loans or requests on Missing items

Note: FOLIO differentiates between Missing, Declared lost ( UXPROD-501 Closed ), and Aged to lost ( UXPROD-87 Closed ). Missing items have gone missing from the shelf & are not on a patron's account, as opposed to Declared lost and Aged to lost items, which have become lost while loaned and are automatically billed to the patron.



 Comments   
Comment by Cate Boerema (Inactive) [ 28/Sep/18 ]

Emma Boettcher I checked the gap analysis survey and for some reason this feature wasn't included. Very odd.

Comment by Emma Boettcher [ 28/Sep/18 ]

Cate Boerema That is odd. I see that creating a report for missing items was there and I thought I remembered a SME question about why this feature was in the Loans epic, but perhaps they were only referring to the report.

Before Q4, I had realized it was redundant with the manually change status aspect, and that feature ( UXPROD-386 Closed ) was ranked as go-live by all responders.

Comment by Theodor Tolstoy (One-Group.se) [ 25/Oct/18 ]

Is this Ticket referring to what happens when an Item has its status manually changed to missing (I assume that UXPROD-386 Closed is about that)?
It will not be an easy thing to handle all the requests for those missing items and to contact patrons about that. Will there be a workaround for this? Can we remove an item from Circulation? Perhaps by changing its material type?

Comment by Emma Boettcher [ 25/Oct/18 ]

Theodor Tolstoy (One-Group.se) The topic of whether an item's status would prohibit a request actually came up briefly in the Resource Access SIG today, and the thought was to prevent requests on those items, by hard-coding that a missing item cannot be requested (in the same way that it's hard-coded that you can't check out an item that's checked out to someone else).

Also might be relevant: Inventory feature to suppress records from displaying in a discovery layer https://folio-org.atlassian.net/browse/UXPROD-136, but that doesn't address what happens to suppressed records in circulation.

Comment by Theodor Tolstoy (One-Group.se) [ 26/Oct/18 ]

Thank you Emma Boettcher for making it clearer!

Comment by Theodor Tolstoy (One-Group.se) [ 07/Nov/18 ]

Emma Boettcher For a short while, while waiting for the intended functionality to come alive, the hard coded option seems like a good interim solution. Is there a Jira ticket for that?

Comment by Cate Boerema (Inactive) [ 29/Nov/18 ]

Emma Boettcher we seem to be missing the front end estimate for this. I assume there is a bit of frontend work. Can you reach out to a developer to estimate? Thanks

Comment by Cate Boerema (Inactive) [ 28/Mar/19 ]

Hi Emma Boettcher looks like this feature needs to be split and closed. Am I correct to assume that the spillover is not needed for Q2?

Comment by Anya [ 29/Mar/19 ]

Comment from the March Meeting : need the ability to mark things missing and make it not requestable

Comment by Emma Boettcher [ 01/Apr/19 ]

Anya There's a couple related issues for that: UIREQ-209 Closed , which has established a whitelist of statuses for various request types, and UXPROD-1320 Closed , which is a feature to make that whitelist tenant-configurable.

Comment by Emma Boettcher [ 01/Apr/19 ]

Cate Boerema The story on it that wasn't done is more relevant to a general status feature ( UXPROD-283 Closed ), not just Missing, so I moved it there before closing this one.

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