After the inclusion of MTT in 3.16, the gather_print_notices is no longer restricted to print holds notices; it now also includes the print overdues as well. I have not tested, but suspect it would now include any notice with transport type of 'print'. There are a couple of options for dealing with this. 1) If this is the new post-MTT *intended* behavior, then the documentation should be updated to reflect the broader coverage of gather_print_notices, and the output file should no longer start with 'holdnotices-', but should be something more generic, e.g. 'notices-'. Optionally, could modify cronjob to split notices into files reflecting their type, e.g. 'holdnotices-', 'overduenotices-', 'preduenotices-', etc. 2) Revert the script back to only dealing with holds notices. There are currently bugs in place to address the issue of print overdues no longer being emailed to the library, as well as a bug to allow gather_print_notices to email the output file. This bug fix should take work on those bugs into consideration. - Larry
It appears that Bug 11603 will be adding the option to specify letter_code in gather_print_notices. If that patch is pushed, then this bug becomes irrelevant. - Larry
Since this looks like this feature rather than a bug, should the generated file be renamed? Right now, our files read "holdnotices-2014-11-07.html". Perhaps they should read "printednotices-2014-11-07.html".
By the way, I am starting to like the ability to have access to printed overdues and holds. Whether we keep them in the same file, or separate them, I like the access. Christopher
Hi Christopher, we are looking for sign-offs for bug 11678 and 11603 that are related to this job - I think they might resolve some of the issues noted here.
(In reply to Katrin Fischer from comment #4) > Hi Christopher, we are looking for sign-offs for bug 11678 and 11603 that > are related to this job - I think they might resolve some of the issues > noted here. I'm not quite at the point where I can test these yet. Almost, but still working some details out on my Virtual box.
1) is done by bug 11678 - marking this duplicate. Please open a new bug if we are still missing needed functionality. *** This bug has been marked as a duplicate of bug 11678 ***