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

Suggestion: create a deprecated() function in Koha.
by Barton Chittenden 25 Jun '18

25 Jun '18

It would be useful for Koha to have a 'Deprecated' function, which would send a warning about the caller() function and the version of Koha where the function will be deprecated, and what it will be replaced by... so let's say that C4::Adequate::DoEET() is being replaced by Koha::Awesome->sauce(). in Koha 18.11. In versions of koha prior to 18.11, we add a call to deprecated( "18.11", "Koha::Awesome->sauce()"); at the beginning of C4::Adequate::DoEET(). Then, when C4::Adequate::DoEET() is called, this would generate the following message in the logs: "C4::Adequate::DoEET is deprecated and will be removed in Koha 18.11. It will be replaced by Koha::Awesome->sauce()." This would allow plugin authors to know that they will need to patch their plugins before they break on upgrade. This is a bare-bones implementation of deprecated(): sub deprecated { my ( $version, $replacement ) = @_; my ( $package, $filename, $line, $subroutine, $hasargs, $wantarray, $evaltext, $is_require, $hints, $bitmask, $hinthash ) = caller(1); warn( "${subroutine} is deprecated and will be removed" . " in Koha version $version." . defined( $replacement ) ? " It will be replaced by ${replacement}." : "" ); }

3 2

Koha 17.11.07 release
by Fridolin SOMERS 25 Jun '18

25 Jun '18

The Koha community is proud to announce the release of Koha 17.11.07. This is a maintenance release. The full release notes are available at https://koha-community.org/koha-17-11-07-release/ 17.11.x is my baby now ;) Regards, -- Fridolin SOMERS <fridolin.somers(a)biblibre.com> BibLibre, France - software and system maintainer

1 0

Koha 18.05.01 released
by Renvoize, Martin 25 Jun '18

25 Jun '18

The Koha community is proud to announce the release of 18.05.01. This is a maintenance release and contains many bugfixes and enhancements. As always you can download the release now and the packages will follow shortly: http://download.koha-community.org This is my first release as the 18.05.XX release maintainer, thank you very much to everyone involved in this release. *Martin Renvoize* Development Manager *T:* +44 (0) 1483 378728 *F:* +44 (0) 800 756 6384 *E:* martin.renvoize(a)ptfs-europe.com www.ptfs-europe.com <https://www.ptfs-europe.com> Registered in the United Kingdom No. 06416372 VAT Reg No. 925 7211 30 The information contained in this email message may be privileged, confidential and protected from disclosure. If you are not the intended recipient, any dissemination, distribution or copying is strictly prohibited. If you think that you have received this email message in error, please email the sender at info(a)ptfs-europe.com

2 1

Staff/OPAC ISBD views and subfield visibility
by Andreas Roussos 25 Jun '18

25 Jun '18

Dear Developers, If you: 1) edit the ISBD and OPACISBD system preferences so that they contain the following code: #453| - translated as: |<a href="/cgi-bin/koha/catalogue/ detail.pl?biblionumber={4530}">{453t}</a> {(453d)}| #454| - translation of: |<a href="/cgi-bin/koha/catalogue/ detail.pl?biblionumber={4540}">{454t}</a> {(454d)}| 2) set the visibility of (UNIMARC) fields 453$0 and 454$0 to 'hidden' in the OPAC ...then the generated links will work fine in the Staff client but will be broken in the OPAC (i.e. the URL will not include the biblionumber contained in subfield 0 of fields 453/454). I've tracked this down to ISBDdetail.pl and opac-ISBDdetail.pl calling the GetISBDView subroutine, which (for some reason) excludes subfields that are hidden in the OPAC: https://github.com/Koha-Community/Koha/blob/master/C4/Biblio.pm#L773-L776 https://github.com/Koha-Community/Koha/blob/master/C4/Biblio.pm#L812-L815 What is the reasoning behind this? In other words, why is _OPAC_ subfield visibility taken into account when displaying the OPAC ISBD view (whereas visibility in Staff is not considered)? If anything, it is more likely to have subfield 0 hidden in OPAC, while visible in Staff, so one would expect the opposite logic. Thanks in advance for your time. Kind regards, Andreas Roussos

3 5

Add "cc" and "bcc" fields to message_queue
by David Cook 25 Jun '18

25 Jun '18

Hi all, What do people think about adding "cc" and "bcc" fields to the message_queue? We already have NoticeBCC, but in multi-branch environments, it can be good for BCCs to go to particular branch email addresses rather than 1 global email address. One use case is for the member_expiry.pl cronjob. It would be nice for BCCs or CCs to go to the branch where the patron/member is expiring. After looking through the code, it doesn't really seem like we have anything to handle this at the moment. We have some CCs and BCCs peppered around but all for emails that are sent on the fly. Nothing for queued messages. Thoughts? David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595

2 2

Preserve white spaces of Control Fields
by Stefano Bargioni 22 Jun '18

22 Jun '18

Hi, I added a new entry in the jQuery Library: <https://wiki.koha-community.org/wiki/JQuery_Library#Preserve_white_spaces_o…> The purpose is to simplify the analysis of control fields 00x, especially 000, 006, 007, 008. They are shown preserving white spaces, each char in a box, and its position is shown on mouse hover. You can test it opening a bib or auth record in MARC view, and pasting the code in the browser console. Any comment is appreciated. Stefano

1 0

Why we do not push the ACCTDETAILS email via message queue?
by Indranil Das Gupta 20 Jun '18

20 Jun '18

Hi all, I was wondering why we do not push the ACCTDETAILS email via the message queue. Is it just one of those cases of "as things have always been done" OR there is a reason that I'm missing out? cheers indranil. Indranil Das Gupta L2C2 Technologies Phone : +91-98300-20971 Blog : http://blog.l2c2.co.in IRC : indradg on irc://irc.freenode.net Twitter : indradg

9 13

Partnership between BibLibre and Orex
by Paul Poulain 19 Jun '18

19 Jun '18

Hello Koha, Hugo & I are happy and proud to announce our partnership to increase Koha deployment in Spain and other Spanish speaking countries : https://www.biblibre.com/en/blog/orex-and-biblibre-join-their-strength-to-p… -- 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

Should the first 3 digits of cn_sort be sorted for dewey decimal?
by Barton Chittenden 19 Jun '18

19 Jun '18

The documentation for GetClassSortKey says * Concatenates class and item part. * Converts to uppercase. * Removes leading and trailing whitespace and '/' * Separates alphabetic prefix from the rest of the call number * Splits into tokens on whitespaces and periods. * Leaves first digit group as is. ... this means that callnumbers 9.1 => 9_100000000000000 80.1 => 80_100000000000000 700.1 => 700_100000000000000 when sorted ascending by cn_sort 700.1 => 700_100000000000000 80.1 => 80_100000000000000 9.1 => 9_100000000000000 Shouldn't these be zero padded to 3 digits, so that they sort as follows? 009_100000000000000 080_100000000000000 700_100000000000000

2 5

Cronjob to run plugin cronjobs?
by Nick Clemens 18 Jun '18

18 Jun '18

Just an idea I had an bounced off Kyle, he suggested sending it out for feedback, let us knwo what you think: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20897 -- Nick Clemens Sonic Screwdriver (Development Support) ByWater Solutions IRC: kidclamp

4 3