[Koha-bugs] [Bug 9499] --itemscontent= option is undocumented in advanced-notice.pl cronjob + default date should be date_due, not issuedate

bugzilla-daemon at bugs.koha-community.org bugzilla-daemon at bugs.koha-community.org
Thu Feb 7 21:21:47 CET 2013


http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9499

--- Comment #7 from Liz Rea (CatalystIT) <liz at catalyst.net.nz> ---
When I was writing this patch, I went back and looked at when this was added -
it has been this way since the beginning. 

No one has been much bothered to change it, apparently, or if they have, they
used the heretofore undocumented --itemscontent flag.

My suspicion is that libraries don't look at the actual output of these notices
very often - they get sent out and they never see what information is contained
in items.content. That, or they see it but don't grok that it's issuedate
instead of date-due. It's clear that if there were complaints, they were
previously unvoiced, at least to bugzilla. However, the impetus for this patch
came from a library who noticed the discrepancy - I can only assume others have
noticed too.

That said, date_due makes a whole lot more sense for the purpose of the notice
- we were sending out a notice telling patrons that an item was due, but that
didn't tell patrons when the item was due, only when they checked it out. That
doesn't seem helpful.

As noted, the behaviour can be reverted to "the old way" by using the
--itemscontent flag on the cronjob and passing the issuedate instead of the
due_date.

Also, if you had previously specified date_due using the items.content flag on
the cron job, that behaviour won't change with this patch.

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


More information about the Koha-bugs mailing list