November 2016 - 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

log file of activities for admin of koha in the library
by rania azad mohammed 18 Jan '17

18 Jan '17

Dear We are 3 admins in the library working on shifts in the library, each of us log-in during her time. I want a report or log file to see all the activities of each admin during a specific day. is there such report or file? I tried to find it using the wiki but hopeless -- *Regards,* *Rania Azad |* Library Manager Library Department http://library.auis.edu.iq/ The American University of Iraq, Sulaimani Office: *B-G-32* Ext *1219*

7 13

FYI: yaz-client limitations
by Tomas Cohen Arazi 12 Jan '17

12 Jan '17

Barton told me it could be useful to share this excange I had with IdexData people during the implementation of the Zebra facets. It highlights a limitation on the yaz-client tool, and they suggest we better use zoomsh. I'm not sure if I already posted this on koha-devel, but it doesn't hurt to re-post, and might save some people some hours and headaches. Regards ---------- Forwarded message --------- From: Adam Dickmeiss <adam(a)indexdata.dk> Date: lun., 9 mar. 2015 a las 6:36 Subject: Re: [Info] Possible limit on the amount of specs on an elementset? [ZEB-663] To: Tomas Cohen Arazi <tomascohen(a)gmail.com> Cc: jira(a)indexdata.com <jira(a)indexdata.com> On 03/02/2015 12:18 PM, Tomas Cohen Arazi wrote: Hi, I compiled 2.0.60 with the aim to patch it for a problem we are facing, and I can say the problem I previously reported is still present: This a limitation in yaz-client which has a limit of 100 characters for elem command. We'll remove that limitiation. You can use zoomsh instead to play with longer facet specs. / Adam Z> elem zebra::facet::su-to:0:100,su-geo:0:100,su-ut:0:100,au:0:100,se:0:100,itype:0:100,location:0:100,holdingbranch:0:100,homebranch:0:100,tomas:0:100 Z> s 1+1 Sent presentRequest (1+1). Records: 1 Record type: XML <record xmlns="http://www.indexdata.com/zebra/"> <facet type="0" index="su-to"> </facet> <facet type="0" index="su-geo"> </facet> <facet type="0" index="su-ut"> </facet> <facet type="0" index="au"> <term coccur="2" occur="2">Adåker, Ulf</term> <term coccur="2" occur="2">Danielsson, Palle</term> <term coccur="2" occur="2">Stenson, Bobo</term> <term coccur="1" occur="1">Davis, Miles</term> <term coccur="1" occur="1">Löfcrantz, Johan</term> <term coccur="1" occur="1">Milder, Joakim</term> <term coccur="1" occur="1">Öström, Magnus</term> </facet> <facet type="0" index="se"> </facet> <facet type="0" index="itype"> </facet> <facet type="0" index="location"> </facet> <facet type="0" index="holdingbranch"> </facet> </record> nextResultSetPosition = 2 Elapsed: 0.001203 So 'holdingbranch' is the last facet it retrieves. If I thange the elementset like this: Z> elem zebra::facet::su-to:0:100,su-geo:0:100,su-ut:0:100,au:0:100,se:0:100,itype:0:100,location:0:100,tomas:0:100,homebranch:0:100,holdingbranch:0:100 I still get a 8 facet limit: Z> s 1+1 Sent presentRequest (1+1). Records: 1 Record type: XML <record xmlns="http://www.indexdata.com/zebra/"> <facet type="0" index="su-to"> </facet> <facet type="0" index="su-geo"> </facet> <facet type="0" index="su-ut"> </facet> <facet type="0" index="au"> <term coccur="2" occur="2">Adåker, Ulf</term> <term coccur="2" occur="2">Danielsson, Palle</term> <term coccur="2" occur="2">Stenson, Bobo</term> <term coccur="1" occur="1">Davis, Miles</term> <term coccur="1" occur="1">Löfcrantz, Johan</term> <term coccur="1" occur="1">Milder, Joakim</term> <term coccur="1" occur="1">Öström, Magnus</term> </facet> <facet type="0" index="se"> </facet> <facet type="0" index="itype"> </facet> <facet type="0" index="location"> </facet> <facet type="0" index="homebranch"> </facet> </record> nextResultSetPosition = 2 Elapsed: 0.003697 On Mon, Feb 9, 2015 at 5:08 PM, Tomas Cohen Arazi <tomascohen(a)gmail.com> wrote: Is there a way (or could it be) to skip the error if there are elems with results? For facets, it would be great that we could ask for n facets, and retrieve all at once. I'll try 2.0.59 in about two hours and reply. El lun., 9 de febrero de 2015 12:59, Adam Dickmeiss <adam(a)indexdata.dk> escribió: On 02/09/2015 04:51 PM, Tomas Cohen Arazi wrote: It is 2.0.44 on ubuntu 14.04. Should i try a newer? I don't see things changes with respect to facets.. But you could try 2.0.59 out. / Adam El lun., 9 de febrero de 2015 12:48, Adam Dickmeiss <adam(a)indexdata.dk> escribió: On 02/05/2015 11:27 AM, Adam Dickmeiss wrote: Hi Tomas, we'll look into this and get back to you. Please reply-all and keep [ZEB-663] contents in the subject line for future conversation. Hi Tomas, we can't see a limit of 8. Asking for more than 8 returns more than 8. And supplying any non-existing facet-field throws an error. What version of Zebra are you using? / Adam / Adam On 02/04/2015 03:59 PM, Tomas Cohen Arazi wrote: Hi, I've been playing with facets retrieval, which shines in Koha 3.18 (thanks!) One thing I noticed is that asking zebra to retrive more than 8 facets at once doesn't work (it only retrieves 8). What i did was: > elem zebra::facet::a1:0:20,...,a8:0:20,bullshit:0:20 ('bullshit' doesn't exist on the facet indexes) and > f a > s 1+1 shows the expected results. If I do > elem zebra::facet::a1:0:20,...,a7:0:20,bullshit:0:20 It fails ([25] Specified element set name not valid...) Regards -- Tomás Cohen Arazi Prosecretaría de Informática Universidad Nacional de Córdoba ✆ +54 351 5353750 ext 13168 <%2B54%20351%205353750%20ext%2013168> GPG: B76C 6E7C 2D80 551A C765 E225 0A27 2EA1 B2F3 C15F _______________________________________________ Info mailing listInfo@lists.indexdata.dkhttp://lists.indexdata.dk/cgi-bin/mailman/listinfo/info -- Tomás Cohen Arazi Prosecretaría de Informática Universidad Nacional de Córdoba ✆ +54 351 5353750 ext 13168 <0351%20535-3750> GPG: B76C 6E7C 2D80 551A C765 E225 0A27 2EA1 B2F3 C15F -- Tomás Cohen Arazi Theke Solutions (https://theke.io <http://theke.io/>) ✆ +54 9351 3513384 GPG: B2F3C15F

2 1

KohaDevBox v2.0 released
by Tomas Cohen Arazi 11 Jan '17

11 Jan '17

After lots of months of work and people's contributions, we finally reached our milestone for v2.0. The original KohaDevBox functionalities are all implemented on the Ansible-driven one, and we can now focus on making it even better (we already have Elasticsearch integration, automatic superlibrarian user creation, and lots of configuration options). It can be used on Linux, Mac OS and Windows. It provides a full development and testing environment for people willing to work on the project. Read the README.md[1] file to get an idea of how easy is to get a full development environment, and the flexibility you can get with all the options we provide. Please enjoy it, and fill issues for any problem you might have. It can be improved, and we count on you to help us :-D Koha Development Team [1] https://github.com/digibib/kohadevbox -- Tomás Cohen Arazi Theke Solutions (https://theke.io <http://theke.io/>) ✆ +54 9351 3513384 GPG: B2F3C15F

2 3

Zebra: the 'elements zebra::snippet' doesn't work
by Tajoli Zeno 11 Jan '17

11 Jan '17

Hi all, I trying to check my indexes in Zebra. My setup: OS: Debian jessie Koha: 3.20.7 [manual install] Zebra: 2.0.61 [install from IndexData repo] Format: UNIMARC Probably the fact that I use unimarc is relevant but I don't understand where. I do the debug described here: http://wiki.koha-community.org/wiki/Troubleshooting_Zebra#Why_does_a_search… The result of a working search is: Diagnostic message(s) from database: [25] Specified element set name not valid for specified database -- v2 addinfo 'zebra::snippet' but my ../etc/zebradb/retrieval-info-bib-dom.xml is correct: <?xml version="1.0" encoding="UTF-8"?> <retrievalinfo xmlns="http://indexdata.com/yaz"> <retrieval syntax="unimarc" name="F"> <backend syntax="xml" name="marc"> <marc inputformat="xml" outputformat="marc" inputcharset="utf-8" outputcharset="utf-8"/> </backend> </retrieval> <retrieval syntax="unimarc" name="B"> <backend syntax="xml" name="marc"> <marc inputformat="xml" outputformat="marc" inputcharset="utf-8" outputcharset="utf-8"/> </backend> </retrieval> <retrieval syntax="xml" /> <retrieval syntax="xml" name="index"/> <retrieval syntax="xml" name="marc" identifier="info:srw/schema/1/marcxml-v1.1"/> <retrieval syntax="xml" name="marcxml" identifier="info:srw/schema/1/marcxml-v1.1"/> <retrieval syntax="xml" name="zebra::*"/> </retrievalinfo> Do I need to check in other places for the setup of ' zebra::snippet' ? Bye Zeno Tajoli -- Zeno Tajoli / SVILUPPO PRODOTTI/ - Automazione Biblioteche Email: z.tajoli(a)cineca.it Fax: 051/6132198 *CINECA* Consorzio Interuniversitario - Sede operativa di Segrate (MI)

5 13

942 versus 952
by Karen Myers 02 Dec '16

02 Dec '16

Hi all I am wanting to clarify the usage of the 942$c field versus the 952$y field as I am setting up a new bib framework. I am wondering if it is necessary to have both the 942$c field and the 952$y field in the framework as they seem to record the same information i.e Koha item type. Is there an advantage to recording the same information in both fields and if not which is the preferred? We are using Koha 3.22 thanks! Karen

3 3

Koha Community Newsletter:November 2016
by kohanews 30 Nov '16

30 Nov '16

Fellow Koha users: The Koha Community Newsletter for November 2016 is here: https://koha-community.org/koha-community-newsletter-november-2016/ 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

Questions regarding localization
by Roger Grossmann 29 Nov '16

29 Nov '16

Hi all, as a Koha development newbie I am having a few questions especially with localization. I am developing enhancements which I plan to bring in to the community hopefully soon. Your answers will help to make progress with it. 1st question ---------------- After looking at much Koha code I did not find a solution to build server side localized strings to persist localized text in the database. What do you recommend to use here? Background: As you know, fines and fees are a sensitive area. Borrowers like to know exactly why they are charged and for what exactly. Lets assume, you want to store good localized name for the type of an overdue fine. It was for instance planned for function "UpdateFine" in C4::Overdues but the parameter $type is never filled as originally planned. If an additional type name would be passed here, it needed to be a localized string since borrowers want to read the charge reason in their language. As this is just an example for the use of a localized server text, the question is, whether there is already an approach to manage localised server side texts. Ideally, server side texts would support parameter replacement that is not dependent of the position in the text as for instance with %s using sprintf. 2nd question ----------------- I want to build some new UI functionality. The procedure how to do that with templates in english first is clear to me. As I am German, I would like to build during development a first German version of the template as well and would like to extend the related German .po file. How can I add the texts for a specific language in my development environment? Is there a way to extract the new texts of templates and add them to an existing .po file with a script and use poedit to translate them? How do you do that? Thanks in advance for your help. Best regards, Roger -- Roger Großmann LMSCloud GmbH Konrad-Zuse-Platz 8 - D-81829 München t +49 (0)89 207042-620 m +49 (0)171-2194775 f +49 (0)89 207042-623 e roger.grossmann(a)lmscloud.de w www.lmscloud.de

2 3

Koha 16.11.00 Debian package released
by Mirko Tietgen 28 Nov '16

28 Nov '16

Hello everyone, the Debian package for Koha, koha-common 16.11.00, is now available from the community repository. Please note that with the new release, the codename/version relationship shifts to stable 16.11 oldstable 16.05 Koha 3.22 is still maintained, but there won't be new Debian packages for this branch an longer. Koha 16.11 requires Debian Jessie. Debian Wheezy is not supported any longer. The same goes for future versions of Koha 16.05. We still have problems with Koha and MySQL 5.7. If you want to run Koha 16.11 on Ubuntu, you will probably have the best experience with Ubuntu 16.04 LTS and MariaDB instead of MySQL 5.7. If you are running Koha 16.05 now and want to stay on this branch, please make sure to change your apt configuration to use the oldstable branch. To upgrade to Koha 16.11, use stable in your apt configuration and do apt-get update apt-get upgrade apt-get dist-upgrade Please report any bugs you may encounter to http://bugs.koha-community.org/ Cheers, Mirko -- Mirko Tietgen mirko(a)abunchofthings.net http://koha.abunchofthings.net http://meinkoha.de

1 0