[Koha-bugs] [Bug 4171] New: overduerules.pl needs an overhaul

[bugzilla-daemon at kohaorg.ec2.liblime.com]

http://bugs.koha.org/cgi-bin/bugzilla3/show_bug.cgi?id=4171

           Summary: overduerules.pl needs an overhaul
           Product: Koha
           Version: rel_3_4
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: enhancement
          Priority: P5
         Component: Notices
        AssignedTo: cnighswonger at foundations.edu
        ReportedBy: cnighswonger at foundations.edu
   Estimated Hours: 0.0
 Change sponsored?: ---


<kf> ah ok, there are some other bad things about notice triggers
<kf> minimal value is 1
<kf> and dont use the default library - no notices will be sent
<chris_n> kf: so the script does not process any notices with a delay of less
than 1?
<kf> got no notice when I tried with 0
<kf> only with 1 for the first notice
<kf> this is the day after due date
<kf> which is ok, because you can also sent itemdue and advances notices
<kf> but a hint would be good
<chris_n> kf: so if I want an advanced notice sent , it will not send until 1
day *after* the item is due?
<kf> overdue notices
<nengard> chris_n - you are missing the point - the advanced notice shouldn't
be on that triggers page at all cause it's handled on the enhanced messaging
preferences on the patron record
<kf> advances notices are sent before due date
<chris_n> nengard: big bug then :)
<chris_n> a blocker imho
<nengard> unless I too am misunderstanding
<kf> I dont understand the problem
<jwagner> I don't think it's a blocker, necessarily, but it definitely needs
more explanatory text.  
<chris_n> kf: so if I set up an advanced notice do I have to set a delay?
* chris_n is confused as to whether the functionality is broken or just the
documentation
<jwagner> chris_n, the delay is set in the patron record -- the Enhanced
Messaging section.  You can do a global db update to set the same delay for
everyone.
<kf> yes, or define the delay in patron type and import your new patrons after
that :)
<jwagner> If you edit the patron categories and set up your desired settings
there for advance notice, holds, etc., then any time you create a new patron it
will pick up the settings automatically.  But there's no easy way short of a
SQL update to modify existing records.
<chris_n> so then what is the Delay field for on the overduerules.pl page?
<kf> advanced notice = before due date and item due = due date are handled in
advanced messaging, overdue notices in notice triggers
<nengard> chris_n - it should only be for overdue notices, but that's the part
that needs fixing 
<nengard> right now you can pick it for anything
<jwagner> It's a documentation/screen display issue.
<kf> for overdue notices, days after due date
<jwagner> Ideally the notice triggers page should only filter/show overdue
notices in the pulldowns.  If that's not possible, at least some screen text
about "this is only for overdue notices"
<chris_n> so it sounds to me like the overduerules.pl page needs an overhaul
<kf> jwagner: right. but its nice you can create as many notice templates as
you want and choose there
<jwagner> Right.  As I said, I'm not logged in right now so I can't look.  Is
there anything in the settings that says "this notice is for overdues" as
opposed to "this notice is for circ stuff"?  I don't remember.
<kf> perhaps a new option for notices - module overdue notices and show only
those on notice triggers page
<kf> i think it shows all from circulation
<chris_n> I'm going to open two bugs then: one for the documentation and one
for a general rework of overduerules.pl
<jwagner> Then yes, kf, making a new notice modules just for overdues & having
the notice triggers only show those would work.
<kf> serials routing list and claim serial issues are already differnet
modules, so its not really koha modules in this list


-- 
Configure bugmail: http://bugs.koha.org/cgi-bin/bugzilla3/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.