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

Reminder: General IRC meeting 19 October 2016, 10 UTC
by Jonathan Druart 18 Oct '16

18 Oct '16

Hi all, There is a general IRC meeting scheduled for tomorrow, 19 October, 10 UTC: https://wiki.koha-community.org/wiki/Development_IRC_meeting_19_October_2016 Check your timezone: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Koha+Developers+I… Please make sure to add any topics you want to discuss to the agenda! Hope to see you there, Katrin^WJonathan

1 0

Git Server
by Brendan Gallagher 17 Oct '16

17 Oct '16

Hello All - Our hosting provider has alerted us to a problem on the host for git.koha-community.org. We are in the process of working with them to restore the server. We will let you all know when it has been restored. Thanks, Brendan -- --------------------------------------------------------------------------------------------------------------- Brendan A. Gallagher ByWater Solutions CEO

1 1

Status values in message_queue table
by Graham, Stephen 17 Oct '16

17 Oct '16

Hi All - doing: select status from message_queue group by status gives me 3 values: sent pending failed Are these 3 values the only value "allowed" in this field? Or, putting it another way, if messages are added to the table with a different status value would it cause problems in Koha? The reason I'm asking is: as soon a book with a reservation is returned on our selfcheck machines an email is added to the message_queue table with the status of pending. A lot can happen to this book before it actually gets on the reserve shelf, and may never actually get to the reserve shelf. If the book does go missing, gets hidden etc, the user with the reservation still gets an email telling them that the book is ready to collect (when it's not). To avoid this we are wondering if could stop this email from being sent (we only send out email notices once a day). We could delete the email from the message_queue table - I don't really like deleting stuff - or we could change the status. I guess I could change to "failed", but "cancelled" sounds better. I thinking of writing a bit of code to allow library staff to do this easily from the staff client - could I change the status to "cancelled" or is it better to stay with one of the original three? Cheers, Stephen Stephen Graham Library Technology Consultant Academic Resources Library and Computing Services University of Hertfordshire Hatfield AL10 9AB UK Tel. 01707 286111 Ext: 77751 Email s.graham4(a)herts.ac.uk

3 2

KohaCon17 status ?
by Paul Poulain 14 Oct '16

14 Oct '16

Hi all, Reading the minutes of the previous IRC discussions, I'm not sure that the KohaCon17 has been decided/validated yet. Am I wrong ? I'd like to point that, in Europe, there's a very important conference (ELAG, can be considered as the European Code4lib) that will take place in June 6th-9th (in Athens, Greece) having the KohaCon not set this week seems a good idea ;-) -- Paul Poulain, Associé-gérant / co-owner BibLibre, Services en logiciels libres pour les bibliothèques BibLibre, Open Source software and services for libraries

1 0

Call for News: October 2016 Newsletter
by kohanews 14 Oct '16

14 Oct '16

Fellow Koha users ~ I'm collecting news for the October 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. -- Chad Roseburg Editor, Koha Community Newsletter

1 0

Marseille16 / REST api
by Tomas Cohen Arazi 13 Oct '16

13 Oct '16

During the first couple Hackfest days, Jonathan, Benjamin and I worked on a reference implementation of CRUD code for a REST endpoint, so others can read it, discuss it and use it as a reference for their own developments. We worked on Koha::Cit(y|ies) because it was a really simple class. All our work is now on bug 17428. The main goals/concepts we tried to apply were: * Controller class (Koha::REST::V1::Cities) should be as simple as possible. No business logic on it. All business logic is expected to be put on the Koha::Cit(ies|y) classes. And fully tested. * All verbs/use cases should be covered by tests (t/db_dependent/api/v1/cities.t). We did it, and this file could be used (with little adjustments) as the basis for new endpoint tests. * Heavy use of exceptions. I wouldn't say we heavily use them, but the point is that we pass everything to the business object, and catch exceptions it might raise. Martin pointed out that he would help us further simplify it, making heavier use of the Swagger plugin's facilities. Specially on parameters sanity check. More on this tomorrow! * Koha::Exceptions got per-class files so the exceptions file is more manageable. Bug 17425 introduced Koha/Exceptions/Object.pm, and we propose that's the way to go (Koha/Exceptions.pm still has Virtualshelves-related exceptions that should be moved). * Make use of Try::Tiny for try/catch blocks. On the process we wrote bug 17425, which introduces new exceptions, we added the dependency for Try::Tiny (no worries, it is packaged for Jessie/Ubuntu) and Mirko was here to validate. * Moving business-logic to Koha:: namespace and write REST endpoints on top of that business objects. We picked a simple object, Koha::Patron(s) will be a more complex one of course. This is what Jonathan has been doing, and people willing to write REST endpoints should check with him, and probably help moving business logic into Koha:: namespace. There are several patches on bugzilla introducing endpoints. We will try to contact patch authors to help them make their work match this proposed 'guidelines'. We are sticking to the 'patches speak' approach, so feel free to criticize this implementation, to improve it or even provide a counter-proposal. We are otherwise moving on, trying to get a functional complete REST api ASAP. Thanks! Tomas, Jonathan, Benjamin -- Tomás Cohen Arazi Theke Solutions (https://theke.io <http://theke.io/>) ✆ +54 9351 3513384 GPG: B2F3C15F

3 7

Introduce the use of Grunt or Gulp?
by Owen Leonard 13 Oct '16

13 Oct '16

I would very much like to start using some kind of build tool for front-end assets in Koha. The ones I've encountered are Grunt and Gulp: Grunt: http://gruntjs.com/ Gulp: http://gulpjs.com/ I have some experience with Grunt, and have heard good things about Gulp. Has anyone else used either in their non-Koha projects? Adopting them would introduce a little more complexity to the process of making client-side changes to Koha, and to be honest I'm not sure of the right way to incorporate the tools into our workflow. What I see as the advantages: - Automatic linting, minification, and concatenation of CSS and JS - Potentially, automatic compression of images and contruction of image sprites - Overall performance improvements from the above Disadvantages: A new process to learn for those wanting to contribute front-end modifications. A new set of dependencies for front-end developers (Node.js etc). If there is interest I'd be happy to submit a patch introducing the process to the OPAC as a demonstration. -- Owen -- Web Developer Athens County Public Libraries http://www.myacpl.org

10 22

Trying to generate the package.
by Rodrigo Santellan 11 Oct '16

11 Oct '16

Hi, I'm trying to generate the package to learn how to so can I apply it later. I follow: https://wiki.koha-community.org/wiki/Building_Debian_Packages_-_The_Easy_Way on the kohadevbox (jessie) but when I try to generate the package this message appear: W: /home/vagrant/.pbuilderrc does not exist I have to said that I change he file: build-git-snapshot the line 32 to my $distribution='testing'; because of this warning: dch --force-distribution -D "squeeze-dev" -v "16.05.04git+20161011182826.70be2835" "Building git snapshot." dch warning: Recognised distributions are: unstable, testing, stable, oldstable, experimental, {testing-,stable-,oldstable-,}proposed-updates, {testing,stable,oldstable}-se And the error I have is: vagrant@kohadevbox:kohaclone(origin/local-16.05.X)$ sudo -E ./debian/build-git-snapshot -r ~/debian -v 16.05.04git -d git status --porcelain -unormal git rev-parse --short=8 HEAD dch --force-distribution -D "squeeze-dev" -v "16.05.04git+20161011182826.70be2835" "Building git snapshot." dch warning: Recognised distributions are: unstable, testing, stable, oldstable, experimental, {testing-,stable-,oldstable-,}proposed-updates, {testing,stable,oldstable}-security, wheezy-backports, jessie-backports and UNRELEASED. Using your request anyway. dch -r "Building git snapshot." git archive --format=tar --prefix="koha-16.05.04git+20161011182826.70be2835/" HEAD | gzip -9 > "../koha_16.05.04git+20161011182826.70be2835.tar.gz" pdebuild --buildresult /home/vagrant/debian W: /home/vagrant/.pbuilderrc does not exist dpkg-checkbuilddeps: warning: relation < is deprecated: use << or <= dpkg-buildpackage: warning: using a gain-root-command while being root dpkg-buildpackage: source package koha dpkg-buildpackage: source version 16.05.04git+20161011182826.70be2835 dpkg-buildpackage: source distribution squeeze-dev dpkg-buildpackage: source changed by root <root@kohadevbox> dpkg-source --before-build kohaclone dpkg-source: warning: relation < is deprecated: use << or <= dpkg-checkbuilddeps: warning: relation < is deprecated: use << or <= fakeroot debian/rules clean dh clean --fail-missing --with bash-completion dh_testdir -O--fail-missing dh_auto_clean -O--fail-missing make[1]: Entering directory '/home/vagrant/kohaclone' make[1]: *** No rule to make target '/usr/lib/x86_64-linux-gnu/perl/5.22/Config.pm', needed by 'Makefile'. Stop. make[1]: Leaving directory '/home/vagrant/kohaclone' dh_auto_clean: make -j1 distclean returned exit code 2 Command 'pdebuild --buildresult /home/vagrant/debian' returns an error (512) debian/rules:9: recipe for target 'clean' failed make: *** [clean] Error 2 dpkg-buildpackage: error: fakeroot debian/rules clean gave error exit status 2 Where can I look for information about this? Regards

1 0

Pending 16.11 Release Dates
by Kyle Hall 11 Oct '16

11 Oct '16

Hey All, It's that time of the year again! Here is the timeline Brendan and I have mapped out for the pending Koha 16.11 release: Nov 1st - Feature Slush For the uninitiated, the slush means that no new enhancements, only bug fixes, will be pushed to master until some time after the 16.11 release. During the slush phase bug fixes may include template string changes that will require translation. Nov 3 - 1st Draft of release notes The 1st draft of the 16.12 release notes will be published and made available so corrections may be submitted. Nov 10 - 2nd Draft of release notes Nov 15th - Feature Freeze >From November 15 until the release date, only bug fixes without string changes will be pushed to master. Nov 17 - Final Draft of release notes Nov 22 - 16.12 Release Day! Kyle http://www.kylehall.info ByWater Solutions ( http://bywatersolutions.com )

2 2

Sandboxes are up
by Fridolin SOMERS 11 Oct '16

11 Oct '16

Hie, Since a few weeks our sandboxes are down. We have created a new system with Ubuntu Xenial machines. The virtualisation LXD allows unlimited cloning. See https://wiki.koha-community.org/wiki/Sandboxes#BibLibre Best regards, -- Fridolin SOMERS Biblibre - Pôles support et système fridolin.somers(a)biblibre.com

1 1