Uploaded image for project: 'UX Product'
  1. UX Product
  2. UXPROD-2699

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

    XMLWordPrintable

    Details

    • Template:
      UXPROD features
    • Potential Workaround:
      None, this is the workaround for not having custom item statuses
    • Epic Link:
    • 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:
      63
    • 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

              Activity

                People

                Assignee:
                charlotte Charlotte Whitt
                Reporter:
                ecboettcher Emma Boettcher
                Front End Estimator:
                Zak_Burke Zak_Burke
                Back End Estimator:
                Bohdan Suprun Bohdan Suprun
                Votes:
                0 Vote for this issue
                Watchers:
                8 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases