Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Notifications and fees don't respect the circulation policy settings #1741

Closed
pronguen opened this issue Mar 3, 2021 · 2 comments · Fixed by #1838
Closed

Notifications and fees don't respect the circulation policy settings #1741

pronguen opened this issue Mar 3, 2021 · 2 comments · Fixed by #1838
Assignees
Labels
bug Breaks something but is not blocking f: circulation Concerns the circulation interface or backend f: notifications p-High High priority (to be solved in the 2-3 next months)
Milestone

Comments

@pronguen
Copy link
Contributor

pronguen commented Mar 3, 2021

Describe the bug

In the screenshot 1, a fixed date checkout was made. Due date on 03.03.21. Default policy applies for reminders and fees. The default policy defines due_soon 5 days before due date, and 1st overdue 5 days after due date. In this case, the notifications didn't respect the settings.

In the screenshot 2, the item 10000000995 is borrowed under the circulation policy "Short", defining due_soon 5 days before due date, and 1st overdue 5 days after due date. In this case, the notifications didn't respect the settings:

  • due_soon was actually sent 4 day before, instead of 5
  • overdue should have been sent on 02.03.21 but wasn't.

To Reproduce

  1. Create a loan
  2. Check the notification dates

Expected behavior

The settings applied for notifications, fees and renewals, come from the circulation policy corresponding to patron type/item type.

Context

Screenshots

image

image

@pronguen pronguen added triage bug Breaks something but is not blocking f: circulation Concerns the circulation interface or backend f: notifications p-High High priority (to be solved in the 2-3 next months) labels Mar 3, 2021
@iGormilhit iGormilhit removed the triage label Mar 4, 2021
@iGormilhit iGormilhit added this to the v1.3.0 milestone Mar 4, 2021
@zannkukai zannkukai self-assigned this Apr 1, 2021
@zannkukai
Copy link
Contributor

@pronguen Date problem seems a problem with UTC date storage. The process is correct but the date stored doesn't take account of the timezone. I will investigate how to solve that problem.

I detect another problem. If you create a loan the 1st april, for a due_date at the same date. No due_soon notification should be send in my opinion. At this time the system create it (because it think that previous notification creation failed and it retry).
Are you agree with this ?

@pronguen
Copy link
Contributor Author

pronguen commented Apr 6, 2021

If you create a loan the 1st april, for a due_date at the same date. No due_soon notification should be send in my opinion.

This depends on the circulation policy. But I agree on this: if the due soon date is smaller or equal to the checkout date, the due soon notification should not be created.

@pronguen pronguen modified the milestones: v1.2.0, v1.3.0 Apr 14, 2021
zannkukai added a commit to zannkukai/rero-ils that referenced this issue Apr 20, 2021
* Closes rero#1741

Co-Authored-by: Renaud Michotte <renaud.michotte@gmail.com>
zannkukai added a commit to zannkukai/rero-ils that referenced this issue Apr 20, 2021
* Closes rero#1741

Co-Authored-by: Renaud Michotte <renaud.michotte@gmail.com>
zannkukai added a commit to zannkukai/rero-ils that referenced this issue Apr 26, 2021
* Closes rero#1741.

Co-Authored-by: Renaud Michotte <renaud.michotte@gmail.com>
zannkukai added a commit to zannkukai/rero-ils that referenced this issue Apr 26, 2021
* Closes rero#1741.

Co-Authored-by: Renaud Michotte <renaud.michotte@gmail.com>
zannkukai added a commit to zannkukai/rero-ils that referenced this issue Apr 27, 2021
* Closes rero#1741.

Co-Authored-by: Renaud Michotte <renaud.michotte@gmail.com>
zannkukai added a commit to zannkukai/rero-ils that referenced this issue Apr 27, 2021
* Closes rero#1741.

Co-Authored-by: Renaud Michotte <renaud.michotte@gmail.com>
zannkukai added a commit to zannkukai/rero-ils that referenced this issue Apr 30, 2021
* Closes rero#1741.

Co-Authored-by: Renaud Michotte <renaud.michotte@gmail.com>
zannkukai added a commit that referenced this issue May 4, 2021
* Closes #1741.

Co-Authored-by: Renaud Michotte <renaud.michotte@gmail.com>
zannkukai added a commit that referenced this issue May 7, 2021
* Closes #1741.

Co-Authored-by: Renaud Michotte <renaud.michotte@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Breaks something but is not blocking f: circulation Concerns the circulation interface or backend f: notifications p-High High priority (to be solved in the 2-3 next months)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants