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

Koha Community Newsletter: August 2017
by kohanews 29 Aug '17

29 Aug '17

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

Circulation Rules RFC - new proposed frontend
by Jesse 29 Aug '17

29 Aug '17

I've updated the proposed UI at https://wiki.koha-community.org/wiki/Circulation_Rules_Interface_and_Backen… . Please see the notes below the screenshots, but the essential idea is a hybrid of the old and (formerly proposed) new UIs, with a table that grows as needed. Comments appreciated. If you wish to try out this very early prototype, please see https://github.com/pianohacker/koha, branch bz15522 (or visit https://github.com/pianohacker/koha/tree/bz15522) The page in question is admin/policy.pl, and the relevant code is at .../prog/js/src/admin/policy.js . Background: the core idea of this new circulation rules project is to allow librarians to specify only those rules that they need to be different, and let the rest inherit from more general settings. This should result in a more pleasant workflow, especially for large libraries, and a UI that no longer scrolls off the side of your monitor. -- Jesse Weaver

1 0

Is the "sms" directory just garbage?
by David Cook 26 Aug '17

26 Aug '17

Hi all, I'm just going through the Koha codebase and making sure everything compiles, and I stumbled upon sms/sms_listen_windows_start.pl: http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=sms/sms_listen_win dows_start.pl;h=a94dc9589d112c2ae70994c61f91570b68375f8f;hb=HEAD It looks like it's a script for Windows, which the community doesn't remotely support, plus the code doesn't really make any sense. ./sms/sms_listen.pl also looks like garbage to me. So does ./sms/sms.pl. Everyone reckon it would be safe to remove both of these scripts from Koha? Looks like they're about 7+ years old. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595

3 2

[SIGNED_OFF] labels
by Marcel de Rooy 26 Aug '17

26 Aug '17

Hi all, I would favor stopping the use of adding [SIGNED_OFF] labels to patches when it is not strictly needed (which normally is the case). Only when (exceptionally) a few patches are signed and a few are not on one report, I could see its use. At this moment they need to be obsoleted manually with git bz. Can we stop adding them ? Marcel

6 5

Putting Koha into Docker...
by Mark Tompsett 25 Aug '17

25 Aug '17

Greetings, I’ve been tasked to dockerize our Koha installation, and I noticed https://github.com/digibib/koha-docker I also noticed it said “www.koha.org” on https://github.com/digibib/koha-docker/wiki even though the code says, “echo "deb http://debian.koha-community.org/koha stable main" > /etc/apt/sources.list.d/koha.list” on https://github.com/digibib/koha-docker/blob/master/Dockerfile So, I’m confused if this is usable for production and it is is Koha or LibLime. Feedback, thoughts much appreciated. GPML, Mark Tompsett

6 5

REST api / pagination
by Tomas Cohen Arazi 25 Aug '17

25 Aug '17

Hi there, I'm currently implementing a couple endpoints for acquisitions-related stuff and also QAing existing patches introducing endpoints. One of the things that need to be done (which I did for my own endpoint for vendors / bug 18120) is migrating them to Mojolicious::Plugin::OpenAPI instead of (the deprecated) Mojolicious::Plugin::Swagger2. I noticed there's lack of a generic way to deal with pagination. There are a couple options we could consider, but I would like to hear the opinion of UI people, which are the ones that will take advantage or suffer what we do on the backend :-D a) GET /patrons?page=1&per_page=3 => [ {borrower1}, {borrower2}, {borrower3} ] b) GET /patrons?offset=0&limit=3 => [ {borrower1}, {borrower2}, {borrower3} ] Lari proposed another one, which tackles an issue we could have on the UI (knowing the total, calculating pages, etc): c) GET /patrons?page=1&per_page=3 { total: 50000, results: [ {borrower1}, {borrower2}, {borrower3} ] } (c) has the problem that it would mean we need to change the current resposes for list operations on the already implemented endpoints. I'm not sure at this point we would need to shift api version (v2?), I would vote against, but here we have the chance to hear people using the API. Looking forward to your comments as my current dev work completion depends on it :-D -- Tomás Cohen Arazi Theke Solutions (https://theke.io <http://theke.io/>) ✆ +54 9351 3513384 GPG: B2F3C15F

5 8

Koha Developers IRC meeting reminder - Today August 23th, 14 UTC
by Jonathan Druart 23 Aug '17

23 Aug '17

Hi, We have a Developers meeting in IRC scheduled for today at 14 UTC (in ~1hour) Local time/date conversion here: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Koha+Developers+I… The agenda is here: https://wiki.koha-community.org/wiki/Development_IRC_meeting_23_August_2017 Jonathan

1 0

What's on in koha-devel #14
by Jonathan Druart 21 Aug '17

21 Aug '17

Hello librarians and developers, The what's on in koha-devel #14 is available on the Koha website: https://koha-community.org/whats-on-in-koha-devel-14 Regards, Jonathan

12 19

Call for News: August 2017 Newsletter
by kohanews 16 Aug '17

16 Aug '17

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

Indic language conjunct clusters printed incorrectly in spine label
by Indranil Das Gupta 12 Aug '17

12 Aug '17

[CROSS-POSTING] Hi all, This is w.r.t. https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19084 (there is a screenshot on the bug showing the problem) This problem seems to be present for most Indian languages whenever they have conjunct clusters in their call numbers (depicted as grapheme clusters in an unicoded string). To describe the problem simply - the order of chars rendered is incorrect in the output. For example the string - "শেখর" is represented by the following code points - \x{09B6}\x{09C7}\x{0996}\x{09B0}. Now here is the catch: \x{09B6} represents the bengali letter SHA, whereas \x{09C7} represents the bengali vowel sign E; however in the correct linguistic visual presentation, the vowel sign E sits before the SHA, which is not how the codepoints are arranged in the unicode string. I looked around PDF::Reuse, Text::PDF::TTFont etc modules, what seems to me to be the root of this problem is the unpacku() method which is pushing the unicode characters into an array in order to introduce them into the PDF content stream with the correct font information. However, being pushed in in that order, I think may be the cause of this problem, which would make this an upstream issue rather than a Koha bug. Your inputs / feedback on this would be greatly appreciated. cheers indranil PS. I am aware of the "CLOSED WONTFIX" status of bug id 2246 ;-) -- Indranil Das Gupta L2C2 Technologies Phone : +91-98300-20971 Blog : http://blog.l2c2.co.in IRC : indradg on irc://irc.freenode.net Twitter : indradg

1 0