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

Add a separate 'Items aged to lost after overdue X <interval>' setting for recalled items

    XMLWordPrintable

    Details

    • Template:
      UXPROD features
    • Epic Link:
    • Front End Estimate:
      Small < 3 days
    • Back End Estimate:
      Large < 10 days
    • Confidence factor:
      Low
    • Development Team:
      Prokopovych
    • Calculated Total Rank:
      45
    • PO Rank:
      99
    • Rank: Chicago (MVP Sum 2020):
      R1
    • Rank: Cornell (Full Sum 2021):
      R2
    • Rank: Duke (Full Sum 2021):
      R1
    • Rank: 5Colleges (Full Jul 2021):
      R3
    • Rank: FLO (MVP Sum 2020):
      R4
    • Rank: GBV (MVP Sum 2020):
      R4
    • Rank: Grand Valley (Full Sum 2021):
      R4
    • Rank: Lehigh (MVP Summer 2020):
      R4
    • Rank: MO State (MVP June 2020):
      R1
    • Rank: TAMU (MVP Jan 2021):
      R3
    • Score:
      5
    • Showstopper for Summer 2021 Implementers?:
      Yes
    • Showstopper Comments from Summer 2021 Implementers:
      Hide
      [Tod from Chicago: this is pretty important for us. When we do recall items we really need them back quickly, and as a practical matter it seems many patrons need the lost book bill as motivation to actually return the item. We don't know if we could manually handle this as a workaround.] [Response from Holly: David B. from Chicago has described this a showstopper in the RA SIG meetings.]
      Show
      [Tod from Chicago: this is pretty important for us. When we do recall items we really need them back quickly, and as a practical matter it seems many patrons need the lost book bill as motivation to actually return the item. We don't know if we could manually handle this as a workaround.] [Response from Holly: David B. from Chicago has described this a showstopper in the RA SIG meetings.]
    • Showstopper December 11 Meeting Summary:
      There isn't a workaround or thin-thread for this. Cate mentioned that the Core: Functional team could probably get this done if Iris was extended one week. Only Chicago needs this for go-live, and would like is 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, it should be completed as part of the Iris release.

      Description

      Overview

      • Currently we have one 'Items aged to lost after overdue X <interval>' setting in the Lost Item Fee Policy that is shared by recalled items and regular items.
      • Brooks Travis brought this to Holly's attention via Slack on June 3, 2020 as a possible future requirement -

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                hollyolepm Holly Mistlebauer
                Reporter:
                hollyolepm Holly Mistlebauer
                Front End Estimator:
                Holly Mistlebauer Holly Mistlebauer
                Back End Estimator:
                Holly Mistlebauer Holly Mistlebauer
                Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases