December 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

Koha 16.11.01 released
by Katrin 10 Jan '17

10 Jan '17

The Koha community is proud to announce the release of Koha 16.11.01 This is the first maintenance release of 16.11 and contains several bugfixes. The full release notes are available at https://koha-community.org/koha-16-11-01-released Packages will be available soon. Happy holidays!

1 1

Benchmarks for 16.11
by Jonathan Druart 02 Jan '17

02 Jan '17

Hi devs, I have done some benchmarks for versions of Koha from 3.14 to the latest 16.11 You can find the results on the wiki: https://wiki.koha-community.org/wiki/Benchmark_for_16.11 To be able to go back in time, I had to modify the koha-misc4dev scripts. I am now able to get a Koha installations fully testable (items, reindexation, psgi file, etc.) with any of these versions in a few minutes, which is pretty awesome and will be very useful for debugging (and git bisecting). Note that not everything is clean at the moment and will still need some works (path in psgi file for instance). All of you should be able to replay the full benchmark script on your kohadevbox, so please do it. That way we will confirm (or not) these numbers. If you want to compare 3.8, feel free to adapt the different scripts (I can help for that) and post the results. Cheers, Jonathan

3 2

Koha Community Newsletter: December 2016
by kohanews 30 Dec '16

30 Dec '16

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

Re: [Koha-devel] Koha Maps
by Marshall Breeding 28 Dec '16

28 Dec '16

Here is the version of Prosentient Systems Koha clients via Library Technology Guides: https://librarytechnology.org/libraries/map.pl?ILS=Koha%20--%20Prosentient%… List version: https://librarytechnology.org/libraries/search.pl?ILS=Koha%20--%20Prosentie… -marshall Marshall Breeding marshall.breeding(a)librarytechnology.org www.librarytechnology.org/ twitter.com/mbreeding http://www.linkedin.com/in/breeding http://scholar.google.com/citations?user=NnvfJ5cAAAAJ -----Original Message----- From: Edmund Balnaves [mailto:ebalnaves@prosentient.com.au] Sent: Wednesday, December 21, 2016 5:46 PM To: 'Chris Cormack'; Marshall Breeding Cc: 'koha'; 'Koha-devel' Subject: RE: [Koha-devel] Koha Maps Hi Marshall, Chris We already have a map of our libraries - http://www.prosentient.com.au/index.php/koha An API where we could push these details in bulk through to you would be great - we could send through the details of the library geocode details. Regards Edmund Edmund Balnaves, PhD Hosted Services Prosentient Systems P/L ABN 31 078 409 168 72/330 Wattle St, Ultimo NSW 2007 tel: 02 92120899 fax: 02 92120885 mobile: 0414737560 ejb(a)prosentient.com.au -----Original Message----- From: koha-devel-bounces(a)lists.koha-community.org [mailto:koha-devel-bounces@lists.koha-community.org] On Behalf Of Chris Cormack Sent: Wednesday, 21 December 2016 7:39 AM To: Marshall Breeding <marshall.breeding(a)librarytechnology.org> Cc: koha <koha(a)lists.katipo.co.nz>; Koha-devel <koha-devel(a)lists.koha-community.org> Subject: Re: [Koha-devel] Koha Maps * Marshall Breeding (marshall.breeding(a)librarytechnology.org) wrote: > I have been following the discussion about how the Koha community can > better market itself, including using a map display to emphasize its > global impact. > > > > Naturally, I would be happy to have the map generated from Library > Technology Guides to be used. Doing so would help me ensure that my > registry of libraries using Koha is more complete since libraries might > be more motivated to be included. Regardless of whether the Koha > community decides to rely more on my mapping tool, I will continue to try > to obtain data on the many libraries using Koha that are not yet > registered on my site or any other database. I continue to think that > Koha is most likely the most implemented ILS, but I do not yet have the > data to validate that assertion. > > > > The purity of working only with open source software and open access data > seems to me like an impossible goal. Richard Stallman, who I heard speak > last year, takes this concept to its logical conclusion, and ends up with > quite a limited realm of software or data which meet his tests for purity. > Is the Koha community comfortable using the Google Map API, for example, > since it is based on a closed and proprietary information infrastructure > and underlying software components that may or may not be open source? Or > does it plan to invent its own global mapping ecosystem? > That's what Open Street Maps is. Are you sure you want to get into a discussion about the ethics of open vs closed/proprietary on this mailing list? > > > I have looked at the Hea tool and I have a hard time imagining it gaining > the functionality of a global mapping visual and becoming well populated > by the mechanisms provided. Since it is generated mechanically through > each instance of Koha, it will be difficult to translate this data to > represent the libraries that are actually using Koha in production. Many > of the entries shown now (http://hea.koha-community.org/libraries) seem to > be duplicates or test implementations. Its single entry for the NExpress > Shared Catalog is represented by 53 libraries on my maps. I don’t see hea > as having the structure has the ability to represent the branches > associated with a library system or consortia and many other aspects of > tracking the libraries which use any given automation system. I think > that many, if not the majority, of Koha implementations globally are based > on older or forked versions of Koha, making it difficult or impossible for > them to automatically contribute their data to Hea. > > > > I also wonder why the Koha development community would divert resources > into re-creating such a tool from other efforts to develop and promote > Koha. Having maintained a registry of libraries for almost two decades, > my experience tells me that it is much more difficult to create and > maintain a well-organized list than others might imagine. > > > > I have also just re-written the map tool on Library Technology Guides to > generate the display more quickly when there are a very large number of > libraries. Although it depends on how quickly the Google API responds, it > now builds the maps in a few seconds, compared to almost a minute > previously. I have also added some basic search selection tools at the > bottom of the page: > > https://librarytechnology.org/libraries/map.pl?ILS=Koha > > > > I’ll be interested to hear further discussion on the topic. > The main thing I would be interested in hearing is that you have licensed the data in the tool under an open license. And then we could use it without issue. Chris > > > Marshall Breeding > > marshall.breeding(a)librarytechnology.org > > www.librarytechnology.org/ > > twitter.com/mbreeding > > http://www.linkedin.com/in/breeding > > http://scholar.google.com/citations?user=NnvfJ5cAAAAJ > > >_______________________________________________ >Koha-devel mailing list >Koha-devel(a)lists.koha-community.org >http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >website : http://www.koha-community.org/ git : >http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ -- Chris Cormack Catalyst IT Ltd. +64 4 803 2238 PO Box 11-053, Manners St, Wellington 6142, New Zealand

1 0