September 2011 - Koha-devel - lists.koha-community.org

Meeting Times
by Elliott Davis 06 Sep '11

06 Sep '11

Hi All, I just wanted to remind everyone about the IRC meeting tomorrow September the 7th at 18:00 UTC. Also please note this is a nominations meeting. For those that are interested we will also be having a meeting September the 8th at 18:00 UTC to discuss revamping the notifications system. Please refer to the wiki for proposed details http://wiki.koha-community.org/wiki/Notifications_RFC Best Regards, Elliott Davis Robert R. Muntz Library University of Texas at Tyler

1 0

Koha db schema pecularities
by Jared Camins-Esakov 06 Sep '11

06 Sep '11

Hello. I was looking at the schema that Koha uses for its database, and noticed a few peculiarities that I wonder if anyone could shed some light on: The serial table uses VARCHAR(100) for serial.biblionumber and serial.subscriptionid. Is there any context in which those are not numeric identifiers? Presumably as a result of that, there are no foreign key constraints on the serial table. I think there probably should be. There's a similar situation with the subscription table: subscription.biblionumber doesn't have a foreign key relation with biblio.biblionumber, nor, indeed, any index at all. Foreign keys are also lacking for subscription.aqbooksellerid and subscription.aqbudgetid. On the subject of foreign keys, should items.itype have a foreign key linking it to itemtypes? My understanding of foreign key relationships is that they're a Good Thing because they provide a means to ensure referential integrity. Am I missing something in these particular cases (and there are probably others, these are just the ones I happened to notice), or would people say this was probably just an oversight? Regards, Jared Camins-Esakov -- Jared Camins-Esakov Bibliographer, C & P Bibliography Services, LLC (phone) +1 (917) 727-3445 (e-mail) jcamins(a)cpbibliography.com (web) http://www.cpbibliography.com/

2 1

koha 4.0 / solR / Zebra : A working group is born ?
by Paul Poulain 03 Sep '11

03 Sep '11

Hi, As you all know, BibLibre has worked hard on integrating solR as search engine into Koha. The resulting work is live in 2 french libraries, and we plan to integrate it into Koha 4.0 Our preference went to do a in-depth work. It mean we changed the API a lot, as well as most of the logic behind the search in Koha. It means we can't keep zebra working as it is today. Fortunately, the proposed structure is modularized, so it's possible to re-implement zebra for those who want to stay with it. It's also possible to reintegrate NoZebra or any other search engine. Zeno Tajoli sent us a mail with some starting work about this re-implementation of zebra. I catched tcohen on IRC today, his boss gave him some time to investigate too. Claire Hernandez (our development manager) is also helping. Unless i'm mistaking, it's a draft of a "search engine working group". If anyone else is interested, drop me (or claire) a mail, we could organize an IRC session. PS: i've submitted a presentation for KohaCon11 about what we did around solR. But it will be librarian-oriented. We will/could/should probably have a topic about that during HackFest as well ;-) -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08

9 10

Idea for patch header (1st line)
by Paul Poulain 02 Sep '11

02 Sep '11

Hello all, I'm following through RSS what is pushed, and I would be interested in having a specific marker for patches that are related to Enhancements. Something like Bug XXXX blabla => it's a bugfix Enh XXXX blabla => it's an enhancement I try to track pushed enhancements, I think doc writters & translators would be highly interested by this difference as well. Your opinion ? -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08

2 2

jquery plugin
by Paul Poulain 02 Sep '11

02 Sep '11

Hello koha-devel, On the bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6086 Alex proposes to add a new jquery filter for tables, picnet.table.filter.min.js (An example of the filter is here: http://www.picnet.com.au/resources/tablefilter/demo.htm ) We already have some jquery plugins for table: * tablesorter = let you sort table columns. Widely used in Koha. * tablesorterPager = automatically paginate long tables. Used in admin section of Koha, and in readingrec * uiTableFilter = add a generic filter to tables. Used only in serials claims if i'm not mistaking. uiTableFilter and tablefilter achieve almost the same goal: * uiTableFilter propose just one filter, generic, outside of the table. You enter something, and any cell with the entered value is kept, others are hidden * tablefilter add a line to the table, just below column names (see the screenshot on bug 6086) the filter can be very detailled. It handles filters from a list, not only from an entered value. We have options: * those 2 plugins are not exactly the same, let's go with both (at the price of sometimes graphic inconsistencies or difficulties to choose one or the other plugin) * uiTableFilter is great, the other gives us too much detail, let's stick with uiTableFilter, don't add another table plugin ! * tablefilter is great, it's better to have a lot of details, it's easier to understand how it works (the uiTableFilter is outside the table, it's strange...) switch to tablefilter and remote uiTableFilter ! What do you think we should do ? Is there an other thing we should take care of ? Anyone knowing the killing-plugin-for-table we should use for sorting/filtering/doing everything on table ? Personally, I think I prefer a little bit tablefilter, I already had some usability questions from Owen about uiTableFilter used in a smart-rules patch we've submitted (and has not been applied yet) Depending on the conclusion, i'll QA the 6086 differently ;-) -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08

6 7

Strange encoding problems that sometimes happens
by Paul Poulain 02 Sep '11

02 Sep '11

Hello, English natives will less concerned by this problem probably, but there are/were some places where strange encoding problems occurs. We have a fix for them (use utf8 decode function), but I was wondering what was the origin of this problem. I think Frédérick Capovilla has a good explanation that I share with you (it's a copy/paste of but 6479) > It's been a while since I created that patch but here is what I understand : > > I remember that in the NewIssue subroutine of Serials.pm, The content of > $serialseq is concatenated with a variable fetched from a SQL query and that's > where the problem happen. > > I did some tests to check the utf-8 flag on those two variables > $serialseq = variable from the form (is_utf8 = false) > $recievedlist = variable from SQL (is_utf8 = true) > > The encoding of the data fetched from SQL differs from the encoding of the data > received from the form. If two string with a different encoding gets > concatenated together, the encoding of one of the string is automatically > changed, and we get an encoding problem on one half of the string. > > Using decode on $serialseq adds the utf-8 flag, so we don't get an encoding > problem when we concatenate. > > > We don't get this encoding problem when the first item is added in > $recievedlist because $recievedlist is empty and doesn't automatically get the > utf-8 flag. I'm guessing Perl DBI automatically addes the utf-8 flag if it > finds utf-8 characters in a string returned from a SELECT. If there are remaining places where this problem occurs, we know why & how to fix it then ! PS: This explanation sounds highly logical to me. But if someone disagree or has another explanation, feel free to drop a comment on the bug or continue this thread ! -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08

2 1

call for help = BZ6328
by Paul Poulain 02 Sep '11

02 Sep '11

Hello all, Koha 3.6 will be released in less than two months, and there is a very important patch that I just rebased a few minuts ago (& squashed) It's the BZ 6328, and is related to fine in days. For french libraries it's a must-have, 99% of french libraries set fines in days of debarment instead of money. This feature had been integrated in 3.4, but it was not functionnal, some important things were missing (it works on biblibre/master, the problem was, as many times we've already seen, we had everything in a single branch). So i'd like to see this patch taken into account. So if you want to have a look (yes, you...), feel free ! Thanks -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08

1 0

RFC - Admin Dashboard
by Barry Cannon 01 Sep '11

01 Sep '11

Hello, I have added an RFC and bug (6828) for the addition of a new feature in 3.6. The enhancement will provide an admin/staff user the ability to view a library Dashboard once logged in. The dashboard will display various library/branch specific information. Comment and suggestions much appreciated. Regards Barry(a)oslo.ie http://www.oslo.ie

2 1

2011-09-02 Global bug squashing day #4 - It's on! Join the fun!
by Magnus Enger 01 Sep '11

01 Sep '11

Dear Community! Just a gentle reminder that GBSD#4 started about half an hour ago, in Kiribati. If Friday September 2nd is inconvenient for you in your timezone you might want to consider diving in now, to get a head start! ;-) For those watching at home, a lot of the changes on Bugzilla will be tweeted here: http://twitter.com/#!/KohaGBSD Best regards, Magnus Enger ---------- Forwarded message ---------- From: Magnus Enger <magnus(a)enger.priv.no> Date: 30 August 2011 08:35 Subject: 2011-09-02 Global bug squashing day #4 To: Koha list <koha(a)lists.katipo.co.nz>, koha-devel(a)lists.koha-community.org Dear Community! Just a gentle reminder that GBSD#4 is approaching fast: http://wiki.koha-community.org/wiki/2011-09-02_Global_bug_squashing_day Please bear in mind that the Release Manager has declared the following dates: * Feature freeze – 22 September 23:59 UTC – From this point on, no new features will be considered for inclusion into 3.6.0 * String freeze – 8 October 23:59 UTC – no bugs that change templates accepted after this point. This allows the translators to translate without things changing on them http://koha-community.org/key-dates-3-6-0/ That means we have about 3 weeks for getting any new features in! And there are (at the moment) 83 (!) bugs/patches waiting to be signed off: http://bugs.koha-community.org/bugzilla3/buglist.cgi?bug_status=NEW&bug_sta… See one in there that you would like to make sure makes it into Koha 3.6? YOU can help it along by signing off on it! http://wiki.koha-community.org/wiki/Sign_off_on_patches Of course, we should take every opportunity to sign off patches in the coming weeks, but why not make a concerted effort on Friday September 2nd 2011 (in your timezone) and see how far we can get, as a team? Could we cut the queue in half? Happy hunting! Magnus Enger PS And you don't have to be a developer to help either!

1 0