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

Koha 17.05.08 release
by Fridolin SOMERS 25 Jan '18

25 Jan '18

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

1 0

a few koha questions
by Johan Seyfferdt 25 Jan '18

25 Jan '18

Hello, we started to use Koha in December and so far very happy with it!!! I just have a few questions: Firstly, all our books we can give out and return except for one book which we gave out in December, and no we cant return it. Ps. I have already ran the fix for auto_increment problem and it didnt work sadly. The Patron has two books, one we can return the other not. Help will be greatly appreciated! If it is somehow possilbe to remove the book while it is out or remove the user, either in the web-interface or in the terminal, it will also be good! Secondly, When our librarian is adding books, she only have a list of pblishers and atohrs, and she was wondering if we can create like a dropdown menus for those fields that she doesnt have to type it every time but simply choose what she wants? Was wondering if someone can help me? Thank you so much and looking forward to hear from you Johan Seyfferdt

2 1

Clarification on build_browser_and_cloud.pl
by Barton Chittenden 23 Jan '18

23 Jan '18

The documentation for misc/cronjobs/build_browser_and_cloud.pl States > *Important* > This preference and cron job should only be used on French systems. (see https://koha-community.org/manual/18.05/en/html/16_cron_jobs.html?highlight… ) The associated OpacBrowser syspref says: Important > > This preference only applies to installations using UNIMARC at this time. ... but the script itself seems to use MARC::File::USMARC exclusively: 13 <http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=misc/cronjobs/bui…> use C4::Koha; 14 <http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=misc/cronjobs/bui…> use C4::Context; 15 <http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=misc/cronjobs/bui…> use C4::Biblio; 16 <http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=misc/cronjobs/bui…> use Date::Calc; 17 <http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=misc/cronjobs/bui…> use Time::HiRes qw(gettimeofday); 18 <http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=misc/cronjobs/bui…> use ZOOM; 19 <http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=misc/cronjobs/bui…> *use MARC::File::USMARC;* 20 <http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=misc/cronjobs/bui…> use Getopt::Long; 21 <http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=misc/cronjobs/bui…> use C4::Log; (see http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=misc/cronjobs/bui… ) The subroutine dewey_french obviously isn't translatable (I've filed bug Bug 20007 - build_browser_and_cloud.pl contains hard-coded text in French for thatt 173 <http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=misc/cronjobs/bui…> sub dewey_french { 174 <http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=misc/cronjobs/bui…> return { 175 <http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=misc/cronjobs/bui…> "0" => "Généralités (Ouvrages généraux (encyclopédies, bibliographies, etc.) et informatique)", 176 <http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=misc/cronjobs/bui…> "00" => "Savoir et communication", 177 <http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=misc/cronjobs/bui…> "001.42" => "Collecte, agencement, analyse des données", 178 <http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=misc/cronjobs/bui…> "003" => "Systémique, systèmes", 179 <http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=misc/cronjobs/bui…> "003.1" => "Identification de système", 180 <http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=misc/cronjobs/bui…> "003.2" => "Prévisions. Futurologie", ... The French text seems to be at cross purposes with MARC::File::USMARC, because French catalogers would probably use UNIMARC; at the same time the use of USMARC contradicts the documentation. Ideally, I'd to get the I18N *and* the marc flavor fixed so that everyone can use this, and I'd like to file bug reports that accurately show what needs to be fixed. Any clarification is welcome. Thanks, --Barton

2 2

Failing prove -v t/Perl.t for qa-test-tools
by Indranil Das Gupta 22 Jan '18

22 Jan '18

Hi Need some clue: I'm on debian 9 - # Looks like you failed 2 tests of 37. Dubious, test returned 2 (wstat 512, 0x200) Failed 2/37 subtests Test Summary Report ------------------- t/Perl.t (Wstat: 512 Tests: 37 Failed: 2) Failed tests: 22-23 Non-zero exit status: 2 Files=1, Tests=37, 8 wallclock secs ( 0.05 usr 0.02 sys + 6.53 cusr 1.10 csys = 7.70 CPU) Result: FAIL What should I look at to make it work? -- Indranil Das Gupta L2C2 Technologies Phone : +91-98300-20971 WWW : http://www.l2c2.co.in Blog : http://blog.l2c2.co.in IRC : indradg on irc://irc.freenode.net Twitter : indradg

2 1

W3C Validator now generates several warnings on OPAC pages
by Indranil Das Gupta 22 Jan '18

22 Jan '18

Hi, I generally use the W3C Validator to make sure that editable OPAC blocks do not contain any non-conforming / invalid HTML5. Earlier, the validator used to complain only about the unapi-server as the only error, which is unavoidable. However, from around Dec 2017, I started noticing that Koha's OPAC pages were triggering several warnings when checked with W3C Validator - about 10 - 14 (or more) warnings that comes up. The warnings are about the type attribute set to "text/javascript" in the <script> element and the type attribute set to "text/css" in the <style> element. I've filed two bugs - 20053 and 20054 for these respectively. What do you all think? Should we fix this OR should be let things be as they are, for now? cheers indranil -- Indranil Das Gupta L2C2 Technologies Phone : +91-98300-20971 WWW : http://www.l2c2.co.in Blog : http://blog.l2c2.co.in IRC : indradg on irc://irc.freenode.net Twitter : indradg

2 1

What is the current kohadocs patch submission workflow
by Indranil Das Gupta 21 Jan '18

21 Jan '18

Hi, Back in the day, when Nicole was managing the Docs, the workflow I knew was thus : clone kohadocs -> add your part -> generate patch -> send it to Nicole Nicole used to merge it and up it went. I was trying to find out what is the present workflow for docs. Any pointers I can read up? thanks indranil -- Indranil Das Gupta L2C2 Technologies Phone : +91-98300-20971 WWW : http://www.l2c2.co.in Blog : http://blog.l2c2.co.in IRC : indradg on irc://irc.freenode.net Twitter : indradg

2 1

Outage for bugs.koha-community.org : Fwd: Linode Support Ticket 9818790 - Critical Maintenance for CPU Vulnerabilities (Meltdown)
by Chris Cormack 20 Jan '18

20 Jan '18

It looks like my linode which hosts bugs.koha-community.org and the dashboard and few other sites will be down for maintenance at 2018-01-19 9:00:00 AM UTC Chris ---------- Forwarded message ---------- From: <support(a)linode.com> Date: 18 January 2018 at 16:39 Subject: Linode Support Ticket 9818790 - Critical Maintenance for CPU Vulnerabilities (Meltdown) To: chris(a)bigballofwax.co.nz Hello, A number of serious security vulnerabilities affecting multiple CPU architectures were recently disclosed by Google's Project Zero team as outlined in our blog post[1]. In order to address the disclosed vulnerabilities, the physical hardware on which your Linode resides will need to undergo maintenance. This is the first of several separate maintenances that will be necessary to fully mitigate these vulnerabilities. This maintenance specifically patches the Meltdown vulnerability; the Spectre vulnerability will be addressed in a future maintenance cycle. We will inform you of these maintenance cycles via additional tickets. Scheduled maintenance windows are listed within the Linode Manager[2] in the time zone that was configured in your user's My Profile[3]. The maintenance window of new Linodes and upgraded, migrated, or resized Linodes will be reflected in the Linode Manager[2], but you may not receive maintenance ticket updates for these changes. The following Linode(s) have now been assigned a maintenance window in which a reboot will occur. Please note that these times can change as a result of the actions mentioned above. At this time your reboot schedule in UTC is as follows: * 2018-01-19 9:00:00 AM UTC - bugs You can prepare your Linode for this maintenance by following our Reboot Survival Guide. By following this guide before your maintenance, you will be able to ensure that services running on your Linode are resumed properly. The Reboot Survival Guide is available here: https://www.linode.com/docs/uptime/reboot-survival-guide These updates affect the underlying infrastructure that your Linode resides on and will not affect the data stored within your Linode. To further protect your Linode, we strongly recommend that you verify it is configured to boot using our latest kernel, which includes patches to help address these vulnerabilities. If your Linode's Configuration Profile is set to utilize our latest kernel, your kernel will automatically be updated upon rebooting. During the maintenance window, your Linode will be cleanly shut down and will be unavailable while we perform the updates. A two-hour window is allocated, however the actual downtime should be much less. After the maintenance has concluded, each Linode will be returned to its last state (running or powered off). We regret the short notice and the downtime required for this maintenance. However, due to the severity of these vulnerabilities, we have no choice but to take swift and immediate action to ensure the safety and security of our customers. For these reasons, we must adhere to a strict timetable, and will not be able to reschedule or defer this maintenance. If you experience any issues following the maintenance, please feel free to reach out to us and we will be happy to assist. --Linode [1] <https://blog.linode.com/2018/01/03/cpu-vulnerabilities-meltdown-spectre> [2] <https://manager.linode.com> [3] <https://manager.linode.com/profile> --- https://manager.linode.com/support/ticket/9818790

3 2

Hackfest, waiting for registrations !
by Paul Poulain 19 Jan '18

19 Jan '18

Hello everyone, I've only a few registrations so far. So reminder : join us in Marseille, March 12-16, for the Koha Hackfest !!! -- 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: January 2017 Newsletter
by kohanews 17 Jan '18

17 Jan '18

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

Koha and Elastic Search used in production ?
by Paul Poulain 11 Jan '18

11 Jan '18

Hello all, Is there someone using Koha with ES in production ? bywater, PTFS-E, Catalyst-NZ, Theke, or any other support company, what's your plan ? BibLibre is planning to invest some effort to work on Koha-ES with UNIMARC in the next months, if there are things to share, we would be more than happy ! -- Paul Poulain, Associé-gérant / co-owner BibLibre, Services en logiciels libres pour les bibliothèques BibLibre, Open Source software and services for libraries

3 2