November 2014 - Koha-devel - lists.koha-community.org

Marseilles hackfest 2015, proposed date
by Paul Poulain 18 Nov '14

18 Nov '14

Hello, Is there anyone having a (major) problem with Marseilles hackfest occuring in March, 2nd-7th ? I had some feedback from some ppl, removing all "impossible" dates, this one seems OK. -- Paul Poulain, Associé-gérant / co-owner BibLibre, expert du logiciel libre pour les bibliothèques BibLibre, Open Source software for libraries expert

2 1

RFC: LDAP login fallback
by Tomas Cohen Arazi 18 Nov '14

18 Nov '14

If you take a look at bug 12831 [1] you will notice it reads as an important bug, but hasn't got much attention. The main reason the bug is stuck is that there's no consensus on what the fallback functionality use case(s) would be. My POV is that we should identify previous behaviour and restore it. As a non-LDAP user I think the logic should work as a simple fallback: Login fails (different reasons, take care of that as a future enhancement) => retry, with the local DB. It doens't seem difficult to implement. But as a non-expert LDAP user I don't know the usual use cases. Please share your use cases and/or comment here and on the bug itself so we have chances to fix this (bug?) for the release in less than two weeks. Thanks in advance Tomás [1] http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12831

1 0

tests for utf-8
by Zeno Tajoli 17 Nov '14

17 Nov '14

Hi to all, at http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13264 I have insert a very basic test on utf-8 on Opac. This test need a specif enviromet: -- working zebraserver -- wokrking background indexer -- the base url of intranet in env variable KOHA_INTRANET_URL -- the base url of opac in env variable KOHA_OPAC_URL if the enviroment is not good, all test are skipped, not a faliure. To do the tests I need to records, one Unimarc and one MARC21. A question about writting patch: Is it better to have a specific patch only for the two iso2709 records ? Is it a good idea to insert in the git archive a version of two record in a flat/open format (like '.mrk' of MarcEdit) ? Reading the code I find an other test that covers utf-8: t/db_dependent/Koha_Database.t Bye Zeno Tajoli -- Dr. Zeno Tajoli Soluzioni per la Ricerca Istituzionale - Automazione Biblioteche z.tajoli(a)cineca.it fax +39 02 2135520 CINECA - Sede operativa di Segrate

2 1

Ambiguous column names
by Marcel de Rooy 14 Nov '14

14 Nov '14

Hi, While adding a timestamp to the borrowers table, I ran into the trouble of ambiguous column names when querying multiple tables. See BZ 10459. Until now we added timestamps to several tables while just naming them "timestamp". Adding more timestamps will be increasingly difficult since we have to check all SQL queries that reference timestamp (from another table) and the table at hand. So I now consider adding borrowertimestamp, or bortimestamp (ugly but shorter). Any thoughts about doing this in some consistent manner? Marcel

6 14

Minor change on HEA
by Paul Poulain 10 Nov '14

10 Nov '14

Hello, Jonathan just made 2 tiny changes on HEA (hea server side, no change on Koha) * HEA now records the creation datetime of an entry. That way we will be able to know which records are never updated (and maybe remove them one day) * when a Koha library send his informations for the 1st time, HEA give it a unique ID. The way the unique ID is generated has been changed, to be less easy to guess by brute force (in case someone would like to hack & flood HEA). database that already have sent their data will keep their previous identifier. Note that http://hea.koha-community.org/ contains the informations for 34 (BibLibre supported) libraries, and, hopefully, much more will be added when Koha 3.18 is released ! All vendors are more than welcomed to set-it HEA for their libraries (and all independent libraries too, of course) After Koha 3.18 release, I plan to submit the patch for previous maintained versions, so we should get more versions info, hopefully. -- Paul Poulain, Associé-gérant / co-owner BibLibre, expert du logiciel libre pour les bibliothèques BibLibre, Open Source software for libraries expert

1 0

Opac doesn't support IE6 and IE7 (with js enabled). Are we aware of this ?
by Zeno Tajoli 10 Nov '14

10 Nov '14

Hi to all, cheking if do o not update of JQuery plugin DataTables I find that now the Opac doesn't support IE6/IE7 with boostrap theme (the default theme now). In fact we use the plugin jstree, https://github.com/vakata/jstree/, that work only from IE8. Probably it work if you disable javascript but many features of Opac are based on javascript. For me it OK, IE6 and IE7 are only 3% of desktop browsers if we check wikipedia source, http://en.wikipedia.org/wiki/Usage_share_of_web_browsers. But: -- Are we aware of this situation -- Is it OK ? Bye Zeno Tajoli -- Dr. Zeno Tajoli Soluzioni per la Ricerca Istituzionale - Automazione Biblioteche z.tajoli(a)cineca.it fax +39 02 2135520 CINECA - Sede operativa di Segrate

7 11

Proposal for a change in guidelines for the sign-off process in the Koha-community
by Brendan Gallagher 10 Nov '14

10 Nov '14

Hello All - During the hackfest, there was a discussion on the sign-off process for Koha. In attendance was, Nathan, Chris, Katrin, Paul_P, Jonathan, Arnaud, Joy, Brendan, Tomás, Brooke, Tom, and BobB. Here is what we all agreed upon to send a proposal to the next developers or general meeting I'd like to put forward a motion for removal of the guideline that one company shouldn't sign-off on the same company's patches within the community. I am suggesting additional checks be included in the sign-off process to prevent abuse of the proposed guideline, such as the committer and the person signing off must not have collaborated on the development of the patch. We shall review that idea/process every 6 months as an agenda item in the general meeting, to make sure that no abuse of the new privilege has occurred; also note here - that we do not have to wait 6 months to point out abuse of this new privilege. The QA team and Release Team still have the right to ask for more eyes to look at a certain bug at anytime and this should continue. Thank you, Brendan Gallagher

6 9

3.18 dates
by Tomas Cohen Arazi 06 Nov '14

06 Nov '14

I asked Bernardo to create the 3.18 translate project on Pootle, and we already have most of the 3.18 strings on the translate server. We still need to set a string freeze date. I propose the following dates: - String freeze: November 20th After that date, patches that touch strings will be delayed until after the release. There might be some exceptions I will consider if necesary: * Blockers. * Small changes to the about page for the release. - Release: November 28th I chose friday for a release, so everyone can have a proper release party without the need to go to the office on saturday :-D It's getting closer! YAY! Thanks everyone.

1 0

Fwd: RDA records
by Nicholas van Rheede van Oudtshoorn 06 Nov '14

06 Nov '14

Hi all, Got this from our librarian the other day, and wondered if anyone could shed any light on this. We've got an RDA framework, and basically it won't save any modifications to the items. New items are added fine, but existing one's just silently don't make any changes... I've included the email below, since it gives the exact workflow... Nick ---------- Forwarded message ---------- From: Judy Smith <judy(a)pbc.wa.edu.au> Date: Thu, Oct 30, 2014 at 11:33 AM Subject: RDA records To: Nicholas van Oudtshoorn <vanoudt(a)gmail.com> [image: Perth Bible College] [image: Thinking Service] 1 College Court Karrinyup WA 6018 Australia Phone: +61 (0)8 9243 2000 Fax: +61 (0)8 9243 2050 college(a)pbc.wa.edu.au www.pbc.wa.edu.au CRICOS Provider Code: 00986G ABN: 52 599 089 532 Hi Nick, In saving a record using RDA I found that once I had saved a record and entered the item details, and also saved that, when I wanted to change any details in the item record I was unable to do so. I was able to select a different item location but when I tried to save this the details went back to the original selection. Judy Smith Perth Bible College judy(a)pbc.wa.edu.au This email is intended for the stated recipient only, and may contain confidential information. If you are not the stated recipient, you are not allowed to use or disclose any information contained within this communication. If you have received this email in error, please contact the sender immediately and delete this email from your system.

1 0

Koha Community Newsletter: October 2014
by Koha News 05 Nov '14

05 Nov '14

Fellow Koha users: The Koha Community Newsletter for October 2014 is here: http://koha-community.org/koha-community-newsletter-october-2014/ Many thanks to the folks who submitted articles and news to this month's newsletter. Please feel free to email us with any corrections or suggestions. Thanks! Chad Roseburg Joanne Dillon Editors, Koha Community Newsletter

1 0