Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Aged to lost billed date should be based on when item was aged to lost

Description

In the Lost Item Fee Policy, the aged to lost settings are written such that the patron is supposed to be billed 'X intervals' after the item is aged to lost. If a library bills 1 week after an item is aged to lost, and the item was aged to lost on September 1, it should be billed on September 8 (or as soon as the batch aged to lost billing process runs after that date).

After talking to Bohdan, I learned that...

Currently the aged to lost billed date is being calculated as:

dateLostItemShouldBeBilled = loanDueDate + agedToLostAfterOverduePeriod + patronBilledAfterAgedToLost.

When it should be calculated as:

dateLostItemShouldBeBilled = agedToLostDate + patronBilledAfterAgedToLost

(This was discovered when testing https://folio-org.atlassian.net/browse/CIRC-877#icft=CIRC-877, so see the 'Comments' and attached test plan in https://folio-org.atlassian.net/browse/CIRC-877#icft=CIRC-877 for more details.)

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Attachments

1
  • 06 Oct 2020, 08:02 PM

Checklist

hide

TestRail: Results

Activity

Show:

Holly Mistlebauer October 6, 2020 at 8:03 PM

Holly just tested this at https://core-functional.ci.folio.org/ and it passed. Thanks!

Holly Mistlebauer October 6, 2020 at 8:03 PM

Holly has attached her test plan: CIRC-927_Test-Plan.xlsx

Holly Mistlebauer October 6, 2020 at 5:12 PM

I just tested this at https://core-functional.ci.folio.org/ with an item that was aged to lost at 3:16 PM and was to be billed 1 hour later. This means the earliest it could be billed would be 4:16 PM. It was billed at 4:51 PM, so the test was passed. I am going to do a few more tests this afternoon before I pass this issue.

Marc Johnson September 23, 2020 at 10:55 AM

Thanks

Before it was date and time when item should be aged to lost, but Holly Mistlebauer clarified that it should be actual date and time when it is aged to lost (when the job is executed).

Does that mean that if the job that determines a borrowed item should be aged to lost does not execute for a while and so that decision is delayed, the decision to bill should also be delayed? Is the intent that there is always (at least) a fixed amount of time between when the item is aged to lost and when the patron is billed?

Bohdan Suprun September 23, 2020 at 10:52 AM

,

Before it was date and time when item should be aged to lost, but clarified that it should be actual date and time when it is aged to lost (when the job is executed).

Done

Details

Assignee

Reporter

Tester Assignee

Labels

Priority

Story Points

Sprint

Development Team

Prokopovych

Fix versions

Release

Q3 2020

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created September 21, 2020 at 4:47 PM
Updated October 6, 2020 at 8:03 PM
Resolved October 6, 2020 at 8:03 PM
TestRail: Cases
TestRail: Runs

Flag notifications