-
Notifications
You must be signed in to change notification settings - Fork 25
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
Overdue notifications: inconsistency between reminder numbers #2390
Comments
@pronguen In the notification refactoring PR, I simply use "Rappel" subject (removing the numbering). As OVERDUE messages could be aggregated, we could send 1 reminder for itemA, second reminder for itemB and fourth reminder for itemC in the same message. So it's impossible to determine the subject based on the reminder counter. This is why I choose "Rappel" simple string as subject. An other solution could be to aggregated reminders notification adding the reminder_counter into the aggregation key. |
@zannkukai Happy to know that it is as expected! Indeed, I knew the problem of the overdue grouping. Maybe the aggregation only within the same overdue number is better, if the library has e-mail filters based on the e-mail object. But for now, I am ok with both solutions. So let's follow the easiest way. |
@pronguen |
This refactoring purpose is to generalize the notification system in order to manage every kind of notification. The `Notification` resource structure is heavy linked to circulation operation (we need to link the notification with a loan). This commit implements a specific class implementation for each type of notification, with a subclass that provides relevant information to process and dispatch the notification. Closes rero#2373. Closes rero#2390. Closes rero#2410. Co-Authored-by: Renaud Michotte <[email protected]>
This refactoring purpose is to generalize the notification system in order to manage every kind of notification. The `Notification` resource structure is heavy linked to circulation operation (we need to link the notification with a loan). This commit implements a specific class implementation for each type of notification, with a subclass that provides relevant information to process and dispatch the notification. Closes rero#2373. Closes rero#2390. Closes rero#2410. Co-Authored-by: Renaud Michotte <[email protected]>
This refactoring purpose is to generalize the notification system in order to manage every kind of notification. The `Notification` resource structure is heavy linked to circulation operation (we need to link the notification with a loan). This commit implements a specific class implementation for each type of notification, with a subclass that provides relevant information to process and dispatch the notification. Closes rero#2373. Closes rero#2390. Closes rero#2410. Co-Authored-by: Renaud Michotte <[email protected]>
This refactoring purpose is to generalize the notification system in order to manage every kind of notification. The `Notification` resource structure is heavy linked to circulation operation (we need to link the notification with a loan). This commit implements a specific class implementation for each type of notification, with a subclass that provides relevant information to process and dispatch the notification. Closes rero#2373. Closes rero#2390. Closes rero#2410. Co-Authored-by: Renaud Michotte <[email protected]>
This refactoring purpose is to generalize the notification system in order to manage every kind of notification. The `Notification` resource structure is heavy linked to circulation operation (we need to link the notification with a loan). This commit implements a specific class implementation for each type of notification, with a subclass that provides relevant information to process and dispatch the notification. Closes rero#2373. Closes rero#2390. Closes rero#2410. Co-Authored-by: Renaud Michotte <[email protected]>
This refactoring purpose is to generalize the notification system in order to manage every kind of notification. The `Notification` resource structure is heavy linked to circulation operation (we need to link the notification with a loan). This commit implements a specific class implementation for each type of notification, with a subclass that provides relevant information to process and dispatch the notification. Closes rero#2373. Closes rero#2390. Closes rero#2410. Co-Authored-by: Renaud Michotte <[email protected]>
This refactoring purpose is to generalize the notification system in order to manage every kind of notification. The `Notification` resource structure is heavy linked to circulation operation (we need to link the notification with a loan). This commit implements a specific class implementation for each type of notification, with a subclass that provides relevant information to process and dispatch the notification. Closes #2373. Closes #2390. Closes #2410. Co-Authored-by: Renaud Michotte <[email protected]>
Describe the bug
For a 2nd reminder, the reminder number is not the same in the e-mail object and in the note (e-mail body).
To Reproduce
Not clear. Maybe the problem happens with all 2nd reminders. See example.
Expected behavior
The reminder number is the same in the two places.
Context
v1.4.11
Example
The text was updated successfully, but these errors were encountered: