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

Re: [Koha-devel] HEA : Error whith the script share_usage_with_koha_community.pl -f
by BOUIS Sonia 22 Jun '17

22 Jun '17

That's it ! Thank you Marcel ! 1. Re: HEA : Error whith the script share_usage_with_koha_community.pl -f (Marcel de Rooy) HEA changed from http to https. I got the same error. Please check if your UsageStats.pm still contains http. Van: koha-devel-bounces(a)lists.koha-community.org [mailto:koha-devel-bounces@lists.koha-community.org] Namens BOUIS Sonia Verzonden: donderdag 22 juni 2017 10:34 Aan: 'koha-devel(a)lists.koha-community.org' <koha-devel(a)lists.koha-community.org> Onderwerp: [Koha-devel] HEA : Error whith the script share_usage_with_koha_community.pl -f Hi devs, I tried to update our data with hea manualy this morning I've just saw that my library isn't listed in hea so I changed the syspref "UsageStats" to "share" and try to launch the script but I have an error message : ./share_usage_with_koha_community.pl malformed JSON string, neither array, object, number, string or atom, at character offset 0 (before "<html>\r\n<head><tit...") at /home/koha/src/C4/UsageStats.pm line 354. We are in a 3.22.20 version. Did we miss something or is it a bug ? Cheers, Sonia BOUIS Responsable du Service des application documentaires BIBLIOTH?QUES UNIVERSITAIRES Biblioth?que de la Manufacture UNIVERSIT? JEAN MOULIN LYON 3 1C AVENUE DES FR?RES LUMI?RE CS 78242 69372 LYON CEDEX 08 ligne directe : +33 (0)4 78 78 79 03 http://bu.univ-lyon3.fr<http://bu.univ-lyon3.fr/> L'Universit? Jean Moulin est membre fondateur de l'Universit? de Lyon

1 0

HEA : Error whith the script share_usage_with_koha_community.pl -f
by BOUIS Sonia 22 Jun '17

22 Jun '17

Hi devs, I tried to update our data with hea manualy this morning I've just saw that my library isn't listed in hea so I changed the syspref "UsageStats" to "share" and try to launch the script but I have an error message : ./share_usage_with_koha_community.pl malformed JSON string, neither array, object, number, string or atom, at character offset 0 (before "<html>\r\n<head><tit...") at /home/koha/src/C4/UsageStats.pm line 354. We are in a 3.22.20 version. Did we miss something or is it a bug ? Cheers, Sonia BOUIS Responsable du Service des application documentaires BIBLIOTHÈQUES UNIVERSITAIRES Bibliothèque de la Manufacture UNIVERSITÉ JEAN MOULIN LYON 3 1C AVENUE DES FRÈRES LUMIÈRE CS 78242 69372 LYON CEDEX 08 ligne directe : +33 (0)4 78 78 79 03 http://bu.univ-lyon3.fr<http://bu.univ-lyon3.fr/> L'Université Jean Moulin est membre fondateur de l'Université de Lyon

2 1

Debian Stretch now stable
by David Cook 22 Jun '17

22 Jun '17

Hi all, I just remembered that I didn't expect Jonas to upload RDF::Trine 1.018 to Debian unstable because of the full freeze on Debian, so I looked up the dates. and it appears that Debian Stretch was released to stable on 2017-06-17. So not quite a week ago. I know I've been around for a few Debian releases, but I can't recall Koha's procedures regarding new Debian releases. I imagine we'll stay on Debian Jessie and Ubuntu 16.04 (Jessie based I think) for a while, but I suppose we'll be targeting Debian Stretch soon? David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595

2 1

Packaging latest RDF::Trine for Debian
by David Cook 22 Jun '17

22 Jun '17

Hi Mirko, I recall you saying that you were willing to package RDF::Trine for Koha on Debian. The current version on Debian Jessie is 1.011 and the current version on CPAN is 1.017, although there is a development release 1.017_1, which is being tested on http://cpantesters.org/. I anticipate a version 1.018 being released in a few weeks, if the time taken for testing and release is the same as 1.017. I don't know if you'd want to wait for 1.018 or start with 1.017 and then do 1.018. In terms of importance, 1.017 contains a fix for a critical bug, while 1.018 is a more minor fix. (I've already coded a workaround for the bug fixed in 1.018 whereas 1.017 can't be worked around.) While testing bug 18713 on Bugzilla, Brendan uncovered a bug in RDF::Trine 1.011. It's fixed in version 1.013, but I think that means we might want to roll a Debian package so that work on RDF can continue. I've been told that Jonas Smedegaard is quite receptive to updating packages in Debian, but I imagine it might be too late to get updates into existing or soon to be released versions of Debian? Anyway, please let me know what you think : ). David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595

2 2

Follow what is waiting for attention on bugzilla
by Jonathan Druart 19 Jun '17

19 Jun '17

Hi devs, Few months ago we have added a "Overall bug tracker health status" section to our dashboard (dashboard.koha-community.org) to quickly highlight the bugs that need urgent attention. I have created a new end point ( http://dashboard.koha-communitrequirey.org/bz_status) to make it easily integrable to your own dashboard (especially useful if you are working in a company). It lists the very important bugs, that need immediate love. If you have time to dedicate to the community you must start with them. Basically the goal of this is to avoid bugs like 18651 to wait for attention for a month whereas it is critical (you know, things like "cannot checkin a book", bad for an ILS, do not you think?) Cheers, Jonathan

2 2

Re: [Koha-devel] KohaCon hackfest
by Jonathan Druart 19 Jun '17

19 Jun '17

Hello Eugene (cc koha-devel list), I had planned to contact you this week to know if you need help, you beat me to it! We have refreshed a bit our wiki pages about how to get involved in the community, so I guess it may be a good read: https://wiki.koha-community.orgneed technical help/wiki/Getting_involved <https://wiki.koha-community.org/wiki/Getting_involved> It will depend on how the participants want to help, but I think you can ask Paul to show you how the sanboxes work, to signoff on patches. I CCed the Koha developers list so they know you need easy patches to test. We usually add the "academy" tag to bug reports easy to test. I have created a search for that: https://frama.link/Koha_academy_NSO_bugs There are only 5 so far but we will try and add more in the next days. If you catch some librarians that are willing to install Koha on their laptop you should guide them to Koha Dev Box (a wiki page should be created before the end of the week, otherwise there is a readme on the dedicated page of the project: https://github.com/digibib/kohadevbox ) You should also join the IRC channel if you need technical help or have any Koha related questions. Cheers, Jonathan On Sat, 17 Jun 2017 at 22:33 KohaCon 17 <kohacon17(a)gmail.com> wrote: > Dear Jonathan, > > KohaCon2017 will be tomorrow and the hackfest will be on Thursday. Based > from the list of attendees, it seems they're almost librarians. Only one or > two developers (we have Paul Poulain attending). I am quite aware of your > position in the Koha Community with regards to its ongoing development. We, > the organizers of KohaCon2017 are reaching out to you to help us in > identifying bugs needing Sign offs and are easier to work with by not so > technically-inclined librarians. Cheers and Mabuhay! > > > Eugene Jose T. Espinoza > Secretary, Association of Special Libraries of the Philippines > Koha ILS Philippines volunteer > >

1 0

Re : State of Elasticsearch support in Koha (Nick Clemens)
by BOUIS Sonia 19 Jun '17

19 Jun '17

Hello Nick, Hello Mirko, Thanks for the wiki page for Elasticsearch support, it's really useful ! I feel frustrated because we are planning a testing day on sandboxes during the French koha symposium next week but we can't test those patches on sandboxes... That's a pity because I know motivated people that would be enthusiastic for testing patches on elasticsearch. Perhaps, there will be some tests during the hackfest at the kohacon : I read that there will be 100 attendees :) Cheers, Sonia 1. Re: State of Elasticsearch support in Koha (Nick Clemens) 2. Re: State of Elasticsearch support in Koha (Indranil Das Gupta) 3. Re: State of Elasticsearch support in Koha (Mirko Tietgen) 4. Re: State of Elasticsearch support in Koha (Tomas Cohen Arazi) 5. Re: State of Elasticsearch support in Koha (Mirko Tietgen) ---------------------------------------------------------------------- Message: 1 Date: Fri, 09 Jun 2017 17:45:46 +0000 From: Nick Clemens <nick(a)bywatersolutions.com> To: Mirko Tietgen <mirko(a)abunchofthings.net>, koha-devel(a)lists.koha-community.org Subject: Re: [Koha-devel] State of Elasticsearch support in Koha Message-ID: <CAA_eX3OxqsDbrDh-wvj2pv7Ep1McRXa7P8dKuFVZasmUgOqsfA(a)mail.gmail.com> Content-Type: text/plain; charset="utf-8" I have been meaning to do this, and this is just a start so anyone can contribute: https://wiki.koha-community.org/wiki/Elasticsearch_status On Thu, Jun 8, 2017 at 5:54 AM Mirko Tietgen <mirko(a)abunchofthings.net> wrote: > Hi everybody, > > is there any kind of summary regarding the state of Elasticsearch > support in Koha at the moment and maybe a roadmap for things that are > missing? > > I'd like to offer the koha-elasticsearch meta package for Koha 17.05, > but as Elasticsearch support is not ready for production (as far as I > know), it should be accompanied by an overview of what to expect > (features and bugs) to not raise false expectations. > > Any information would be appreciated. > > Cheers, > > Mirko > > > -- > > Mirko Tietgen > mirko(a)abunchofthings.net > http://koha.abunchofthings.net > http://meinkoha.de > > _______________________________________________ > 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/ >

1 0

Call for News: June 2017 Newsletter
by kohanews 15 Jun '17

15 Jun '17

I'm collecting news for the June newsletter. Send anything noteworthy to: k o h a news AT gmail dot com News criteria: --------------------------- ** For events **: - Please include dates for past events. If I can't find dates I may not add it. - Announcements for future events with dates T.B.A. are fine ...Eg., Kohacon - For past events , **** one month back is the cut-off ****. * News items can be of any length. * Images are fine * Anything and everything Koha. * Submit by the 26th of the month. If you are working on an interesting project or development related to Koha, please let me know and I'll include it in the development section. Thank you! -- Chad Roseburg Editor, Koha Community Newsletter

1 0

e-books as "virtual items"?
by Giuseppe Angilella 15 Jun '17

15 Jun '17

Hi, (apologies for double posting this here as well, as I think it might contain a suggestion for a possible development in Koha) I've just started populating my library's catalog with e-book readers and e-books. I've defined different item types for either e-readers and e-books, and classified the former as "equipment" and the latter as "monographs" in the appropriate MARC record fields (leader etc). For a given e-reader type (Kindle, say) I may have several items. These are distinct, as they have a different serial number, and receive therefore a distinct barcode. Similarly, they can be borrowed individually. Therefore, they perfectly qualify as "Koha items". On the other hand, an e-book is entered as a specific record (which is distinct from the record of the corresponding hardcopy, if also available), with a cross-link to the e-reader's record in the 773 MARC field. Originally, I thought that no physical item should be attached to an e-book, since it is the e-reader, and not the e-book, which can be borrowed. However, this prevents the e-book to appear in the "Browse shelf" feature, close to books with similar topic (which is very useful for patrons). One solution might be that of restricting the e-book type to "no loan", but then the cross-link to the appropriate e-reader would be contained in the record (Koha's biblioitem), and not in the item (Koha's item), which might be confusing for the patron. Another solution might be that of devising some kind of "virtual items". Several "virtual items" (say, several e-books) could be mapped onto a single (physical) "item", so that whenever the (physical) item is on loan, all of the "virtual items" contained by it are also set "on loan". A "virtual item" could then be shelved, receive a call number etc appropriately, and therefore show consistently in Koha's "browse shelf" feature. Of course, this implies a database issue: several "virtual items" would correspond to one individual physical "item": any action (loan, return, damage etc) on the latter should propagate to any corresponding virtual items as well. I would very much appreciate receiving your feedback on my thoughts above. Best regards, Giuseppe.

1 1

Koha 17.05.00 and 16.05.14 packages; repository reorganized
by Mirko Tietgen 14 Jun '17

14 Jun '17

1. Koha 17.05.00 Debian package released 2. Koha 16.05.14 CRITICAL bugfix Debian package released 3. Koha community repository reorganized Hi everybody, 1. Koha 17.05.00 Debian package released The Debian package for Koha 17.05.00 is now available from the Koha community repository. The package is available via the 17.05/stable pocket of the repository, more information below. 2. Koha 16.05.14 Debian package released The Debian package for Koha 16.05.14 is now available from the Koha community repository. The package is available via the 16.05/oldoldstable pocket of the repository, more information below. 3. Koha community repository reorganized The repository has been completely reorganized for the 17.05 release. A lot of obsolete dependency packages have been removed, additional configuration options are available. You have two apt configuration options now: a. Follow by codename (version number) We do not have codenames for Koha versions yet, so we use the version number instead 17.05 16.11 16.05 When a new major version is released, you will stay on the version you have chosen until you change your apt configuration. Example: Release of 17.11 If you have set "17.05" in your apt configuration, you will stay on 17.05 until you change your apt configuration to follow 17.11. To use this option, choose one of the following in your apt configuration: (for 17.05) deb https://debian.koha-community.org/koha 17.05 main (for 16.11) deb https://debian.koha-community.org/koha 16.11 main (for 16.05) deb https://debian.koha-community.org/koha 16.05 main b. Follow by suite This has been the standard way so far: follow Koha stable or oldstable, which change every release cycle. At the moment we have stable 17.05 oldstable 16.11 There is also oldoldstable this release cycle. This suite may not be available in every release cycle. oldoldstable 16.05 When a new major version is released, suite names will change and you will upgrade to a newer branch of Koha with your next update. Example: Release of 17.11 17.11 becomes "stable", 17.05 becomes "oldstable". If you have set "stable" in your apt configuration, you will automatically upgrade from 17.05 to 17.11. To use this option, choose one of the following in your apt configuration: (for 17.05) deb https://debian.koha-community.org/koha stable main (for 16.11) deb https://debian.koha-community.org/koha oldstable main (for 16.05) deb https://debian.koha-community.org/koha oldoldstable main Cheers, Mirko -- Mirko Tietgen mirko(a)abunchofthings.net http://koha.abunchofthings.net http://meinkoha.de

3 5