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

Elastic search demo interface
by BOUIS Sonia 05 Jun '17

05 Jun '17

Hello everybody, First of all, congratulations Kyle for the 17.05 koha release ! I'm wondering if someone have planned to propose an interface demo (staff and public) on Koha 17.05 with Elastic Search turn on. It would be great :) It would help librarians that have heard about Elastic Search for one year to make it more real and to evaluate if it could be relevant for them to switch from zebra to elastic search. And I have 2 more questions about elastic search : - Is it compatible with unimarc ? - Is it usable with non-latin character ? Thanks in advance, 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

3 3

Clean HTML validations....
by Mark Tompsett 05 Jun '17

05 Jun '17

Greetings, I noticed a couple bugs fix HTML on a couple things, but not all. In fact, I hit a stall on one bug, so I just removed myself from it. However, the problem still haunts me. Is there a community acceptable way to fix HTML validation of something like: <option value=""></option>? This happens in many places, and when someone fixes a missing </form> or </div> tag, my tendency is to see what other HTML creeps would be easy. Some are, but this one is not. Possibilities: <option value=””> </option> <option value=””>Enter something meaningful</option> (where the phrase is descriptive of what is expected, or what nothing really means in this case) Thoughts, feedback, updated coding guidelines? GPML, Mark Tompsett

2 1

git.k-c.org not using HTTPS
by Tomas Cohen Arazi 05 Jun '17

05 Jun '17

Hi, I think we should move it to using HTTPS. I can help if needed. Regards -- Tomás Cohen Arazi Theke Solutions (https://theke.io <http://theke.io/>) ✆ +54 9351 3513384 GPG: B2F3C15F

2 1

Koha 17.05.00 released!
by Kyle Hall 01 Jun '17

01 Jun '17

Hello all! It is my honor to announce the release of Koha 17.05.00! Thanks you to everyone who contributed time and effort making this the best version of Koha yet! The release notes can be found on the Koha Community website: https://koha-community.org/koha-17-05-released/ Kyle http://www.kylehall.info ByWater Solutions ( http://bywatersolutions.com ) Meadville Public Library ( http://www.meadvillelibrary.org ) Crawford County Federated Library System ( http://www.ccfls.org )

5 4

Koha Community Newsletter: May 2017
by kohanews 01 Jun '17

01 Jun '17

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

What's on in koha-devel #13
by Jonathan Druart 31 May '17

31 May '17

Hello librarians and developers, I have a lot of things to tell you :) First, Koha 17.05 is out! I would like to congratulate Kyle and all the release team! It includes 7 new features and many enhancements and bug fixes. You can find the release notes on the website : https://koha-community.org/koha-17-05-released/ I would like to highlight a feature that I am talking about for months now, Hea version 2 = Hea v2 = The development is now in the last version of 3.22.x and has been backported to all supported releases. So if you are using 3.22, 16.05 or 16.11 you should upgrade to (at least) 3.22.21, 16.05.13 or 16.11.08 and share with us information about your libraries! See the global map to see all libraries https://hea.koha-community.org/libraries-on-a-map (just a few at the moment, we are waiting for you!) See an example of the detail of a Koha installation with several libraries: https://hea.koha-community.org/libraries/425 You can tune and choose the information to share with the community on a new administration page. You can find it under "Administration › Usage statistics". I really hope to see a whole map full of libraries in the next weeks :) = 17.11 development has started = 17.05 is out, that means the next development cycle has just started. I have been elected to take the lead as Release Manager for this one. I announced in my RM proposal ( https://wiki.koha-community.org/wiki/Proposal_for_RM_17.11_joubu) that I wanted to integrate more people in the team. To this end, I needed to know 1) who is willing to dedicate time for the next 6 months, 2) what are the needs of everybody and 3) coordinate and assign tasks to ease and speed the integration of patches. As I am not a politician I will try and do what I said. You may have noticed that I already started, here are the different actions that have already been triggered: == Contact people == I have sent an email to 1) the support companies, 2) the contributors and 3) the general list ( https://lists.katipo.co.nz/pipermail/koha/2017-May/048066.html) to ask them/you filling a form ( https://framaforms.org/ready-to-help-the-koha-community-1493918217) to collect ideas/needs on what we could work on the next release and who is going to help. I have received 40 answers so far, for a total of 62 persons and 852h per months. 29 support companies, 6 libraries and 5 volunteers. That's a good start, but quite a lot of (active) support companies did not answer yet. If you are not an employee of a support company, you can still fill the form! == A new tool - kanban == To coordinate and assign tasks I suggest a new tool that is quite easy to use: a kanban. You can find it at https://tree.taiga.io/project/joubu-koha-rm-1711/kanban There is a wiki page to explain a bit how it works: https://tree.taiga.io/project/joubu-koha-rm-1711/wiki/home It will be a very important tool for the next release, so if you are involved directly or indirectly in the Koha community (translation, documentation, write or test patches, etc.) you should join us if it is not done yet. For instance we are currently reworking our entry points on the wiki to welcome new contributors, there is a task on the kanban subdivided in several tasks: https://tree.taiga.io/project/joubu-koha-rm-1711/us/21 == Welcoming new contributors, a priority == As I just said previously we are focussing on welcoming new contributors, if you are new and willing to help us it's certainly the best moment to do it. You should just wait a bit to let us rebuilt our wiki and give you the desire to help! If you always wanted to dive into the Koha code, we are writing a tutorial to help and guide you throughout the different steps of a patch: write a patch, attach it to the bug tracker, sign it off, etc. It is called koha-howto and you can find more information about it on the kanban. The official announcement should arrive soon. = Collaborative what's on = Heh yeah, I am sure some of you are sick of my English grammar and my obsession for the wiki syntax in my emails :) Since I guess other developers would like to share what they did over the previous month I have created a pad ( https://annuel2.framapad.org/p/What_s_on_in_koha-devel) where everybody can contribute to the next "what's on in koha-devel" email. Feel free to add stuffs to this page when you want to highlight something. = Push refactoring patches soon = I have a lot of refactoring patches that are in the queue for too long. I really would like to see a collective effort done on them. They will lead to cleaner and more flexible and maintainable code. We have seen lot of bug recently that would have been avoided with them. See the kanban and filter on the "Refactoring" Epic to see what must be done quickly. Do not forget the IRC meetings! If you want to tell us something or highlight a problem, start a discussion, it is the place to do it (do not forget to add the topic on the agenda!) The next general IRC meeting is on June 7th at 13 UTC. https://wiki.koha-community.org/wiki/General_IRC_meeting_7_June_2017 The next dev IRC meeting is on June 14 at 21 UTC https://wiki.koha-community.org/wiki/Development_IRC_meeting_14_June_2017 Cheers, Jonathan

1 0

Koha 16.05.13 release
by Mason James 30 May '17

30 May '17

The Koha community is proud to announce the release of Koha 16.05.13 This is a maintenance release and includes 36 bugfixes, and Hea2 :0) https://hea.koha-community.org/ The full release notes are available at https://koha-community.org/koha-16.05.13-release/ Packages will be available soon. Mason

2 2

Koha 17.05 Release Delay
by Kyle Hall 28 May '17

28 May '17

Hello All, As some of you may have heard at the last IRC meeting, I'm in the middle of moving into a new home. This has delayed the release of 17.05 a bit. I hope to have it out the door sometime tonight or tomorrow ( as soon as I've got internet access again ). Sorry for the delay! Kyle http://www.kylehall.info ByWater Solutions ( http://bywatersolutions.com ) Meadville Public Library ( http://www.meadvillelibrary.org ) Crawford County Federated Library System ( http://www.ccfls.org )

1 0

Expected behaviod when printing serials - add reserve?
by Jonathan Druart 25 May '17

25 May '17

Hi devs, I found an obvious bug in serials/routing-preview.pl. If the script is called with ok=1 (hum... yes...), the script will add or modify a hold placed on the bibliographic records existing in the routing list. So from /serials/serials-collection.pl?subscriptionid=1, click on "Print list" you get a pop-up with a print and close button. When the pop-up is generated, we already have the ok=1 and the go through: 66: my ($count2,@bibitems) = GetBiblioItemByBiblioNumber($biblio); Then later: 96 AddReserve($branch,$routing->{borrowernumber},$biblio,\@bibitems,$routing->{ranking}, undef, undef, $notes,$title); The problem is that GetBiblioItemByBiblioNumber will always return only 1 value (for obvious reasons) and @bibitems will always be empty => reserve is placed at bib level The thing is that this bug exists for ages (at least 2006, maybe always). What is the expected behaviour? No need to tell you that I was going to kick GetBiblioItemByBiblioNumber when I found that bug. Cheers, Jonathan

3 2

Re: [Koha-devel] [Koha] NCIP project
by Magnus Enger 24 May '17

24 May '17

On 19 May 2017 at 09:07, vikram zadgaonkar <vikramczadgaonkar(a)gmail.com> wrote: > We are working on NCIP server integration with koha.We are looking for > support for the same. > > Currently, ncip framework (server and responses etc) appears to be working. > However, data from koha db is not being picked up. There appears to be some > communication error between the koha library (C4) and ncip server's modules. Are you using the NCIPServer created by Chris Cormack/Catalyst and later forked/developed by several people, including ByWater and myself? If so: How are you running it? I run it something like this: $ sudo KOHA_CONF=/etc/koha/sites/koha/koha-conf.xml perl -I/home/magnus/kohaclone/ bin/ncip_dancing.pl --port 80 KOHA_CONF=/etc/koha/sites/koha/koha-conf.xml is the path to the koha-conf.xml of the Koha instance that NCIPServer should be talking to. -I/home/magnus/kohaclone/ is the path to where the C4 and Koha folders are. This is how NCIPServer knows where to find the C4:: and Koha:: modules it needs. Hope that helps, Magnus Libriotech

1 0