[Koha-bugs] [Bug 20962] New: Overhaul to notices

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

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

            Bug ID: 20962
           Summary: Overhaul to notices
 Change sponsored?: Sponsored
           Product: Koha
           Version: unspecified
          Hardware: All
               URL: https://wiki.koha-community.org/wiki/Notices_Overhaul_
                    RFC
                OS: All
            Status: NEW
          Severity: enhancement
          Priority: P5 - low
         Component: Notices
          Assignee: koha-bugs at lists.koha-community.org
          Reporter: hughr at brimbank.vic.gov.au
        QA Contact: testopia at bugs.koha-community.org
          Deadline: 2018-11-01

Currently notices are run using effectively two separate systems. Overdue
notices run using their own cron job, whilst everything else is either queued
by the advance_notices cron or directly added to the message queue.
Additionally, print overdues are treated differently to other overdues. This
means the options available for print overdues considerably lag those available
for other notice types, and there are confusing discrepencies between overdues,
other notices, and print overdues and everything else.

Note that this enhancement is primarily aimed at modernising the way paper
(postal) notices are managed, but as part of that it moves overdues under the
same structure as other notices.

# Step 1 - Move Overdues into member messaging preferences
This should allow patrons (or staff on behalf of patrons) to:

  1. Select one or more notification methods (SMS, email etc)
  2. Choose not to be notified about Overdues at all
  3. Choose to receive a digest for overdues

# Step 2 - Enable 'postal' as a specific option rather than simply a
fallback,for all notice types

# Step 3 - option to process all print notices together

# Step 4 - extend <item> tags to other circulation notices

# Step 5 - Allow for 'digesting' of all notices in queue regardless of type

# Step 6 - Allow circulation notices to be created for any item status change

More detail is provided in the RFC - once we have community feedback the
details may change slightly.

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