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

Loan: Aged to Lost using SET COST

    XMLWordPrintable

Details

    • 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.
    • XXL < 30 days
    • Medium
    • Jumbo: > 45 days
    • 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).
    • Prokopovych
    • 100
    • 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.
    • R4
    • R1
    • R1
    • R1
    • R1
    • R1
    • R4
    • R4
    • R1
    • R1
    • R4
    • R5
    • R1
    • R1
    • 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

            blocks

            New Feature - New feature requests UXPROD-2572 Loan: Aged to Lost using ACTUAL COST

            • P2 - normal priority level, must be included in the current development cycle
            • Closed
            defines

            Bug - A problem which impairs or prevents the functions of the product. MODFEE-239 Aged to lost fees and fines not generating

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed
            has to be done after

            Task - A task that needs to be done. FOLIO-1953 SPIKE: propose an approach for scheduling tasks in Okapi

            • P2 - normal priority level, must be included in the current development cycle
            • Closed
            has to be done before

            New Feature - New feature requests UXPROD-2165 Notify user when item(s) are aged to lost (automated f/f)

            • P2 - normal priority level, must be included in the current development cycle
            • Closed
            is blocked by

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CIRC-467 Back end work for UICIRC-341: add lost item fee policy in circulation rules syntax

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Bug - A problem which impairs or prevents the functions of the product. RMB-689 Unable to create b-tree index more than 49 symbols length

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Open

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UICIRC-341 Circ Rules Editor - Add lost item fee policies to policy menu

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            New Feature - New feature requests UXPROD-1857 Fee/fine Policies for Lost Item Fees

            • P1 - highest priority item, drop everything else before this is resolved, reserved for critical bugfixes
            • Closed

            New Feature - New feature requests UXPROD-2130 Lost item fee policies and overdue fine policies in circulation rules editor

            • P2 - normal priority level, must be included in the current development cycle
            • Closed
            is defined by

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CIRC-667 New endpoint for aging loaned item to lost

            • TBD - To be determined
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CIRC-668 Backend - Aged to lost: Check in

            • TBD - To be determined
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CIRC-669 Backend - Aged to lost: Check out (not allowed)

            • TBD - To be determined
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CIRC-670 Backend - Aged to lost: Prevent all request types

            • TBD - To be determined
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CIRC-671 Backend - Aged to lost: Renewal (staff only)

            • TBD - To be determined
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CIRC-672 Backend - Aged to lost: Prevent change due date

            • TBD - To be determined
            • Closed

            Umbrella - CIRC-737 Aged to lost: Automatically age overdue items to lost - SET COST

            • TBD - To be determined
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CIRC-751 Aged to lost: Exclude claim returned items from aged to lost process

            • TBD - To be determined
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CIRC-835 [SPIKE] Technical design for the 'Aged to lost' feature

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CIRC-844 Aged to lost: Renewal (effect on lost item fees) - SET COST

            • TBD - To be determined
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CIRC-845 Aged to lost: Check in (effect on fees/fines) - SET COST

            • TBD - To be determined
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CIRC-851 Age to lost: Mark overdue loans as Aged to lost

            • TBD - To be determined
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CIRC-852 Age to lost: Assign lost fees for aged to lost loans - SET COST

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CIRC-854 Age to lost: Add billing date and time when aging an item to lost - SET COST

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CIRC-862 Backend: Aged to lost action on loan details

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CIRC-877 Backend - Aged to lost: Closing (Lost and paid status) - SET COST

            • TBD - To be determined
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CIRC-878 Backend - Aged to lost: Close loans when no fees charged - SET COST

            • TBD - To be determined
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CIRC-881 Allow renew of Aged to lost item when renewal would not change the due date

            • TBD - To be determined
            • Closed

            Bug - A problem which impairs or prevents the functions of the product. CIRC-889 Extra "Aged to lost" loan action is created when aged to lost loan is billed

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CIRC-937 BE: Override failed renewal when renewal will not change the due date

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CIRCSTORE-198 Backend: Automatically age overdue items to lost

            • TBD - To be determined
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CIRCSTORE-199 Backend: Add "agedToLostDelayedBilling" property to loan schema

            • P1 - highest priority item, drop everything else before this is resolved, reserved for critical bugfixes
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CIRCSTORE-228 Add b-tree index needed for age to lost delayed billing

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CIRCSTORE-230 Add b-tree index for loan.itemStatus

            • TBD - To be determined
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODINV-299 Add 'Aged to lost' status to allowed item statuses list

            • TBD - To be determined
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODINVSTOR-503 Add 'Aged to lost' status to allowed item statuses list

            • TBD - To be determined
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UICHKIN-164 Aged to lost: Check in

            • TBD - To be determined
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UICHKOUT-600 Aged to lost: Checkout (not allowed)

            • TBD - To be determined
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIIN-1006 Aged to lost: Behavior in Inventory

            • TBD - To be determined
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIREQ-429 Aged to lost: Prevent all request types

            • TBD - To be determined
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIU-1464 Aged to lost: Renewal (staff only)

            • TBD - To be determined
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIU-1495 Aged to lost: Prevent change due date

            • TBD - To be determined
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIU-1500 Aged to lost: Closing (Lost and paid status) - SET COST

            • TBD - To be determined
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIU-1791 Aged to lost action on loan details

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIU-1803 Loan details action history: source for closed loan, aged to lost

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIU-1804 Update Lost date in loan details

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Bug - A problem which impairs or prevents the functions of the product. UIU-1820 Filter out blank actions on loan details UI

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIU-1853 Override failed renewal when renewal will not change the due date

            • P2 - normal priority level, must be included in the current development cycle
            • Closed
            relates to

            Bug - A problem which impairs or prevents the functions of the product. CIRC-955 Loan is returned in check in response for Lost and paid item (aka no longer checking in 'Lost and paid' items on first attempt)

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Activity

              People

                hollyolepm Holly Mistlebauer
                cboerema Cate Boerema
                Holly Mistlebauer Holly Mistlebauer
                Holly Mistlebauer Holly Mistlebauer
                Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases