Invitation: I would like to invite you to a related discussion with the App Interaction SIG on Friday, June 11th at 11:15 am ET / 4:15 pm UK / 5:15 pm CET.
→ Quick update on that and preparation for the meeting tomorrow
On scenario is where an overdue item gets a recall, and the library has configured recalls to change the due date but to _not_ extend the due date. This triggers the scheduled notices to be regenerated based on the original, already past, due date. The patron gets a recall notice and all courtesy and overdue notices scehduled to be sent up until the date of the recall.
The other scenario is where you migrate overdue loans using the check-out-by-barcode API. When the loan is created, scheduled notices are generated based on the due date, which is already in the past. The notices with the nexRunTime in the past are sent out along with other delayed notices.
Lisa's original writeup of the recall scenario:
2019-11-29: 1204168883 is checked out by PatronA. The original due date of the loan is 2020-02-29. As per the standard notice policy, 3 OD notices are shceduled to be sent out in the weeks following the due date.
Repeatedly during spring/summer 2020: before the due data is reached, the loan is given a new later due date. The old OD notices are replaced with new ones scheduled to be sent out in the weeks after the new due date. (This is done through a scripted process which uses the circulation/loans API.)
Sometime in August 2020: the loan is given a new due date of 2020-09-29. The old OD notices are replaced with new ones scheduled to be sent out in the weeks following 2020-02-29.
2020-09-29: the loan expires. In the following weeks, the 3 scheduled notices are sent out.
Winter 2020-2021: the library adds 5 additional notices to the standard notice policy.
March 2021: the loan has still not been returned, and the patron hasn't heard from the library since the 3rd OD was sent in late 2020.
2021-04-11: the loan is recalled by PatronB. Since the loan is already overdue, this does not affect the due date. The due date is still 2020-09-29. The recall action triggers the scheduled notices to be generated. As per the standard notice policy, 8 OD notices are scheduled to be sent out in the weeks following 2020-09-29. Seeing that the there are now 8 delayed scheduled notices, FOLIO sends all of these notices to PatronA ASAP. (FOLIO does not care if the notice is delayed by an hour or 7 months, but the patron may.)