[FOLIO-2374] Vega - Courtesy and Overdue patron notices not being sent to users - Chalmers environment Created: 25/Nov/19  Updated: 03/Jun/20  Resolved: 01/Dec/19

Status: Closed
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Bug Priority: TBD
Reporter: Marie Widigson Assignee: Kostyantyn Khodarev
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: PNG File screenshot-1.png     PNG File screenshot-2.png     PNG File screenshot-3.png     PNG File screenshot-4.png     PNG File screenshot-5.png    
Issue links:
Cloners
clones CHAL-156 Courtesy and Overdue patron notices n... Closed
is cloned by CIRC-582 Broken schedule notices records block... Closed
Relates
relates to CIRC-620 Delete scheduled notice if referenced... Closed
Sprint: EPAM-Veg Sprint 29
Story Points: 3
Development Team: Vega

 Description   

Steps to reproduce:

  1. Check out an item to a patron. The circulation rule activated by the patron/item combo sets the due date one hour into the future, and says that a courtesy notice should be sent out 1 minute before the loan expires, the first overdue notice 1 minute after, the second 2 minutes after, and the third 3 minutes after.
  2. Wait three hours.
  3. Verify that the loan has expired, and check the patron's email inbox.

Expected result:
The patron has received one courtesy notice and three overdue notices.

Actual result:
The patron has not received any courtesy or overdue notices.

Since receipts and recall notices are being sent out (and received) just fine, we suspect that this issue is specifically affecting notices that are set to be triggered by the due date expiring.

~

We're suspecting that no overdue notices are sent to patrons by e-mail. Last week, several patrons claimed that they have not received any reminder for their overdue items. We, the system librarians, have tested a few loan types/patron groups/e-mail domains, and can confirm that we are not seeing any overdue notices.

We don't know how to see for how long the overdue notices has been failing, maybe since going live? Is there a way we can check this?

Some other types of notices seems to work fine, for example recalls and loan receipts.

We continue the testing on our part and will report our findings, but need this to be urgently investigated from your side as well. Thanks!



 Comments   
Comment by Theodor Tolstoy (One-Group.se) [ 26/Nov/19 ]

Chalmers had some progrees with this today. We will adjust settings and see how it goes tonight.

Comment by Marc Johnson [ 29/Nov/19 ]

Theodor Tolstoy (One-Group.se) Cate Boerema Kostyantyn Khodarev

If this issue is for cleaning up records within the Chalmers environment, should it be in the Chalmers project rather than in the mod-circulation project, especially as there is CIRC-582 Closed for changing the behaviour of the module?

Comment by Marc Johnson [ 02/Dec/19 ]

I'm moving this out of the circulation project as it is making release management more difficult (any done issues in the circulation project should have resulted in changes to mod-circulation).

Generated at Thu Feb 08 23:20:12 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.