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

Loan: Aged to Lost using SET COST

    XMLWordPrintable

    Details

    • Template:
    • Potential Workaround:
      Hide
      Holly: Libraries use the "aged to lost" process to prompt their patrons to return items that have been overdue for a long time (say 6 weeks). When a patron is notified that the item they have will be flagged as lost and they will need to pay $150, they usually bring the book back right away. Most of the time the library waits a week or so after they notify the patron to actually charge them the $150. Libraries that do this could query the database (or data warehouse?) for a list of items more than 6 weeks overdue and send out some type of notice and then bill the patrons a week later using the manual New Fee/Fine feature, but due to the volume this is not a reasonable workaround.
      Show
      Holly: Libraries use the "aged to lost" process to prompt their patrons to return items that have been overdue for a long time (say 6 weeks). When a patron is notified that the item they have will be flagged as lost and they will need to pay $150, they usually bring the book back right away. Most of the time the library waits a week or so after they notify the patron to actually charge them the $150. Libraries that do this could query the database (or data warehouse?) for a list of items more than 6 weeks overdue and send out some type of notice and then bill the patrons a week later using the manual New Fee/Fine feature, but due to the volume this is not a reasonable workaround.
    • Epic Link:
    • Front End Estimate:
      XXL < 30 days
    • Back End Estimate:
      Jumbo: > 45 days
    • Confidence factor:
      Medium
    • Estimation Notes and Assumptions:
      Hide
      Estimate is high because there is so much work to do to check the item status and block certain actions. Age to lost is also a batch process that has criteria to use in determining what to age to lost (rather than a button to push like with Declared Lost).
      Show
      Estimate is high because there is so much work to do to check the item status and block certain actions. Age to lost is also a batch process that has criteria to use in determining what to age to lost (rather than a button to push like with Declared Lost).
    • Development Team:
      Prokopovych
    • Calculated Total Rank:
      104
    • PO Rank:
      100
    • PO Ranking Note:
      This feature is ranked low because non-US libraries don't care about this. For US libraries like Chicago, Duke, and Lehigh this must be available at go-live.
    • Rank: Chalmers (Impl Aut 2019):
      R4
    • Rank: Chicago (MVP Sum 2020):
      R1
    • Rank: Cornell (Full Sum 2021):
      R1
    • Rank: Duke (Full Sum 2021):
      R1
    • Rank: 5Colleges (Full Jul 2021):
      R1
    • Rank: FLO (MVP Sum 2020):
      R1
    • Rank: GBV (MVP Sum 2020):
      R4
    • Rank: hbz (TBD):
      R4
    • Rank: Hungary (MVP End 2020):
      R1
    • Rank: Lehigh (MVP Summer 2020):
      R1
    • Rank: Leipzig (Full TBD):
      R4
    • Rank: Leipzig (ERM Aut 2019):
      R5
    • Rank: MO State (MVP June 2020):
      R1
    • Rank: TAMU (MVP Jan 2021):
      R1
    • Rank: U of AL (MVP Oct 2020):
      R1

      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:
                cboerema Cate Boerema
                Front End Estimator:
                Holly Mistlebauer Holly Mistlebauer
                Back End Estimator:
                Holly Mistlebauer Holly Mistlebauer
                Votes:
                0 Vote for this issue
                Watchers:
                7 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases