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

Call for News: November 2018 Newsletter
by kohanews 14 Nov '18

14 Nov '18

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

Freeze and release notes
by Nick Clemens 14 Nov '18

14 Nov '18

Hi All, I went through the queue today and pushed what I could, I think we got a few nice things in today :-) There are some outstanding bugs still, please keep up the great work and help us sort these before release, especially majors/criticals and of course, blockers The release notes are generated rolling now, so first, very rough, draft is already generated: https://gitlab.com/koha-community/koha-release-notes/blob/master/release_no… There are two outstanding enhancements I am considering, 18983 and 20244 for ES - they shouldn't affect Zebra code so I think they are safe and will help uskeep ES momentum Thanks for all your hard work, and your patience. Let me know your feedback and where I can help. -Nick -- Nick Clemens Sonic Screwdriver (Development Support) ByWater Solutions IRC: kidclamp

2 1

Candidate for 18.05 Maintainer
by Nick Clemens 13 Nov '18

13 Nov '18

Hello all! Last week during the Koha developers meeting we voted on roles for the 19.05 release. I will be continuing as the Release Manager, and we have many hands helping along the way ( https://wiki.koha-community.org/wiki/Roles_for_19.05) There is one role left unfilled: 18.05 Release Maintainer (old stable) The release maintainers are responsible for watching the bugs queue from the upcoming release and backporting bugs that affect the version they watch, helping to make sure version in use are kept as stable as possible. It is a good way to learn more about different areas of Koha, to practice your rebasing skills, and to get more involved in the community. There will be many people in the community around to help you out, and we are always looking for new faces to take on these roles. If you are interested please add your name to the wiki page above and we will be voting tomorrow to accept candidates if we have one in place. If you have any questions you can ask the list or message me here or in IRC. Thanks! -Nick -- Nick Clemens Sonic Screwdriver (Development Support) ByWater Solutions IRC: kidclamp

1 0

Freeze/Notes draft
by Nick Clemens 09 Nov '18

09 Nov '18

Hello all, I have hit a multitude of issues today with my VMs and testing and did not realize I was traveling tomorrow when I first set dates for release. I plan to extend the freeze through Monday so that things in the queue (and things I commented today) have some time to get fixed. I will test everything I can today to provide feedback and do the final push on Monday. Thank you for your patience. -Nick -- Nick Clemens Sonic Screwdriver (Development Support) ByWater Solutions IRC: kidclamp

2 2

Documentation for KohaTable() javascript function
by David Cook 02 Nov '18

02 Nov '18

Hi all, Does anyone know where there is any documentation for using the KohaTable() javascript function? I'm muddling through, but it would be great if there was something in at least https://wiki.koha-community.org/wiki/Coding_Guidelines. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595

2 2

Handling for items lost in transit
by Renvoize, Martin 01 Nov '18

01 Nov '18

Hi all, I'm seeking some thoughts regarding 'Bug 21732 - If an item is marked as lost, any outstanding transfers should be cancelled <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21732>'. Currently, there is no thought given to transfers when an item is marked as lost, an as such you may have lost items in the transfers queue. This bug aims to solve this by triggering a cancellation of the transfer at the point an item is marked as lost. We have a few questions: 1) Should this be treated as an enhancement or a bug (If it's an enhancement then we would enable/disable it's functionality based upon a system preference. If it's a bug (as I advocate), then it would be always enabled and no system preference would be added) 2) If the items is 'in transit' where should the items holding library be set to when it is marked as lost (the from or to library). 3) If we consider this a bug, should we add handling for cleaning up the transfers table at upgrade time for any lost items. Many thanks for your help, *Martin Renvoize* <https://www.ptfs-europe.com> Development Team Manager *Phone:* +44 (0) 1483 378728 *Mobile:* +44 (0) 7725 985 636 *Email:* martin.renvoize(a)ptfs-europe.com *Fax:* +44 (0) 800 756 6384 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

1 0

Koha Community Newsletter: October 2018
by kohanews 01 Nov '18

01 Nov '18

The Koha Community Newsletter for October 2018 is here: https://koha-community.org/koha-community-newsletter-september-2018/ Many thanks to the folks ( and poultry <http://avengingchicken.online/kohacon2018/> ) who submitted articles and news to this month's newsletter. Please feel free to email me with any corrections or suggestions. -- Chad Roseburg Editor, Koha Community Newsletter

2 2

Bug 15395: Internationalization, plural forms, context and more
by Julian Maurice 30 Oct '18

30 Oct '18

Hi all, This bug has been signed off more than a year ago but it is still not Passed QA. It seems that not everyone agree on it. It should probably be discussed during an IRC meeting, but in the meantime, I wrote a wiki page [1] to better explain what it is supposed to do and created a thread on framavox [2] to gather opinions. If you have some time, I would really appreciate feedback on this feature. Thanks. [1] https://wiki.koha-community.org/wiki/Internationalization,_plural_forms,_co… [2] https://framavox.org/d/2juWqIMz/internationalization-plural-forms-context-a… PS: framavox.org is a free software (Loomio) hosted by a French association (Framasoft) promoting free software. It only requires an e-mail address to create an account. -- Julian Maurice <julian.maurice(a)biblibre.com> BibLibre

1 0

wrong url/uri filters
by Jonathan Druart 30 Oct '18

30 Oct '18

Hi devs, Another quick update about the ongoing work on the variable filtering. Bug 21526 fixes the href attributes for links in a naive way (replacing html with uri), but there are a few wrong replacements that have been done (uri should have been url instead). I tried to fix them today with a follow-up on the bug, but it is not ready yet. If you find internal links that do not work it is certainly caused by this bug. Instead of opening a new bug report, please make sure the follow-up fixes the issue. Cheers, Jonathan

1 0

Kanopy and SIP2 hack
by Mark Alexander 27 Oct '18

27 Oct '18

Our little library is preparing to use the Kanopy video streaming service. Kanopy can use SIP2 to query our Koha server for the purpose of user authentication. That's great; I can enable SIP2 pretty easily. The problem is that our librarian wants to put limits on which patrons can use Kanopy. The idea is that we don't want to allow more than one person per household to be able stream videos; otherwise mom, pop, and all the kids could go crazy one weekend on a Buffy The Vampire Slayer binge, for example. But Kanopy and Koha don't have a way to impose this kind of limit. So I came up with the following idea, which does seem to work in my test VM: 1. Add a new patron attribute called "KANOPY_OK", which has a yes/no value. Set it to yes for those patrons that will be allowed access to Kanopy. 2. Hack the SIP server code for "handle patron status" to check the incoming client's IP address against a Kanopy-provided list of IP addresses. If there is a match, authenticate the patron only if their "KANOPY_OK" atribute is "yes" (actually "1"). But I hate the fact that I had to hack Koha to do this (see part of the hack below). Am I'm going at this the wrong way? Would it make more sense to enhance the plugin architecture to add a SIP2 patron filter function like the one below? Is this just too ugly to ever be considered seriously? Thanks in advance, Mark P.S. Here's the main part of the hack, which is a function that is called from handle_patron_status and handle_patron_info. my @kanopy_ips = ( "208.66.24.46", "104.239.197.182", "18.209.148.51", "34.232.89.121", "34.234.81.211", "34.235.227.70", "34.235.53.173", "52.203.108.44" ); sub sip2_check_patron { my ( $patron, $server ) = @_; if ( $patron ) { my $ipaddr = $server->{server}->{client}->peerhost; foreach my $kanopy ( @kanopy_ips ) { if ( $ipaddr =~ /^(::ffff:)?\Q$kanopy\E$/ ) { my $borrowernumber = $patron->{borrowernumber}; my $value = C4::Members::Attributes::GetBorrowerAttributeValue( $borrowernumber, 'KANOPY_OK' $ return $value eq "1"; } } } return 1; }

2 5