January 2017 - Koha-devel - lists.koha-community.org

Koha 3.22, Plack & EDS plugin
by Paul Poulain 27 Mar '17

27 Mar '17

Hello friends, We've deployed Koha 3.22, running Plack and the EDS plugin, and it appears that it does not work. We think it's because there are some .pl code that is out of plack scope, so it's not run. Is there anyone here who has some experience with koha / Plack / EDS ? (Frido will probably send a patch to Ebsco in the next days if there's no other ida) -- Paul Poulain, Associé-gérant / co-owner BibLibre, Services en logiciels libres pour les bibliothèques BibLibre, Open Source software and services for libraries

5 8

proper sorting order and search for Swedish characters and ISBN search
by Gaetan Boisson 02 Feb '17

02 Feb '17

Hello, I have been trying several things to try to sort this out, and haven't found a way (yet) that would avoid ugly compromises. The issue is: in Swedish ä, ö and å are separate letters. Not variants of a and o. This means that searching for å shouldn't bring up a. When sorting, they belong to the very end of the alphabet, after z, not along a and o. ICU has some kind of setting that allows to standardize isbns for searching, so you can search for any hyphenated variant, and still find the isbn that actually appears in your data. I *think* this works by removing all the hyphens in the index, but i am not quite sure. Anyway, in order to get the Swedish letters right, we had to do some specific chr configuration. Doing this forces us not to use ICU, which means giving up on standardized isbn search. Alternatives are transforming all the isbns in the records (quite uly). Or using the SearchWithISBNVariations syspref, but as far as i understand, this only works when using the dedicated isbn index, not in the simple search. Has anyone found a more satisfactory way of handling this? Thanks, -- Gaetan Boisson Chef de projet bibliothécaire BibLibre +33(0)6 52 42 51 29 108 rue Breteuil 13006 Marseille gaetan.boisson(a)biblibre.com

6 6

Fwd: [Koha-translate] Help Manual translation help - script to generate
by Francois Charbonnier 31 Jan '17

31 Jan '17

Hello all, Chris gave me indications to understand how the translation of the manual will work for 16.11. I don't fully understand how it works. But, right now I'm working on 16.05. The process is different and I want to be able to generate the manual the way we have it in the /html-desktop, /html and /pdf folders (http://translate.koha-community.org/manual/16.05/fr-CA/) I'm sure there is a script somewhere to automate the generation for every langage on pootle. And there is a probably a gitted stylesheet somewhere as well. Does anyone know where all this is ? As soon I have the information, I will update the wiki. I think it help the translator to be able to generate locally the manuel they are translating! Thanks a lot! -------- Message transféré -------- Sujet : [Koha-translate] Manual translation - scripts Date : Tue, 24 Jan 2017 08:00:50 -0500 De : Francois Charbonnier <francois.charbonnier(a)inlibro.com> Pour : Koha-org - Translate list <koha-translate(a)lists.koha-community.org> Hello, Lately, I worked on the documentation translation for 16.05 (fr-CA). To check the results, I tried to generate the html the version. I haven't found any documentation to get what we have right now in the /html-desktop, /html and /pdf folders. I have been able to generate the manual.html we used to have before. But, I can't retreive all the translations I've worked ono. Some chains stay untranslated but they are in my po files... Could someone give me the indications to translate properly the manual offline ? I will update the wiki with these indications! :^) Thanks a lot! François -- François Charbonnier, Bibl. prof. / Chef de produits Tél. : (888) 604-2627 francois.charbonnier(a)inLibro.com <mailto:francois.charbonnier@inLibro.com> inLibro | Spécialistes en technologies documentaires | www.inLibro.com

1 0

Koha 16.05.09 security release
by Mason James 31 Jan '17

31 Jan '17

The Koha community is proud to announce the release of Koha 16.05.09 This is a security release and contains several bugfixes. If you are running 16.05.x, we strongly recommend you update. Packages are available. For the full release notes see... https://koha-community.org/koha-16-05-09-security-release/

1 0

Koha 16.11.03 security release
by Katrin Fischer 31 Jan '17

31 Jan '17

1 0

Koha Community Newsletter: January 2017
by kohanews 31 Jan '17

31 Jan '17

Fellow Koha users: The Koha Community Newsletter for January 2017 is here: https://koha-community.org/koha-community-newsletter-january-2017/ Many thanks to the folks who submitted articles and news to this month's newsletter. Please feel free to email me with any corrections or suggestions. Thanks! -- Chad Roseburg Editor, Koha Community Newsletter

1 0

Quick and easy sign off
by David Cook 25 Jan '17

25 Jan '17

Hi all, It looks like I accidentally introduced a bug into Koha with my patch for Bug 17880. It's a little copy/paste error and I've already posted the one line patch fix to Bug 17986 https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17986. I'd be delighted if someone would look at it, since it effects Koha 16.11.02 and Koha Master. Most notably on the "Perl modules" tab of /cgi-bin/koha/about.pl and when using koha_perl_deps.pl -a -c. Thanks, David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595

3 2

Horizon to Koha migration
by Peter Fanter 25 Jan '17

25 Jan '17

Hello, has someone experience, or provide me with documentation, with what one must do, in order to make a migration, from Horizon to Koha? We have access only to a Horizon database, so we can only run sql queries, and we must get back, as much as possible info needed. I know the Koha part, i lack the knowledge, of how to extract info from Horizon, what tables exist, what info they have, how combine tables, etc Thank you very much

2 1

Matthias working on Coral <> Koha interface
by Paul Poulain 25 Jan '17

25 Jan '17

Hello Koha & Coral lists, I'm happy and proud to announce that in the next 3 months, Matthias will work full time on Coral <> Koha interface. He can be dedicated to this task thanks to 3 companies that joined their strength and money to make this possible: Ebsco (45%), BibLibre (40%) and ByWaterSolutions (15%) He will start by playing the new features and installer of Coral 2.0. Then he will improve the specs I've written (and already sent to some/most of you. If you want them, just ask). Then he will code. Things he will work on : * rebase the Coral <> gokb interface and officially submit it for inclusion into Coral. That will be a first step and framework for later inclusion of Ebsco KB. * work on linking Coral and Koha acquisitions modules: share organizations/vendors, budgets, create basket in Koha from a given Coral acquisition workflow, share bibliographic records when relevent. Some general guidelines we will follow: Coral: * we will keep things as ILS-agnostic as possible. It means we will use webservices, and never access the Koha DB from Coral * Every "linked" feature will be activated through the configurations files. If not activated, Coral users will see no change. That's important for "Coral without Koha" * We will have to add some fields to store the links between ILS and Coral data. Koha: * We will mostly add webservices (restful, of course), related to acquisition (vendors, budget, baskets, ...). * We will have to add some fields to store the links between Koha and Coral data. Hopefully, at the end of those 3 months, we should have a working version 1, not complete, that could be improved for an easier use. Our long term goal is to have a fully integrated solution. -- Paul Poulain, Associé-gérant / co-owner BibLibre, Services en logiciels libres pour les bibliothèques BibLibre, Open Source software and services for libraries

4 3

Coding Guidelines: POD Documentation
by Nick Clemens 25 Jan '17

25 Jan '17

Hello Koha developers, At the last developers meeting there was some discussion about guidelines for requiring POD during QA. Our current guideline is here: https://wiki.koha-community.org/wiki/Coding_Guidelines#PERL13:_POD The discussion centered on a few questions: 1 - Should (basic) POD be required when making a small change to a module that has no existing POD. The answer to this seemed to be generally yes, and Barton volunteered to assist. Anyone else wanting to help add POD is more than welcome to join him :-) 2 - Where should POD go? Inline or after __END__ Please offer your opinion if you feel strongly. As I am cutting it close to sending before the meeting I think we can push off adding/updating the guideline until the February meeting. Thanks! Nick (kidclamp)

3 2