Uploaded image for project: 'mod-circulation'
  1. mod-circulation
  2. CIRC-763

Overdue fine not calculated properly for migrated overdue item



    • Standard Bug Write-Up Format
    • EPAM-Veg Sprint 91, EPAM-Veg Sprint 92
    • 3
    • Vega
    • Q2 2020
    • Low


      Holly just met with Anne Highsmith of Texas A&M to review an issue Anne has uncovered with the calculation of overdue fines on a migrated overdue item. The meeting recording is available at https://drive.google.com/open?id=10OUlIB7VbYWg0DOklo_-QmJhYOH-XjlH
      The recording explains the situation, shows the policies in effect, the calendar, etc. We also wanted to test the calculation of overdue fines on a loan that originated in FOLIO, but we couldn't due to a system error. We will try that again after the system error is fixed.

      Steps to Reproduce:

      1. Migrate an overdue Voyager loan to FOLIO
      2. The loan we are testing with was due on December 10, 2018 at 6:11 PM (very overdue!)
      3. Log into TAMU's FOLIO test environment (Anne will request a special login for the developer who investigates this issue)
      4. Check in the overdue book on May 29, 2020 at 2:36 PM
      5. The check-in page indicates that a fee/fine was charged

      Expected Results:
      35.00 fee/fine charged (overdue fine is 1.00 per day, with a maximum of 35.00)

      Actual Results:
      9.00 fee/fine charged

      Additional Information:

      • TAMU does not count closed time in overdue fines
      • TAMU has installed the most recent hotfix related to not counting closed time (mod-circulation-18.0.9)
      • TAMU's calendar begins on January 1, 2000, and they are open every day
      • When the test was rerun, with a check-in on June 2, 2020, the fee/fine was still 9.00. We would have expected it to be higher.
      • The loans were migrated into FOLIO about a week ago

      TestRail: Results




              roman-barannyk Roman Barannyk
              hollyolepm Holly Mistlebauer
              Holly Mistlebauer Holly Mistlebauer
              0 Vote for this issue
              3 Start watching this issue



                TestRail: Runs

                  TestRail: Cases