Items marked long overdue one day after due date
Running Koha 3, we're having all items marked long overdue one day after the due date and patrons are charged the items replacement price. Our LOST status is 1=lost and 2=long overdue. The crontab entry is from crontab.example 10 21 * * 1 $USER $KOHA_CRON_PATH/longoverdue.pl --lost 20=2 --lost 100=1 --charge 1 --confirm What else should I be checking to get long overdues to wait till books ar long ovedue? -- Tim McMahon Technical Services West Liberty Public Library
Hi Tim -- You are at the right place for what you want... That script needs to be placed in your crontab and you need to replace the first part of it with your path to koha_cronjobs. So that script will have items age to longoverdue after 20 days and then become lost after 100 days and charge the patron replacement fees. -Brendan --------------------------------------------------------------------------------------------------------------------------------- Brendan A. Gallagher ByWater Solutions CEO, Director of Innovation Support and Consulting for Open Source Software Installation, Data Migration, Training, Customization, Hosting, Complete Support Packages Phone # (203)823-5847 http://bywatersolutions.com info@bywatersolutions.com --------------------------------------------------------------------------------------------------------------------------------- On Feb 18, 2009, at 8:32 AM, Tim McMahon wrote:
Running Koha 3, we're having all items marked long overdue one day after the due date and patrons are charged the items replacement price. Our LOST status is 1=lost and 2=long overdue. The crontab entry is from crontab.example
10 21 * * 1 $USER $KOHA_CRON_PATH/longoverdue.pl --lost 20=2 --lost 100=1 --charge 1 --confirm
What else should I be checking to get long overdues to wait till books ar long ovedue?
-- Tim McMahon Technical Services West Liberty Public Library _______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
--------------------------------------------------------------------------------------------------------------------------------- Brendan A. Gallagher ByWater Solutions CEO, Director of Innovation Support and Consulting for Open Source Software Installation, Data Migration, Training, Customization, Hosting, Complete Support Packages Phone # (203)823-5847 http://bywatersolutions.com info@bywatersolutions.com ---------------------------------------------------------------------------------------------------------------------------------
Thanks for the speedy reply. I already have that line in the crontab. Are you saying I can't use the $KOHA_CRON_PATH and need to replace that with the actual path? I have $KOHA_CRON_PATH defined at the beginning of the crontab. Brendan Gallagher wrote:
Hi Tim --
You are at the right place for what you want...
That script needs to be placed in your crontab and you need to replace the first part of it with your path to koha_cronjobs.
So that script will have items age to longoverdue after 20 days and then become lost after 100 days and charge the patron replacement fees.
-Brendan
---------------------------------------------------------------------------------------------------------------------------------
Brendan A. Gallagher ByWater Solutions CEO, Director of Innovation Support and Consulting for Open Source Software Installation, Data Migration, Training, Customization, Hosting, Complete Support Packages Phone # (203)823-5847 http://bywatersolutions.com info@bywatersolutions.com ---------------------------------------------------------------------------------------------------------------------------------
On Feb 18, 2009, at 8:32 AM, Tim McMahon wrote:
Running Koha 3, we're having all items marked long overdue one day after the due date and patrons are charged the items replacement price. Our LOST status is 1=lost and 2=long overdue. The crontab entry is from crontab.example
10 21 * * 1 $USER $KOHA_CRON_PATH/longoverdue.pl --lost 20=2 --lost 100=1 --charge 1 --confirm
What else should I be checking to get long overdues to wait till books ar long ovedue?
-- Tim McMahon Technical Services West Liberty Public Library _______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
---------------------------------------------------------------------------------------------------------------------------------
Brendan A. Gallagher ByWater Solutions CEO, Director of Innovation Support and Consulting for Open Source Software Installation, Data Migration, Training, Customization, Hosting, Complete Support Packages Phone # (203)823-5847 http://bywatersolutions.com info@bywatersolutions.com ---------------------------------------------------------------------------------------------------------------------------------
-- Tim McMahon Technical Services West Liberty Public Library 400 N. Spencer St. West Liberty, IA 52776 Phone: 319-627-2084 Fax: 319-627-2135 tmcmahon@wlpl.org http://www.wlpl.org
yup -- The KOHA_CRON_PATH is a place holder -- so you know where to put in the actual path to the cronjob script for example on one of my servers it looks like this 20 0 * * * perl /home/koha/kohaclone/misc/cronjobs/longoverdue.pl -- lost 5=2 --lost 10=1 --charge 1 --confirm Cheers, Brendan --------------------------------------------------------------------------------------------------------------------------------- Brendan A. Gallagher ByWater Solutions CEO, Director of Innovation Support and Consulting for Open Source Software Installation, Data Migration, Training, Customization, Hosting, Complete Support Packages Phone # (203)823-5847 http://bywatersolutions.com info@bywatersolutions.com --------------------------------------------------------------------------------------------------------------------------------- On Feb 18, 2009, at 9:29 AM, Tim McMahon wrote:
Thanks for the speedy reply. I already have that line in the crontab. Are you saying I can't use the $KOHA_CRON_PATH and need to replace that with the actual path? I have $KOHA_CRON_PATH defined at the beginning of the crontab.
Brendan Gallagher wrote:
Hi Tim -- You are at the right place for what you want... That script needs to be placed in your crontab and you need to replace the first part of it with your path to koha_cronjobs. So that script will have items age to longoverdue after 20 days and then become lost after 100 days and charge the patron replacement fees. -Brendan --------------------------------------------------------------------------------------------------------------------------------- Brendan A. Gallagher ByWater Solutions CEO, Director of Innovation Support and Consulting for Open Source Software Installation, Data Migration, Training, Customization, Hosting, Complete Support Packages Phone # (203)823-5847 http://bywatersolutions.com info@bywatersolutions.com --------------------------------------------------------------------------------------------------------------------------------- On Feb 18, 2009, at 8:32 AM, Tim McMahon wrote:
Running Koha 3, we're having all items marked long overdue one day after the due date and patrons are charged the items replacement price. Our LOST status is 1=lost and 2=long overdue. The crontab entry is from crontab.example
10 21 * * 1 $USER $KOHA_CRON_PATH/longoverdue.pl --lost 20=2 --lost 100=1 --charge 1 --confirm
What else should I be checking to get long overdues to wait till books ar long ovedue?
-- Tim McMahon Technical Services West Liberty Public Library _______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha --------------------------------------------------------------------------------------------------------------------------------- Brendan A. Gallagher ByWater Solutions CEO, Director of Innovation Support and Consulting for Open Source Software Installation, Data Migration, Training, Customization, Hosting, Complete Support Packages Phone # (203)823-5847 http://bywatersolutions.com info@bywatersolutions.com
-- Tim McMahon Technical Services West Liberty Public Library 400 N. Spencer St. West Liberty, IA 52776 Phone: 319-627-2084 Fax: 319-627-2135 tmcmahon@wlpl.org http://www.wlpl.org
Tim -- In my opinion, the longoverdue.pl cronjobs fails to support multiple --lost arguments reliably, despite its example's claim to the contrary. You can try executing the job with -v (verbose) and see if you don't have an unexpected range for your second case reported, like: starting range: X - Y with lost value 1 I recommend only using one --lost argument for now. --Joe On Wed, Feb 18, 2009 at 11:32 AM, Tim McMahon <tmcmahon@wlpl.org> wrote:
Running Koha 3, we're having all items marked long overdue one day after the due date and patrons are charged the items replacement price. Our LOST status is 1=lost and 2=long overdue. The crontab entry is from crontab.example
10 21 * * 1 $USER $KOHA_CRON_PATH/longoverdue.pl --lost 20=2 --lost 100=1 --charge 1 --confirm
What else should I be checking to get long overdues to wait till books ar long ovedue?
-- Tim McMahon Technical Services West Liberty Public Library _______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
This is what I changed my crontab entry to and I'm still getting items marked as long overdue and the patron is charged the cost of the item when they are only one day past due. 10 21 * * * /usr/share/koha/bin/cronjobs/longoverdue.pl --lost 100=1 --charge 1 --confirm Joe Atzberger wrote:
Tim --
In my opinion, the longoverdue.pl cronjobs fails to support multiple --lost arguments reliably, despite its example's claim to the contrary.
You can try executing the job with -v (verbose) and see if you don't have an unexpected range for your second case reported, like: starting range: X - Y with lost value 1
I recommend only using one --lost argument for now.
--Joe
On Wed, Feb 18, 2009 at 11:32 AM, Tim McMahon <tmcmahon@wlpl.org <mailto:tmcmahon@wlpl.org>> wrote:
Running Koha 3, we're having all items marked long overdue one day after the due date and patrons are charged the items replacement price. Our LOST status is 1=lost and 2=long overdue. The crontab entry is from crontab.example
10 21 * * 1 $USER $KOHA_CRON_PATH/longoverdue.pl --lost 20=2 --lost 100=1 --charge 1 --confirm
What else should I be checking to get long overdues to wait till books ar long ovedue?
-- Tim McMahon Technical Services West Liberty Public Library _______________________________________________ Koha mailing list Koha@lists.katipo.co.nz <mailto:Koha@lists.katipo.co.nz> http://lists.katipo.co.nz/mailman/listinfo/koha
------------------------------------------------------------------------
_______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
-- Tim McMahon Technical Services West Liberty Public Library 400 N. Spencer St. West Liberty, IA 52776 Phone: 319-627-2084 Fax: 319-627-2135 tmcmahon@wlpl.org http://www.wlpl.org
Hey Tim -- As Joe suggest below - have you tried running the command with the minus v ( -v ) flag set. This would need to be run from the command line and not through crontab (and you can run at anytime). It should print most everything that the perl script is doing on your command window. Give that a try and see if it helps you determine what's going on. -Brendan --------------------------------------------------------------------------------------------------------------------------------- Brendan A. Gallagher ByWater Solutions CEO, Director of Innovation Support and Consulting for Open Source Software Installation, Data Migration, Training, Customization, Hosting, Complete Support Packages Phone # (203)823-5847 http://bywatersolutions.com info@bywatersolutions.com --------------------------------------------------------------------------------------------------------------------------------- On Feb 19, 2009, at 12:40 PM, Tim McMahon wrote:
This is what I changed my crontab entry to and I'm still getting items marked as long overdue and the patron is charged the cost of the item when they are only one day past due.
10 21 * * * /usr/share/koha/bin/cronjobs/longoverdue.pl --lost 100=1 --charge 1 --confirm
Joe Atzberger wrote:
Tim --
In my opinion, the longoverdue.pl cronjobs fails to support multiple --lost arguments reliably, despite its example's claim to the contrary.
You can try executing the job with -v (verbose) and see if you don't have an unexpected range for your second case reported, like: starting range: X - Y with lost value 1
I recommend only using one --lost argument for now.
--Joe
On Wed, Feb 18, 2009 at 11:32 AM, Tim McMahon <tmcmahon@wlpl.org <mailto:tmcmahon@wlpl.org>> wrote:
Running Koha 3, we're having all items marked long overdue one day after the due date and patrons are charged the items replacement price. Our LOST status is 1=lost and 2=long overdue. The crontab entry is from crontab.example
10 21 * * 1 $USER $KOHA_CRON_PATH/longoverdue.pl --lost 20=2 -- lost 100=1 --charge 1 --confirm
What else should I be checking to get long overdues to wait till books ar long ovedue?
-- Tim McMahon Technical Services West Liberty Public Library _______________________________________________ Koha mailing list Koha@lists.katipo.co.nz <mailto:Koha@lists.katipo.co.nz> http://lists.katipo.co.nz/mailman/listinfo/koha
------------------------------------------------------------------------
_______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
-- Tim McMahon Technical Services West Liberty Public Library 400 N. Spencer St. West Liberty, IA 52776 Phone: 319-627-2084 Fax: 319-627-2135 tmcmahon@wlpl.org http://www.wlpl.org _______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Output from /usr/share/koha/bin/cronjobs/longoverdue.pl -v --lost 100=1 --charge 1 --confirm starting range: 100 - 366 with lost value 1 at /usr/share/koha/bin/cronjobs/longoverdue.pl line 104. updating 18281 for borrower 3656 to lost: 1 at /usr/share/koha/bin/cronjobs/longoverdue.pl line 108. 3656 / 18281 at /usr/share/koha/lib/C4/Accounts.pm line 314. Undefined subroutine &C4::Accounts::ModItem called at /usr/share/koha/lib/C4/Accounts.pm line 317. Brendan Gallagher wrote:
Hey Tim --
As Joe suggest below - have you tried running the command with the minus v ( -v ) flag set. This would need to be run from the command line and not through crontab (and you can run at anytime). It should print most everything that the perl script is doing on your command window.
Give that a try and see if it helps you determine what's going on.
-Brendan
--------------------------------------------------------------------------------------------------------------------------------- Brendan A. Gallagher ByWater Solutions CEO, Director of Innovation Support and Consulting for Open Source Software Installation, Data Migration, Training, Customization, Hosting, Complete Support Packages Phone # (203)823-5847 http://bywatersolutions.com info@bywatersolutions.com ---------------------------------------------------------------------------------------------------------------------------------
On Feb 19, 2009, at 12:40 PM, Tim McMahon wrote:
This is what I changed my crontab entry to and I'm still getting items marked as long overdue and the patron is charged the cost of the item when they are only one day past due.
10 21 * * * /usr/share/koha/bin/cronjobs/longoverdue.pl --lost 100=1 --charge 1 --confirm
Joe Atzberger wrote:
Tim --
In my opinion, the longoverdue.pl cronjobs fails to support multiple --lost arguments reliably, despite its example's claim to the contrary.
You can try executing the job with -v (verbose) and see if you don't have an unexpected range for your second case reported, like: starting range: X - Y with lost value 1
I recommend only using one --lost argument for now.
--Joe
On Wed, Feb 18, 2009 at 11:32 AM, Tim McMahon <tmcmahon@wlpl.org <mailto:tmcmahon@wlpl.org>> wrote:
Running Koha 3, we're having all items marked long overdue one day after the due date and patrons are charged the items replacement price. Our LOST status is 1=lost and 2=long overdue. The crontab entry is from crontab.example
10 21 * * 1 $USER $KOHA_CRON_PATH/longoverdue.pl --lost 20=2 -- lost 100=1 --charge 1 --confirm
What else should I be checking to get long overdues to wait till books ar long ovedue?
-- Tim McMahon Technical Services West Liberty Public Library _______________________________________________ Koha mailing list Koha@lists.katipo.co.nz <mailto:Koha@lists.katipo.co.nz> http://lists.katipo.co.nz/mailman/listinfo/koha
------------------------------------------------------------------------
_______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha -- Tim McMahon Technical Services West Liberty Public Library 400 N. Spencer St. West Liberty, IA 52776 Phone: 319-627-2084 Fax: 319-627-2135 tmcmahon@wlpl.org http://www.wlpl.org
Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
-- Tim McMahon Technical Services West Liberty Public Library 400 N. Spencer St. West Liberty, IA 52776 Phone: 319-627-2084 Fax: 319-627-2135 tmcmahon@wlpl.org http://www.wlpl.org
participants (3)
-
Brendan Gallagher -
Joe Atzberger -
Tim McMahon