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

Hebis (Poppy): Implement Reminder Fees for German Libraries. Minimal requirements

    XMLWordPrintable

Details

    • Poppy (R2 2023)
    • Jumbo: > 45 days
    • Jumbo: > 45 days
    • Odin
    • 80
    • 0
    • R5
    • R5
    • R5
    • R5
    • R1
    • R2
    • R2
    • R5
    • R1
    • R2
    • R5
    • R5

    Description

      UPDATE:
      Reduced scope for the German reminder fees (2/13/2023): hebis_Reminder fees - minimal Requirements_20230213.docx
      See RA SIG presentation at https://docs.google.com/presentation/d/1xH9O5ytkd21eApuJTSiVmCrLotXekMQL3Nzk5BjpmvA/edit?usp=sharing for details (was updated after December 16, 2021, February 3, 2022 and April 25, 2022 meetings).

      OVERVIEW: This is related to overdue fines, but is not the same thing. Overdue fines are calculated when an overdue item is returned to the library. The patron is billed at that point. The amount owed is often a huge shock to the patron. Reminder fees are billed to the patron immediately when the item becomes overdue. The patron is notified of what they already owe even if they return the item right now. If they wait longer to return the item, they are notified that they now owe more in reminder fees. Some libraries charge both reminder fees and overdue fines.

      DETAILS: The German libraries charge reminder fees after an item becomes overdue with a scheduled process that creates a reminder notice. The process usually runs at night on a regular schedule (e.g. at 12:00:01). A notice is sent to the patron indicating that they now owe a certain amount (1 Euro, 3 Euros). Often there is a 7-day or 13-day grace period before the next reminder fee is charged, giving the patron time to return the item. The second reminder fee is usually twice as much as the first reminder fee. Again there will be a grace period. Often the third reminder fee will be the last, but there may be a 4th or 5th. Usually after the 2nd or 3rd reminder the library will use block the patron from borrowing/renewing/requesting until the item is renewed. The final reminder usually must be sent via snail mail. Some of the requirements are regulated by state law and some are preferences that must be added to Settings.

      EXAMPLES: See the spreadsheet at https://docs.google.com/spreadsheets/d/14z4drYUGeRvYxB5BhJ6HU6kKAbHVMQqN6BLjtwIx8T0/edit#gid=1907843891&range=A1 for examples. The tabs named Example 2, 5, 6, 7 and 8 have German examples. Attached file Mockups.png provides a summary of all libraries in one place. Attached file Automated Reminder Fee.pdf includes an actual example of a reminder notice.

      EXCEPTION: It appears that Leipzig does not do "reminder fees" but charges overdue fines immediately. See attached file Leizig_Overdue_Fines_Example.xlsx for the details. We may need to create a separate UXPROD feature for this.

      WHEN NEEDED: German libraries need this feature in order to implement Circulation.

      TestRail: Results

        Attachments

          Issue Links

            blocks

            New Feature - New feature requests UXPROD-3461 Hebis: Patron notices for reminder fees for German Libraries. Minimal requirements

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

            New Feature - New feature requests UXPROD-3896 Future Fees/Fines: Allow sites to indicate if "Reminder fees" should be "suspended" when item is claimed returned and/or "cancelled" when item is later aged to lost or declared lost

            • TBD - To be determined
            • Draft

            New Feature - New feature requests UXPROD-4003 2nd iteration. Implement Reminder Fees for German Libraries

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

            New Feature - New feature requests UXPROD-4181 Hebis. Loans prepare a file to print for e.g. German Reminder Fees

            • P2 - normal priority level, must be included in the current development cycle
            • Analysis Complete
            is cloned by

            New Feature - New feature requests UXPROD-4159 Hebis (Quesniella): Implement Reminder Fees for German Libraries

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

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CIRC-1527 Hebis: Create process to bill "Reminder fees" (minimal requirements)

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

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CIRC-1528 Hebis: Setup job to run for billing of "Reminder fees"

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

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CIRC-1529 Hebis: Add "Reminder fee" as hidden automated Fee/Fine Type in Settings>Users>Fee/fine: Manual charges

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

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CIRC-1599 Hebis: BE: Add new reminder fee fields to Loan Record

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

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CIRC-1768 Hebis: Spike. Investigate reuse of the Count closed days in the new Reminder Fee sectionetup job to run for billing of "Reminder fees"

            • 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. CIRC-1775 Hebis: Test. Create process to bill "Reminder fees" (all possible scenarios written up)

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

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CIRCSTORE-414 Hebis: BE: Store two new reminder fee fields to Loan Record

            • P2 - normal priority level, must be included in the current development cycle
            • In Code Review

            Task - A task that needs to be done. MODFEE-335 Hebis: German Reminder fees. Investigate the current code for overdue fees and more

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

            Task - A task that needs to be done. MODFEE-339 Hebis: German Reminder fees. Investigate the Okapi Timer

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

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODFEE-345 Hebis: BE | Add "Reminder fee" sub-section to Overdue Fine Policy: SCENARIOS FOR NEW OVERDUE FINE POLICY A+B+C

            • P2 - normal priority level, must be included in the current development cycle
            • In Code Review

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UICIRC-931 Hebis: Add "Reminder fee" sub-section to Overdue Fine Policy: SCENARIOS FOR NEW OVERDUE FINE POLICY

            • P2 - normal priority level, must be included in the current development cycle
            • In Code Review

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UICIRC-932 Hebis: Add "Reminder fee" sub-section to Overdue Fine Policy: SCENARIOS FOR EXISTING OVERDUE FINE POLICY WITHOUT EXISTING REMINDER FEES

            • P2 - normal priority level, must be included in the current development cycle
            • In Code Review

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UICIRC-933 Hebis: Add "Reminder fee" sub-section to Overdue Fine Policy: SCENARIOS FOR EXISTING OVERDUE FINE POLICY WITH EXISTING REMINDER FEES

            • P2 - normal priority level, must be included in the current development cycle
            • In Code Review
            is duplicated by

            New Feature - New feature requests UXPROD-2822 Future Patron Blocks: Add automated patron block to block patrons with items overdue x number of days

            • TBD - To be determined
            • Closed

            New Feature - New feature requests UXPROD-2950 Future Fees/Fines: Implement Overdue Fine Policy with staggered intervals

            • TBD - To be determined
            • Closed
            relates to

            New Feature - New feature requests UXPROD-96 Fee/fine Policies for Overdue Items

            • TBD - To be determined
            • Closed

            New Feature - New feature requests UXPROD-109 Charge automated overdue fines

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

            Page Loading...

            Activity

              People

                florianruckelshausen Florian Ruckelshausen
                hollyolepm Holly Mistlebauer
                Holly Mistlebauer Holly Mistlebauer
                Holly Mistlebauer Holly Mistlebauer
                Votes:
                0 Vote for this issue
                Watchers:
                29 Start watching this issue

                Dates

                  Created:
                  Updated:

                  TestRail: Runs

                    TestRail: Cases