Greetings, I need some help with a problem I've encountered in the circulation rules. About six months ago I set a global due date for May 17, the end of the semester. Since then, we've updated Koha a couple times, and I can no longer find the page where I set the global due date. (From my reading, it appears that this feature has been replaced with circ rules?) The system is still maintaining the May 17 due date. I'm not sure how to reset this. In the meantime, every time I check out a book, I have to confirm the action and manually create due dates. All books checked out now are immediately overdue I've made sure that there are no hard due dates set in the circulation rules, but this hasn't made any difference. Thanks for your time and help! -- View this message in context: http://koha.1045719.n5.nabble.com/how-to-undo-global-due-date-tp5714544.html Sent from the Koha-general mailing list archive at Nabble.com.
On 31 May 2012 02:30, jrhsigler <jrhsigler@gmail.com> wrote:
Greetings,
I need some help with a problem I've encountered in the circulation rules. About six months ago I set a global due date for May 17, the end of the semester. Since then, we've updated Koha a couple times, and I can no longer find the page where I set the global due date. (From my reading, it appears that this feature has been replaced with circ rules?) The system is still maintaining the May 17 due date. I'm not sure how to reset this. In the meantime, every time I check out a book, I have to confirm the action and manually create due dates. All books checked out now are immediately overdue
I've made sure that there are no hard due dates set in the circulation rules, but this hasn't made any difference.
Can you find the systempreference in the localuse tab? Try looking in that tab under systempreferences If not, you can change it in the db. Chris
Thanks, I looked in 'local use' but didn't see any options for changing global due dates. I'm at Koha 3.8 now, but set the global due date when I had 3.4 running. Do you have a sample sql statement that I can use to update the database directly? Thank you! -- View this message in context: http://koha.1045719.n5.nabble.com/how-to-undo-global-due-date-tp5714544p5714... Sent from the Koha-general mailing list archive at Nabble.com.
* jrhsigler (jrhsigler@gmail.com) wrote:
Thanks, I looked in 'local use' but didn't see any options for changing global due dates. I'm at Koha 3.8 now, but set the global due date when I had 3.4 running.
Do you have a sample sql statement that I can use to update the database directly?
Thank you!
Hi, Sorry about the slow reply, timezones are a pain. Ok the variable is called ceilingDueDate So DELETE FROM systempreferences WHERE variable ='ceilingDueDate'; Will kill that line completely. There is also globalDueDate DELETE FROM systempreferences WHERE variable ='globalDueDate'; To get rid of it However if you wanted to file a bug also, because there must be code still referencing the old dead syspref, that we need to purge. So bonus points if you go to bugs.koha-community.org and add a bug something like "Vestiges of code still refer to deprecated syspref globalDueDate" Its in C4/Circulation.pm that the bad code is so you could at that, and then someone can write a patch to clean it up, extra super mega bonus points if you write the patch too :) Chris
-- View this message in context: http://koha.1045719.n5.nabble.com/how-to-undo-global-due-date-tp5714544p5714... Sent from the Koha-general mailing list archive at Nabble.com. _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
-- Chris Cormack Catalyst IT Ltd. +64 4 803 2238 PO Box 11-053, Manners St, Wellington 6142, New Zealand
ceilingDueDate and globalDueDate shouldn't be in your 3.8 system; they were deleted as part of the database update that moved them to the circulation matrix (issuingrules table). You should be able to re-enter your rules in the Circulation and Fines rules area under the Administration. You'll have to do this for all your rules, which could be a pain. What might be easier is: UPDATE issuingrules SET hardduedate = 'XXXX-YY-ZZ' WHERE hardduedate = '2012-05-17'; Where 'XXXX-YY-ZZ' is the new global due date you want to set for all materials. If you want finer grain control (only applying a global due date for certain item types, patrons or branches), you'll need to either use the Circulation and Fines editor in Admin, or add a series of additional WHERE clauses to the query. Hope this helps, -Ian On Thu, May 31, 2012 at 5:14 PM, Chris Cormack <chrisc@catalyst.net.nz>wrote:
* jrhsigler (jrhsigler@gmail.com) wrote:
Thanks, I looked in 'local use' but didn't see any options for changing global due dates. I'm at Koha 3.8 now, but set the global due date when I had 3.4 running.
Do you have a sample sql statement that I can use to update the database directly?
Thank you!
Hi,
Sorry about the slow reply, timezones are a pain.
Ok the variable is called ceilingDueDate
So
DELETE FROM systempreferences WHERE variable ='ceilingDueDate';
Will kill that line completely.
There is also globalDueDate
DELETE FROM systempreferences WHERE variable ='globalDueDate';
To get rid of it
However if you wanted to file a bug also, because there must be code still referencing the old dead syspref, that we need to purge.
So bonus points if you go to bugs.koha-community.org and add a bug something like "Vestiges of code still refer to deprecated syspref globalDueDate"
Its in C4/Circulation.pm that the bad code is so you could at that, and then someone can write a patch to clean it up, extra super mega bonus points if you write the patch too :)
Chris
-- View this message in context:
http://koha.1045719.n5.nabble.com/how-to-undo-global-due-date-tp5714544p5714...
Sent from the Koha-general mailing list archive at Nabble.com. _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
-- Chris Cormack Catalyst IT Ltd. +64 4 803 2238 PO Box 11-053, Manners St, Wellington 6142, New Zealand _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Ian Walls <koha.sekjal@gmail.com> wrote:
ceilingDueDate and globalDueDate shouldn't be in your 3.8 system; they were deleted as part of the database update that moved them to the circulation matrix (issuingrules table).
Yep but if for whatever reason this didn't run or failed the code still refers to at least one of them. That's a legit bug we need to tidy up. Chris
You should be able to re-enter your rules in the Circulation and Fines rules area under the Administration. You'll have to do this for all your rules, which could be a pain. What might be easier is:
UPDATE issuingrules SET hardduedate = 'XXXX-YY-ZZ' WHERE hardduedate = '2012-05-17';
Where 'XXXX-YY-ZZ' is the new global due date you want to set for all materials. If you want finer grain control (only applying a global due date for certain item types, patrons or branches), you'll need to either use the Circulation and Fines editor in Admin, or add a series of additional WHERE clauses to the query.
Hope this helps,
-Ian
On Thu, May 31, 2012 at 5:14 PM, Chris Cormack <chrisc@catalyst.net.nz>wrote:
* jrhsigler (jrhsigler@gmail.com) wrote:
Thanks, I looked in 'local use' but didn't see any options for changing global due dates. I'm at Koha 3.8 now, but set the global due date when I had 3.4 running.
Do you have a sample sql statement that I can use to update the database directly?
Thank you!
Hi,
Sorry about the slow reply, timezones are a pain.
Ok the variable is called ceilingDueDate
So
DELETE FROM systempreferences WHERE variable ='ceilingDueDate';
Will kill that line completely.
There is also globalDueDate
DELETE FROM systempreferences WHERE variable ='globalDueDate';
To get rid of it
However if you wanted to file a bug also, because there must be code still referencing the old dead syspref, that we need to purge.
So bonus points if you go to bugs.koha-community.org and add a bug something like "Vestiges of code still refer to deprecated syspref globalDueDate"
Its in C4/Circulation.pm that the bad code is so you could at that, and then someone can write a patch to clean it up, extra super mega bonus points if you write the patch too :)
Chris
-- View this message in context:
http://koha.1045719.n5.nabble.com/how-to-undo-global-due-date-tp5714544p5714...
Sent from the Koha-general mailing list archive at Nabble.com. _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
-- Chris Cormack Catalyst IT Ltd. +64 4 803 2238 PO Box 11-053, Manners St, Wellington 6142, New Zealand _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Thanks for the help, I checked the database and there was a ceilingDueDate and a GlobalDueDate set in the systempreferences table. I deleted those rows from the database and verified that they're gone. We only have one circulation rule defined so I also deleted it and recreated it. The circulation rule does not have a hard due date defined and simply specifies a 21 day loan period. Unfortunately, we're still experiencing the same problem. When books are checked out, they're still assigned a due date of 5/17/2012. Any other suggestions? I verified that the server's system date is correct. Eric On Fri, Jun 1, 2012 at 12:35 PM, Chris Cormack <chrisc@catalyst.net.nz> wrote:
Ian Walls <koha.sekjal@gmail.com> wrote:
ceilingDueDate and globalDueDate shouldn't be in your 3.8 system; they were deleted as part of the database update that moved them to the circulation matrix (issuingrules table).
Yep but if for whatever reason this didn't run or failed the code still refers to at least one of them. That's a legit bug we need to tidy up.
Chris
You should be able to re-enter your rules in the Circulation and Fines rules area under the Administration. You'll have to do this for all your rules, which could be a pain. What might be easier is:
UPDATE issuingrules SET hardduedate = 'XXXX-YY-ZZ' WHERE hardduedate = '2012-05-17';
Where 'XXXX-YY-ZZ' is the new global due date you want to set for all materials. If you want finer grain control (only applying a global due date for certain item types, patrons or branches), you'll need to either use the Circulation and Fines editor in Admin, or add a series of additional WHERE clauses to the query.
Hope this helps,
-Ian
On Thu, May 31, 2012 at 5:14 PM, Chris Cormack <chrisc@catalyst.net.nz>wrote:
* jrhsigler (jrhsigler@gmail.com) wrote:
Thanks, I looked in 'local use' but didn't see any options for changing global due dates. I'm at Koha 3.8 now, but set the global due date when I had 3.4 running.
Do you have a sample sql statement that I can use to update the database directly?
Thank you!
Hi,
Sorry about the slow reply, timezones are a pain.
Ok the variable is called ceilingDueDate
So
DELETE FROM systempreferences WHERE variable ='ceilingDueDate';
Will kill that line completely.
There is also globalDueDate
DELETE FROM systempreferences WHERE variable ='globalDueDate';
To get rid of it
However if you wanted to file a bug also, because there must be code still referencing the old dead syspref, that we need to purge.
So bonus points if you go to bugs.koha-community.org and add a bug something like "Vestiges of code still refer to deprecated syspref globalDueDate"
Its in C4/Circulation.pm that the bad code is so you could at that, and then someone can write a patch to clean it up, extra super mega bonus points if you write the patch too :)
Chris
-- View this message in context:
http://koha.1045719.n5.nabble.com/how-to-undo-global-due-date-tp5714544p5714...
Sent from the Koha-general mailing list archive at Nabble.com. _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
-- Chris Cormack Catalyst IT Ltd. +64 4 803 2238 PO Box 11-053, Manners St, Wellington 6142, New Zealand _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
* Eric Sigler (eric.sigler@gmail.com) wrote:
Thanks for the help,
I checked the database and there was a ceilingDueDate and a GlobalDueDate set in the systempreferences table. I deleted those rows from the database and verified that they're gone.
We only have one circulation rule defined so I also deleted it and recreated it. The circulation rule does not have a hard due date defined and simply specifies a 21 day loan period.
Unfortunately, we're still experiencing the same problem. When books are checked out, they're still assigned a due date of 5/17/2012.
Any other suggestions? I verified that the server's system date is correct.
You could try UPDATE issuingrules SET hardduedate = NULL WHERE hardduedate = '2012-05-17'; Actually just check issuingrules to make sure you do indeed only have that one rule. If not, that would be your problem. Chris -- Chris Cormack Catalyst IT Ltd. +64 4 803 2238 PO Box 11-053, Manners St, Wellington 6142, New Zealand
There was a hard due date set in the issuingrules table and clearing out the hardduedate fixed the problem. Thanks for the help! Sorry for the delay in responding. We're using koha at a school library and somehow the urgency drops once summer vacation starts. ;-) Should I still open a defect for the original issue? Eric On Fri, Jun 1, 2012 at 5:13 PM, Chris Cormack <chrisc@catalyst.net.nz> wrote:
* Eric Sigler (eric.sigler@gmail.com) wrote:
Thanks for the help,
I checked the database and there was a ceilingDueDate and a GlobalDueDate set in the systempreferences table. I deleted those rows from the database and verified that they're gone.
We only have one circulation rule defined so I also deleted it and recreated it. The circulation rule does not have a hard due date defined and simply specifies a 21 day loan period.
Unfortunately, we're still experiencing the same problem. When books are checked out, they're still assigned a due date of 5/17/2012.
Any other suggestions? I verified that the server's system date is correct.
You could try
UPDATE issuingrules SET hardduedate = NULL WHERE hardduedate = '2012-05-17';
Actually just check issuingrules to make sure you do indeed only have that one rule. If not, that would be your problem.
Chris
-- Chris Cormack Catalyst IT Ltd. +64 4 803 2238 PO Box 11-053, Manners St, Wellington 6142, New Zealand
participants (5)
-
Chris Cormack -
Chris Cormack -
Eric Sigler -
Ian Walls -
jrhsigler