Re: [Koha] National holidays and other free days - how are they handled?
----- "Tomasz Holdowanski" <mordazy@poczta.onet.pl> wrote:
Hi all,
How Koha handles free days, especially national holidays in the middle
of a week? Is there a list where I can write down all dates when my library is closed, so the system will not allow to set return date to
any day from the list, but instead set it to the first "open" day after the "closed" one? I guess I could change the return date manually, but
it`s rather bad idea when there are up to 300 patrons and up to 1500
transactions per day... Any suggestions?
Regards, Tomasz. _______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Hi Tomaz, Tumer Garip (and friends ;) wrote the original holidays code for koha-3.0. But I have been doing some recent work back-porting it to dev_week, and rel-2.2. So hopefully i can answer some of your questions... There are basically 4 different ways that Koha handles due-dates that fall on a holiday, these a set by a syspref called 'useDaysMode' The most common (i think) holidays mode is 'DateDue', this mode does exactly what you described above. You can define a national holiday as an 'anually repeating' holiday Heres paste from the sys-pref description. --- useDaysMode - "How to calculate return dates : 'Calendar' means that loan-length is increased by ALL holidays occuring between issuing date and due-date, 'Datedue' means that due-date will be increased until next non- calendar day, 'Days' means that holidays rules are ignored" --- We are still currently testing it on the 'devweek' branch wth the NPL templates, and we'll hopefully get some of the newer changes over to rel-2.2 in the next few weeks FYI: it looks like Antoine has got holidays currently included with the latest 2.2 release, using the 'default' templates. Hope that helps you :) Mason James mason.james@liblime.com Programmer www.liblime.com LibLime +64 21 542 117
----- "Tomasz Holdowanski" <mordazy@poczta.onet.pl> wrote: Hi all, How Koha handles free days, especially national holidays in the middle of a week? Is there a list where I can write down all dates when my library is closed, so the system will not allow to set return date to any day from the list, but instead set it to the first "open" day after the "closed" one? I guess I could change the return date manually, but it`s rather bad idea when there are up to 300 patrons and up to 1500 transactions per day... Any suggestions? Regards, Tomasz. _______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha Hi Tomasz, Tumer Garip (and friends ;) wrote the original holidays code for koha-3.0. But I have been doing some recent work back-porting it to dev_week, and rel-2.2. So hopefully i can answer some of your questions... There are basically 4 different ways that Koha handles due-dates that fall on a holiday, these a set by a syspref called 'useDaysMode' The most common (i think) holidays mode is 'DateDue', this mode does exactly what you described above. You can define a national holiday as an 'anually repeating' holiday Heres paste from the sys-pref description. --- useDaysMode - "How to calculate return dates : 'Calendar' means that loan-length is increased by ALL holidays occuring between issuing date and due-date, 'Datedue' means that due-date will be increased until next non- calendar day, 'Days' means that holidays rules are ignored" --- We are still currently testing it on the 'devweek' branch wth the NPL templates, and we'll hopefully get some of the newer changes over to rel-2.2 in the next few weeks FYI: it looks like Antoine has got holidays currently included with the latest 2.2 release, using the 'default' templates. Hope that helps. Mason James mason.james@liblime.com Programmer www.liblime.com LibLime +64 21 542 117
FYI: it looks like Antoine has got holidays currently included with the latest 2.2 release, using the 'default' templates.
I want to point that this is wrong. Here is some explanation on how CVS branches are atm : - we had a rel_2_2 CVS branch, that resulted in 2.2.x release until 2.2.6. - then libLime did some additions to rel_2_2 branch. As Release Manager, I made some checkings and found that those additions were adding some instability, were uncomplete (some systempreferences were added in the code but not in the updatedatabase that is run when updgrading), and were in NPL templates only. In the mean time, some bugfixes were added to rel_2_2 that were strictly bugfixes. So, I decided (and it's written in the Release Notes) to branch a R_2_2_7 CVS from 2.2.6 with only bugfixes. And release the 2.2.7 based on this "branch". Then some bugfixes were added, and 2.2.8 was based on this temporary branch as well. same for 2.2.9) Last month, antoine, requested by my (it's employer) ported the rel_2_2 NPL improvements to default templates. I also have listed all systempreferences that should be added during upgrade process to rch (from libLime), and, iirc, some have been added, although I think some are still missing. I still have to test most rel_2_2 improvements to check that everything is working well & properly integrated, although time is really missing... To conclude : * 2.2.9 is based on R_2_2_7 branch, and does NOT contain holidays management (and no serials improved) either. * rel_2_2 branch has no public releases atm. * dev_week branch is a specific branch, that only libLime uses (afaik), for only a few customers (2 ?) * rel_3_0 branch is abandonned since 4 months, everything for 3.0 is done on HEAD Joshua is trying to organize an irc meeting to clear everybody position on the different branches, and organise things, as, I agree, they can be considered as "unclear" for someone from outside the core team... -- Paul POULAIN et Henri Damien LAURENT Consultants indépendants en logiciels libres et bibliothéconomie (http://www.koha-fr.org) Tel : 04 91 31 45 19
Paul POULAIN wrote:
To conclude : * 2.2.9 is based on R_2_2_7 branch, and does NOT contain holidays management (and no serials improved) either. * rel_2_2 branch has no public releases atm. * dev_week branch is a specific branch, that only libLime uses (afaik), for only a few customers (2 ?) * rel_3_0 branch is abandonned since 4 months, everything for 3.0 is done on HEAD
Pity, since my library has overdue charges, proper (and automatic) handling of holidays etc. would be very nice touch. I think there`s even no need for modifying GUI, just a MYSQL table with dates of closed days and a couple lines of Perl code. I have access to one quite big (and clumsy) ILS, and although my opinion about it is rather bad, it has a couple things nicely done - also handling holidays. It uses a table of 6 columns: branch ID, date, day of week, status, open hour, closed hour. Date format may be yyyymmdd (one particular day), ####mmdd (yearly event), ########dd (monthly event) or ######## (any day); day of week format is numbers from 0 to 6, and status is C (closed) or O (open). So, typical row in that table looks like this: MAIN ######## 0 C, which means the main library is closed on sundays MAIN 20071224 [empty]C, means the library is closed on the Christmas Eve MAIN ######## 1 O - the library is open on mondays UNLESS there`s a particular date marked as closed BEFORE that row in the table. Suppose most libraries don`t need such sophisticated system, but please, include at least a table with "closed" dates and make Koha just skip them when setting due date or counting overdue charges. Guess most of us here would manage typing a couple of dozens of dates in phpMyAdmin. Regards, Tomasz.
Tomasz Holdowanski a écrit :
Paul POULAIN wrote:
To conclude : * 2.2.9 is based on R_2_2_7 branch, and does NOT contain holidays management (and no serials improved) either. * rel_2_2 branch has no public releases atm. * dev_week branch is a specific branch, that only libLime uses (afaik), for only a few customers (2 ?) * rel_3_0 branch is abandonned since 4 months, everything for 3.0 is done on HEAD
Pity, since my library has overdue charges, proper (and automatic) handling of holidays etc. would be very nice touch.
why is it a pity ? Koha 3.0 is not that far : i've started deploying it in france (1 librariy done, 3 to come soon), i'm working hard on fixing reported bugs. I hope that a public release can occur in september (although with probably some RC (Release Candidate) warnings) the CVS point of view is a developper one. HTH -- Paul POULAIN et Henri Damien LAURENT Consultants indépendants en logiciels libres et bibliothéconomie (http://www.koha-fr.org) Tel : 04 91 31 45 19
Hi Paul and everybody !!!! We might be interested in the holidays handling. We follow the national holidays (christmas, labour day ...) and we also have the specific of the university (mostly jewish holidays), the last ones change every year. Is this covered? Andres
Tomasz Holdowanski a écrit :
Paul POULAIN wrote:
To conclude : * 2.2.9 is based on R_2_2_7 branch, and does NOT contain holidays management (and no serials improved) either. * rel_2_2 branch has no public releases atm. * dev_week branch is a specific branch, that only libLime uses (afaik), for only a few customers (2 ?) * rel_3_0 branch is abandonned since 4 months, everything for 3.0 is done on HEAD
Pity, since my library has overdue charges, proper (and automatic) handling of holidays etc. would be very nice touch.
why is it a pity ? Koha 3.0 is not that far : i've started deploying it in france (1 librariy done, 3 to come soon), i'm working hard on fixing reported bugs. I hope that a public release can occur in september (although with probably some RC (Release Candidate) warnings)
the CVS point of view is a developper one.
HTH
-- Paul POULAIN et Henri Damien LAURENT Consultants indépendants en logiciels libres et bibliothéconomie (http://www.koha-fr.org) Tel : 04 91 31 45 19 _______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
-- A/P Andrés Tarallo
Pity, since my library has overdue charges, proper (and automatic) handling of holidays etc. would be very nice touch.
why is it a pity ? Koha 3.0 is not that far : i've started deploying it in france (1 librariy done, 3 to come soon), i'm working hard on fixing reported bugs. I hope that a public release can occur in september (although with probably some RC (Release Candidate) warnings)
Unfortunately, I can`t wait till september, not to mention the 'mainstream' version of Koha is rather unsuitable for Polish libraries, mostly placed in old buildings, divided into branches with separate locations, collections, desks, and sometimes different borrowing and charging policies. I cooperate with Wojciech Zatorski, who is working on a 'university' version, heavily modified compared to the 'mainstream' one, but thought that something as obvious as holiday handling would be already included in 'standard' Koha. As I said before, there`s no need for a GUI, a table with dates to skip and a couple lines of code would be plenty enough :) Regards, Tomasz.
On 5/06/2007, at 9:00 PM, Tomasz Holdowanski wrote:
Pity, since my library has overdue charges, proper (and automatic) handling of holidays etc. would be very nice touch. why is it a pity ? Koha 3.0 is not that far : i've started deploying it in france (1 librariy done, 3 to come soon), i'm working hard on fixing reported bugs. I hope that a public release can occur in september (although with probably some RC (Release Candidate) warnings)
Unfortunately, I can`t wait till september, not to mention the 'mainstream' version of Koha is rather unsuitable for Polish libraries, mostly placed in old buildings, divided into branches with separate locations, collections, desks, and sometimes different borrowing and charging policies. I cooperate with Wojciech Zatorski, who is working on a 'university' version, heavily modified compared to the 'mainstream' one, but thought that something as obvious as holiday handling would be already included in 'standard' Koha. As I said before, there`s no need for a GUI, a table with dates to skip and a couple lines of code would be plenty enough :)
Hi As paul said its in the rel_2_2 branch of cvs and in the HEAD, you are welcome to check the code out yourself and install it, if waiting for a new version of 2.2 or 3.0 won't do. IE the code has all been written. Chris -- Chris Cormack chris.cormack@liblime.com VP Research and Development www.liblime.com LibLime +64 21 542 131
Unfortunately, I can`t wait till september, not to mention the 'mainstream' version of Koha is rather unsuitable for Polish libraries, mostly placed in old buildings, divided into branches with separate locations, collections, desks, and sometimes different borrowing and charging policies. I cooperate with Wojciech Zatorski, who is working on a 'university' version, heavily modified compared to the 'mainstream' one, It'd be a shame to have a fork. We certainly have an interest in having mainline Koha suitable for Polish University libraries, and university libraries in general. Tumer Garip (Near East University) has done a lot of useful work toward that. LibLime is also working with some largish academics in the US that plan to sponsor some academic-specific functions.
The advantage of an OSS system in the first place is the ability to reuse code, if at all possible, lets try to work together to make the mainline version work for everyone. Maybe we need to separate Koha's settings out into profiles or something? Maybe switching to Git (distributed version control) would help? Any other ideas? Cheers, -- Joshua Ferraro SUPPORT FOR OPEN-SOURCE SOFTWARE President, Technology migration, training, maintenance, support LibLime Featuring Koha Open-Source ILS jmf@liblime.com |Full Demos at http://liblime.com/koha |1(888)KohaILS
participants (6)
-
Chris Cormack -
Joshua M. Ferraro -
Mason James -
Paul POULAIN -
tarallo＠ort.edu.uy -
Tomasz Holdowanski