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

Dashboard
by Marcel de Rooy 25 May '18

25 May '18

I like the Koha dashboard, but I would not mind if someone else (...) removed the patch status changes box and the patches pushed for release 18.05 list. (The last one is not updated in a longer time.) Removing should not be that hard for the maintainer himself ? I am focusing on Koha in the meantime :) Thanks, Marcel

1 0

Replace Catmandu indexing code with pure perl and eventually drop Catmandu as a Koha dependency
by David Gustafsson 25 May '18

25 May '18

Hi all! I have been working on replacing Catmandu depandant indexing code with a simpler and faster Koha-specific one using the Search::Elasticsearch package (which Catmandu uses internally): https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19893 Some of the benefits would be: 1) Increased indexing performance (about twice as fast, six times as fast if comparing time spent in update_index()), due to more efficient json-conversion and fewer Elasticsearch requests. 2) With Catmandu indexing speed decreases as more mappings are added, with the alternative algorithm indexing is kept more or less constant no matter how many mappings you add. 3) Neglectable indexing start-up time. Especially noticeable when indexing a single document. For example we have an issue with the book drop machine, each return taking a couple of seconds because of the Catmandu start-up overhead (or when saving biblios in staff client). 4) More transparent code and less complexity compared with Catmandu (admittedly partly subjective statement) should lead to improved maintainability and increased stability. 5) No need for new developers to learn the Fix language 6) Closer to the metal so easier to perform even more Koha-specific optimizations and customizations which might not be feasible with Catmandu in tthe way The proposed patch only addresses the indexing logic but the remaining Catmandu-dependant code (mainly for searching) should be pretty trivial to replace with Search::Elasticsearch implementation which can be done as a next step. Would be wonderful if this could be raised for discussion at the next developers meeting. Best regards David Gustafsson

2 6

Koha 17.05.12 release
by Fridolin SOMERS 24 May '18

24 May '18

The Koha community is proud to announce the release of Koha 17.05.12. This is a maintenance release containing 2 security patches. The full release notes are available at https://koha-community.org/koha-17-05-12-release/ Regards, -- Fridolin SOMERS <fridolin.somers(a)biblibre.com> BibLibre, France - software and system maintainer

1 0

Can we do away with items.onloan?
by Barton Chittenden 21 May '18

21 May '18

One of my first trouble-shooting experiences with Koha involved a report of search results where an item was showing as 'available', but the detail showed it checked out to a patron. Some helpful bywaterian pointed me to items.onloan, and issues.date_due, and showed me that they didn't match. A database update and a zebra re-index later, and the problem was solved. We've never figured out the circumstances under which these get out of sync... we always find out about it after the fact. I'm sure that we could find everywhere that they're written, and put the writes to the items table and the issues table into a single transaction... but wouldn't it be better to simply add the due date to the marcxml record from the issues table at the time of indexing and remove the possibility of error entirely? It's a paper-cut of a problem, but it's always bothered me. --Barton

4 4

Release candidate of Koha 18.05.00 available
by Mirko Tietgen 18 May '18

18 May '18

Good news everyone, the first release candidate (RC1) of the upcoming feature release Koha 18.05.00 is now available from the UNSTABLE repository: koha-common_18.05.00~~rc1-2 !!! This is a test version and NOT considered ready for use in production !!! If you test the RC1, please report any bugs you may find at the community bug tracker.[1] Please refer to the Koha wiki for information about the repository configuration.[2] Information for developers: The version number is lower than the versions in the NIGHTLY repository, which have been bumped to koha-common_18.05.00~git[…]. If you have the NIGHTLY repository in your apt configuraton and want to test the RC1 of 18.05.00, you should disable the NIGHTLY repository. Cheers, Mirko [1] https://bugs.koha-community.org/bugzilla3/ [2] https://wiki.koha-community.org/wiki/Debian#Follow_a_suite:_stable.2C_oldst… -- Mirko Tietgen mirko(a)abunchofthings.net http://koha.abunchofthings.net

2 2

accountlines.dispute
by Tomas Cohen Arazi 18 May '18

18 May '18

I've filed bug 20777 [1] removing that column. If you are familiar with that pre-3.0 column and its usage, please speak up on the bug! Thanks! [1] https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20777 -- Tomás Cohen Arazi Theke Solutions (https://theke.io <http://theke.io/>) ✆ +54 9351 3513384 GPG: B2F3C15F

2 1

Call for News: May 2018 Newsletter
by kohanews 16 May '18

16 May '18

I'm collecting news for the May 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

Turn Koha into a Mojolicious application
by Julian Maurice 16 May '18

16 May '18

Hi all, I've been playing with Mojolicious recently and I thought it would be great if Koha was a Mojolicious application (like the REST API already is). Some pros: - Easier deployment - Testable CGI scripts (Test::Mojo) - All Mojolicious features (routing, commands, plugins, ...) - Koha already uses Mojolicious, so there's no new dependency. I wrote a POC here : https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20582 I'd like to gather opinions on it, and for that I want to try something new. I created a "Koha" group on framavox.org, an instance of Loomio (a free software designed to make decisions). In this group there is a discussion named "Bug 20582 - Turn Koha into a Mojolicious application" where you can add comments. And in this discussion there is a proposal where you can vote (Agree, Abstain, Disagree, Block) and add a reason for your vote Group link : https://framavox.org/g/iAKeRC8Q/koha Discussion link : https://framavox.org/d/tTGf0Bzd/bug-20582-turn-koha-into-a-mojolicious-appl… To keep things clean, please - use the framavox group to discuss about the idea of turning Koha into a Mojolicious app (not the implementation) - use the bug report to discuss about the implementation - reply to this mail for anything else (feedback about framavox.org for instance) Thanks -- Julian Maurice <julian.maurice(a)biblibre.com> BibLibre

1 2

HTTP::OAI
by Tomas Cohen Arazi 15 May '18

15 May '18

Hi, I've successfully built master packages with my patch (forcing HTTP::OAI@3.x dependency)[1]. They also install with no issue in Stretch. Here's what you need to test yourself: https://cloud.theke.io/s/AyfTWpXt6R87epe Basically download everything somewhere and: $ vagrant up $ vagrant ssh v$ wget -q -O- https://debian.koha-community.org/koha/gpg.asc | sudo apt-key add - v$ echo 'deb http://debian.koha-community.org/koha unstable main' | sudo tee /etc/apt/sources.list.d/koha.list v$ apt update v$ sudo dpkg -i /vagrant/libhttp-*.deb v$ sudo apt -f install v$ sudo dpkg -i /vagrant/koha-deps*.deb v$ sudo apt -f install v$ sudo dpkg -i /vagrant/koha-perldeps*.deb v$ sudo apt -f install v$ sudo dpkg -i /vagrant/koha-common*.deb v$ sudo apt -f install Voila. [1] https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20437 -- Tomás Cohen Arazi Theke Solutions (https://theke.io <http://theke.io/>) ✆ +54 9351 3513384 GPG: B2F3C15F

3 7

Documentation Sprint!
by Lee Jamison 15 May '18

15 May '18

Hello all, as you know the May 22nd release is fast approaching so to prepare for the release I'll be spearheading a documentation sprint. The order of priority (from top priority down) is as follows: *- New features* *- Enhancements* *- Everything else* Any questions or comments can be directed to me and I'll be happy to address them Thank you! -- Lee Jamison Automated Library Technician Marywood University 570-961-4586 ldjamison(a)marywood.edu

1 0