[UXPROD-2699] Item statuses: Unavailable, Unknown Intellectual, In process - non requestable, Long missing, Restricted - FOLIO Issue Tracker

XML

Word

Printable

Details

Type: New Feature
Status: Closed (View Workflow)
Priority: P2
Resolution: Done
Affects Version/s: None
Fix Version/s: R1 2021
Component/s: None
Labels:

Template:

UXPROD features
Potential Workaround:
None, this is the workaround for not having custom item statuses
Epic Link:
Item states
Front End Estimate:
Small < 3 days
Back End Estimate:
XL < 15 days
Estimation Notes and Assumptions:

Hide
The frontend estimate is based on the fact that the front-end doesn't directly manipulate item-status -- it's always handled by the backend as a result of some action (creating a request, checking something out or in, etc.).

BE: We need dedicated APIs for all 4 statuses, but they should be similar to existing Withdrawn and Mark missing

Show
The frontend estimate is based on the fact that the front-end doesn't directly manipulate item-status -- it's always handled by the backend as a result of some action (creating a request, checking something out or in, etc.). BE: We need dedicated APIs for all 4 statuses, but they should be similar to existing Withdrawn and Mark missing
Development Team:
Prokopovych
Calculated Total Rank:
PO Rank:
141
PO Ranking Note:
Created this feature on 9/29 based on conversations with item status and implementers' group. May be under-ranked by SMEs at time of Iris planning, but yes, it is important!
Rank: Chicago (MVP Sum 2020):
R1
Rank: Cornell (Full Sum 2021):
R2
Rank: Duke (Full Sum 2021):
R1
Rank: 5Colleges (Full Jul 2021):
R2
Rank: GBV (MVP Sum 2020):
R2
Rank: Grand Valley (Full Sum 2021):
R2
Rank: Lehigh (MVP Summer 2020):
R1
Rank: MO State (MVP June 2020):
R2
Rank: St. Michael's College (Sum 2021):
R2
Rank: TAMU (MVP Jan 2021):
R3
Score:
6
Showstopper for Summer 2021 Implementers?:
Yes
Showstopper Comments from Summer 2021 Implementers:

Hide
[Tod from Chicago: This is a showstopper for Chicago. The statuses that we need:
* Intellectual/dummy: We have a significant number of cases, like with bound-withs and analytics, where we need an item record to carry some data, but it does not really represent something physical with a barcode. These are item records that do not belong to any of the hard-coded item workflows; it would be wrong for them to have an item state that puts them into any of the workflows. Here's where it gets tricky. Item status is not required by the schema; however, there are UI screens which require an item status for you to be able to view or edit the item record, which has the back-door effect of making this a de facto required field. It order for staff to manually create or update a dummy item, an item status is required, when then puts it into some utterly inappropriate workflow. We've identified no practical workaround for this.
* Restricted: In this era of HathiTrust ETAS (Emergency Temporary Access Service) we have a legal obligation to restrict circulation of HathiTrust items where we electronic access to the digital versions through ETAS. We don't have a practical way to manage this obligation without a suitable item status.]

Show
[Tod from Chicago: This is a showstopper for Chicago. The statuses that we need: * Intellectual/dummy: We have a significant number of cases, like with bound-withs and analytics, where we need an item record to carry some data, but it does not really represent something physical with a barcode. These are item records that do not belong to any of the hard-coded item workflows; it would be wrong for them to have an item state that puts them into any of the workflows. Here's where it gets tricky. Item status is not required by the schema; however, there are UI screens which require an item status for you to be able to view or edit the item record, which has the back-door effect of making this a de facto required field. It order for staff to manually create or update a dummy item, an item status is required, when then puts it into some utterly inappropriate workflow. We've identified no practical workaround for this. * Restricted: In this era of HathiTrust ETAS (Emergency Temporary Access Service) we have a legal obligation to restrict circulation of HathiTrust items where we electronic access to the digital versions through ETAS. We don't have a practical way to manage this obligation without a suitable item status.]
Showstopper December 11 Meeting Summary:

Hide
Chicago has identified a thin-thread for this feature. They only need 2 of the item statuses at go-live: 'Restricted' and 'Intellectual'. These statuses don't need to change in an automated way. This makes things much easier. Charlotte just took over Item Statuses from the departed Emma. Holly (or someone else) and Charlotte need to meet with Chicago reps to discuss the thinnest thread possible. We discussed using locations and loan type in the meeting, but these options have issues. We just need to get together and do some brainstorming. (Chicago wants these items statuses in place at least one month before they go live.)

Show
Chicago has identified a thin-thread for this feature. They only need 2 of the item statuses at go-live: 'Restricted' and 'Intellectual'. These statuses don't need to change in an automated way. This makes things much easier. Charlotte just took over Item Statuses from the departed Emma. Holly (or someone else) and Charlotte need to meet with Chicago reps to discuss the thinnest thread possible. We discussed using locations and loan type in the meeting, but these options have issues. We just need to get together and do some brainstorming. (Chicago wants these items statuses in place at least one month before they go live.)
Showstopper Capacity Planning Team Recommendation:

Hide
The Capacity Planning Team recommended to the FOLIO Product Council that the Iris release date be extended to May 3 (from March 1) so that all of the at-risk 'showstopper' features could be completed and released before the July implementations. (Slide deck presented to PC: https://docs.google.com/presentation/d/12s_fs3vqjm4hAGIfZ_HX1jm--v8QOEFber5uvo0VTGw/edit?usp=sharing)

Show
The Capacity Planning Team recommended to the FOLIO Product Council that the Iris release date be extended to May 3 (from March 1) so that all of the at-risk 'showstopper' features could be completed and released before the July implementations. (Slide deck presented to PC: https://docs.google.com/presentation/d/12s_fs3vqjm4hAGIfZ_HX1jm--v8QOEFber5uvo0VTGw/edit?usp=sharing)
Showstopper FOLIO Product Council Decision:
FOLIO Product Council compromised and allowed the Iris release to be delayed by one month, to April 5. Based on the size of the t-shirt estimate for this feature, the thin thread needed by Chicago should be completed as part of the Iris release.

Description

Add the following item statuses to FOLIO:

Unavailable
Intellectual (name subject to change) - to be used for intellectual items/dummy item records
In process - non requestable - to be used for items that are being worked on by staff but should not be requested by patrons
Long missing - to be used by libraries that differentiate between items that have been missing off the shelf for a short amount of time and items that have been missing off the shelf for a longer amount of time
Restricted

& handle the new item status "Unknown" introduced in Honeysuckle

All statuses will need stories corresponding to the status checklist: https://docs.google.com/document/d/1iWhEAxd3hvlvqmDgXmbJ2a3A_J2ahQHaMN2RKvDLvWI/edit

Whether requests on that status are allowed, and what type
Allowed transitions to other statuses - can they be marked withdrawn, missing
Behavior if item with that status is checked in
Behavior if item with that status is checked out
Permissions for that status
Appearance of status in search & filter
Effect of closing order for item with that status
Effect of receiving item for item with that status

TestRail: Results

Attachments

Issue Links

blocks

MODINV-338 Field mappings: Item - Item status handling logic for new statuses

Closed

UIDATIMP-641 Field mappings: Item - update reference dropdown list for Item status to include new statuses

Closed

is defined by

CIRC-1007 BE: Check in items with new statuses

Closed

CIRC-1008 BE: Prevent check in for items with intellectual item status

Closed

CIRC-1009 BE: Check out items with new statuses

Closed

CIRC-1011 BE: Prevent check out for items with intellectual item status

Closed

CIRC-1027 BE: New item statuses: prevent requests

Closed

CIRC-1054 BE: Check out items with new statuses (Restricted only)

Closed

CIRC-1085 BE: Allow requests for items that have item status as Restricted

Closed

MODINV-356 Extend list of item statuses, allow users to change items to those statuses

Closed

MODINV-364 Extend list of item statuses, allow users to change items to those statuses: Restricted

Closed

MODINV-366 BE: Allow changes between new item statuses

Closed

MODINV-377 Documentation of implemented item states

Closed

MODINVSTOR-615 Extend list of item statuses, allow users to change items to those statuses

Closed

MODINVSTOR-623 Extend list of item statuses, allow users to change items to those statuses: Restricted

Closed

UICHKIN-120 Check in items with new statuses

Closed

UICHKIN-210 Prevent check in for items with intellectual item status

Closed

UICHKIN-221 Check in items with new statuses (Restricted only)

Closed

UICHKOUT-669 Prevent check out for items with intellectual item status

Closed

UICHKOUT-671 FE: Check out items with new statuses

Closed

UIIN-756 Extend list of item statuses, allow users to change items to those statuses

Closed

UIIN-894 Long missing: permission

Closed

UIIN-938 Show new statuses in Inventory search and filter

Closed

UIIN-1305 Allow changes between new item statuses

Closed

UIIN-1306 Do not display New request option in item record actions menu for new statuses

Closed

UIIN-1307 Unavailable: permission

Closed

UIIN-1308 In process (non-requestable): permission

Closed

UIIN-1326 Unknown item status: permission

Closed

UIIN-1333 Extend list of item statuses, allow users to change items to those statuses: Restricted

Closed

UIIN-1335 Restricted item status: permission

Closed

UIIN-1336 Intellectual item status: permission

Closed

UIIN-1374 Extend list of item statuses, allow users to change items to those statuses (Intellectual and Restricted only)

Closed

UIREQ-393 New item statuses: prevent requests

Closed

UIREQ-581 Allow requests for items that have item status as Restricted

Closed

relates to

UXPROD-2641 Blocked Field mapping profile updates for Inventory records

Draft

(29 is defined by , 1 relates to)

Activity

People

Assignee:: Charlotte Whitt

Reporter:: Emma Boettcher

Front End Estimator:: Zak_Burke

Back End Estimator:: Bohdan Suprun

Votes:: 0 Vote for this issue

Watchers:: 7 Start watching this issue

Dates

Created:: 29/Sep/20 7:02 PM

Updated:: 01/Mar/21 12:45 PM

Resolved:: 01/Mar/21 12:45 PM

Item statuses: Unavailable, Unknown Intellectual, In process - non requestable, Long missing, Restricted