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

Loan: Aged to Lost using ACTUAL COST

    XMLWordPrintable

    Details

    • Template:
      UXPROD features
    • Epic Link:
    • Back End Estimate:
      XXL < 30 days
    • Confidence factor:
      Low
    • Estimation Notes and Assumptions:
      Hide
      New back end developers are still getting used to working in the team (and FOLIO) and are all unfamiliar with this area.

      zburke: I don't believe there is any front-end work defined here.
      Show
      New back end developers are still getting used to working in the team (and FOLIO) and are all unfamiliar with this area. zburke: I don't believe there is any front-end work defined here.
    • Development Team:
      Prokopovych
    • Calculated Total Rank:
      22
    • Kiwi Planning Points (DO NOT CHANGE):
      71
    • PO Rank:
      95
    • Rank: Chicago (MVP Sum 2020):
      R5
    • Rank: Cornell (Full Sum 2021):
      R2
    • Rank: Duke (Full Sum 2021):
      R4
    • Rank: 5Colleges (Full Jul 2021):
      R3
    • Rank: GBV (MVP Sum 2020):
      R5
    • Rank: Grand Valley (Full Sum 2021):
      R4
    • Rank: Lehigh (MVP Summer 2020):
      R4
    • Rank: MO State (MVP June 2020):
      R1
    • Rank: U of AL (MVP Oct 2020):
      R4

      Description

      July 9, 2020 Change

      UXPROD-87 (Loan: Aged to Lost) was split into:

      Aging items to lost is a process many larger libraries do in order to encourage patrons to return their overdue items. After an item is overdue a specified period of time (see 'Item aged to lost after <number> <interval>' in attached Lost Item Fee Policy), the library will age it to lost by changing the item Item Status to 'Aged to lost' and billing the patron lost item fee(s) per the Lost Item Fee Policy. When a patron receives a bill for a 'lost' item that is most likely just 6 weeks overdue, they usually return the item immediately.

      Some libraries wait a week or so between notifying the patron of the upcoming charge for the aged to lost item and actually billing the patron, giving the patron time to return the very overdue item before a bill is cut. This is determined in the Lost Item Fee Policy setting 'Patron billed after aged to lost <number> <interval>'.

      The patron may also be charged a lost item processing fee depending on the Lost Item Fee Policy setting 'Charge lost item process fee if item aged to lost by system?'

      There are many user stories defining this features because after an item has a status of 'Aged to lost' the system needs to block checkout, renewal and all requests, take special action at check-in, etc.

      The 'is defined by" user stories with a Status of DRAFT are user stories Holly copied over from 'Declared lost" but has not updated for 'Aged to lost' yet. The other users stories, which are directly related to aging an item to lost, are ready for development.

      Attached zipped folder Lost Item Processing.zip contains mock-ups and in-progress requirements for this feature.

        TestRail: Results

          Attachments

          1. Lost-Item-Policy.JPG
            Lost-Item-Policy.JPG
            53 kB
          2. Lost Item Processing.zip
            318 kB
          3. screenshot-1.png
            screenshot-1.png
            399 kB

            Issue Links

              Activity

                People

                Assignee:
                hollyolepm Holly Mistlebauer
                Reporter:
                hollyolepm Holly Mistlebauer
                Front End Estimator:
                Zak_Burke Zak_Burke
                Back End Estimator:
                Marc Johnson Marc Johnson
                Votes:
                0 Vote for this issue
                Watchers:
                7 Start watching this issue

                  Dates

                  Created:
                  Updated:

                    TestRail: Runs

                      TestRail: Cases