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.