[Koha-bugs] [Bug 29997] Allow to send email notification when a serial issue is late

[bugzilla-daemon at bugs.koha-community.org]

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29997

Julian Maurice <julian.maurice at biblibre.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
 Attachment #130048|0                           |1
        is obsolete|                            |

--- Comment #2 from Julian Maurice <julian.maurice at biblibre.com> ---
Created attachment 143637
  -->
https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=143637&action=edit
Bug 29997: Allow to send email notification when a serial issue is late

This patch adds the ability to define, for each subscription, a letter
that will be sent whenever an issue is automatically marked as late by
the script misc/cronjobs/serialsUpdate.pl.
If no letter is defined for a subscription, then no letter will be sent.

The letter will be sent to the subscription's manager (the staff
member who created or last modified the subscription).

Test plan:
1. Run updatedatabase.pl and update_dbix_class_files.pl
2. Create a letter in Tools › Notices & slips for module "Serials". Fill
   the Email template.
3. Create a new subscription, with a grace period of 1 day, and set the
   new field "Late issue notification" to the letter you just created.
   Set the first issue publication date and subscription start date to
   two days ago
4. Run `misc/cronjobs/serialsUpdate.pl -v -c`.
5. The first serial issue of your subscription should have been
   automatically marked as late. Now verify that the table message_queue
   contains a new message corresponding to this serial issue. The
   message's contents should be what you defined in step 1.
   The message should be addressed to the subscription's manager (you)

Technical note:
   The "subscription" table contained a column named "librarian", which
   contained the userid of the patron who created or last modified the
   subscription, but there was no foreign key constraint referencing the
   borrowers table. So this patch also adds a new column "manager_id"
   which contains the borrowernumber of the patron who created or last
   modified the subscription, and it also adds the foreign key
   constraint.  The atomicupdate script tries to fill the new
   "manager_id" column by searching patrons by their "userid", which
   might fail, so it's normal to have some NULL values in "manager_id"
   at the end. The "librarian" column is removed at the end of the
   script

-- 
You are receiving this mail because:
You are watching all bug changes.