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

Valid id_types for LookupPatron in ilsdi.pl
by Jon Knight 08 Nov '17

08 Nov '17

Hi all, I've been tinkering on bug 13990 to provide ilsdi.pl with a default when the optional id_type field in LookupPatron isn't supplied by the client. We'd noticed some time ago that we can use "email" as an id_type to search patron's based on email address, which turns out to be very handy for integrating with the CampusM mobile app that we have here (which uses email addresses for lots of stuff). However email isn't a documented id_type so whilst tinkering on 13990 I added it into the POD and online documentation in the patches. I traced the logic in the code a bit and realised that any borrower table field can be specified as an id_type. Is this expected/OK? The ilsdi.pl script is usually either disabled or restricted to a known set of IP addresses, so I don't think its much of a security issue, but it does mean that we're exposing database schema details to the outside world, which might cause integration issues if we did ever change the borrower table fields. Should id_type be a constrained list that LookupPatron validates? If so, I hope we can have email in there! ;-) If not, should the documentation point out that any borrower table column name is OK as an id_type field? Jon

1 0

Canceling reserves via opac
by Alex Arnaud 08 Nov '17

08 Nov '17

Hi Koha community Just came across a weird thing about the way Koha handle the ability to cancel reserves via opac user account. There is 2 steps: - Displaying of the "cancel" button. Which depends on Koha::Hold->is_cancelable method, - the cancellation itself, which depends on C4::Reserves::CanReserveBeCanceledFromOpac The problem is that the 2 sub do not behave the same. Just see: /sub is_cancelable {// // my ($self) = @_; // //// //*return 1 unless $self->is_found();*// // return 0 if $self->is_in_transit(); // //*return 1 if $self->is_waiting(); * // // return 0; // //}/ /sub CanReserveBeCanceledFromOpac {// // my ($reserve_id, $borrowernumber) = @_;// // // return unless $reserve_id and $borrowernumber;// // my $reserve = Koha::Holds->find($reserve_id);// // // return 0 unless $reserve->borrowernumber == $borrowernumber;// //*return 0 if ( $reserve->found eq 'W' ) or ( $reserve->found eq 'T' );*// // // return 1;// // //}/ A concrete example is that if i want to cancel a waiting reserve, i can see the button, but it does nothing. I think this should be fixed, but which sub is the right one? Regards Alex Biblibre

2 1

What's on in koha-devel #16
by Jonathan Druart 07 Nov '17

07 Nov '17

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

2 1

Meeting reminders for tomorrow
by Nick Clemens 07 Nov '17

07 Nov '17

Hi All, Reminder that we have 2!!! Koha IRC meetings tomorrow, General and Development You can follow the calendar to get updates: https://koha-community.org/calendar/ Agendas where you can find IRC info and local time conversions: https://wiki.koha-community.org/wiki/General_IRC_meeting_8_November_2017 https://wiki.koha-community.org/wiki/Development_IRC_meeting_8_November_2017 Hope to see you all soon! -Nick

1 0

New Firefox version 57 incompatibility with JS Print Setup Addon
by Roger Grossmann 07 Nov '17

07 Nov '17

Hi all, I am not sure whether one of you has more information about an incompatility of the "JS Print Setup Addon" with the new Firefox version 57 going to be released on 2017-11-14. It seems that the new Webextensions API used with Firefox 57 does not provide the functionality required to build a compatible version of the "JS Print Setup Addon". See https://github.com/edabg/jsprintsetup/issues/39 and https://bugzilla.mozilla.org/show_bug.cgi?id=1385827 With an activated automated Firefox update function the update is going to be installed automatically after 2017-11-17 which makes the silent print feature likely to be dysfunctional. Looks like blocking the FF 57 update until the issue is fixed is the only way for now to keep the silent printing feature. Roger -- LMSCloud GmbH Roger Großmann - Geschäftsführer Konrad-Zuse-Platz 8 - D-81829 München t +49 (0)89 207042-620 m +49 (0)171-2194775 f +49 (0)89 207042-623 e roger.grossmann(a)lmscloud.de w www.lmscloud.de

2 1

Koha 18.05 released in march ? (Joubu)
by Paul Poulain 04 Nov '17

04 Nov '17

Hi Koha-devel & mainly Jonathan, On your RM proposal (https://wiki.koha-community.org/w/index.php?title=Proposal_for_RM_18.05_jou…) , you write: * Koha 18.05 will be released *end of March*, if it is considered stable enough for release I've nothing against this, but is there a reason to release in March and not in May as usual ? In this case, shouldn't we call it 18.03 ? Or will it be a 18.05RC, and the final 18.05.00 will still be in May ? Anyway: explanation welcomed ;) -- 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

Koha Community Newsletter: October 2017
by kohanews 02 Nov '17

02 Nov '17

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

Multiple levels approval for suggested title and multiple level late fee slabs required in Koha
by Manju N 01 Nov '17

01 Nov '17

Dear All, Anybody has customized the Koha for multiple level approval of suggested titles from the patrons/faculty in Acquisition module? In our library, we need multiple level approvals such as from the Head of Department and Chairman, Library Committee/Dy. Director etc. We also want to use multiple levels late fee/fine slab. Currently, Koha supports only one late fee slab. We have different late fee structure/ slabs at our library. Please let us know if anybody customized the Koha for the above requirements. With Regards Manju Naika, PhD Asst.Librarian IIT Bombay

3 2

Mailinglist "Koha"
by Michael Kuhn 31 Oct '17

31 Oct '17

Hi Does anyone know hat happened to the mailinglist "Koha", it seems the list has become inactive? I haven't received any e-amils from there since October 25. Also I sent one answer but it didn't appear until now (at least I didn't receive it via the list). I didn't know where else to ask this. Best wishes: Michael -- Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz T 0041 (0)61 261 55 61 · E mik(a)adminkuhn.ch · W www.adminkuhn.ch

4 5

Vote request for Bug 18483 Customised help: Enhance staff client with news based, easily editable help system (Passed QA -> In Discussion)
by Marc Véron 30 Oct '17

30 Oct '17

Dear Koha community On 2017-04-22 I filed Bug 18483 "Customised help: Enhance staff client with news based, easily editable help system". https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18483#c0 The Enhancement was ready for Sign off on 2017-04-30, was signed off on 2017-05-02, and, after some discussion, passed QA on 2017-10-27, and the same day was set to "In Discussion". The aim of the bug is described in the initial comment. It fills a request we have since 2012. In short, it is about having an additional help system that allows libraries to create their own, library specific help information, taking advantage of all functionality we already have with the news system. Initial comment: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18483#c0 ---Quote--- "Koha's staff client has a file based help system with an edit function for customising. However, the edited files have to be saved and restored with each release. Otherwise they are overwritten. As an enhancement or alternative, the existing news system can be used to implement a complementing help system. Similar to the news, the text can be created for all branches or for individual branches. Help is context sensitive (based on the existing help system), and it can be created / edited directly from the help page (based on a user permission). The display can be managed with a system preference (Bug 18472: Add system preference CustomOnlineHelpStaff to hide / select custom online help system)." ---End quote --- Author's answer on a question of QA team member M. de Rooy (asked on Bug 18472, Comment 21), moved to Bug 18483: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18483#c21 ---Quote--- Need: - Having a user editable, page aware help system is a long outstanding need. First time I was asked for goes back to 2012. - We have libraries interested in Koha who ask for in their requirements. - Writing a brand new help module would take a lot of time. And who would fund it? User: - The news system works very well and libraries are used to use it. The help additons introduced in Bug 18483 enhances the news system to host custom help as well. - From a user standpoint it is easy to use, you can add whatever you want / need as help. All the benefits of the news system can be used. Custom help items can easyly be added / edited. - It can be turned on and off (combined with the existing file based help system or 'standalone'). This Bug 18472 is the basis for turning on and off and/or add additional help systems. - There is no change in behavior of news and file based help system if turned off (however this patch allows to turn off the edit function of the existing file based help system). Impact: - In Bug 18483, I paid great attention to have a minimal impact on existing code. No changes in .pm files were needed. - There is a small database change to have a field to host the page key if a news item is used as help item. Things to come: - Since the news system works for both staff client and OPAC it will be easy to implement the editable help for OPAC as well (Bug 18515) So I kindly ask for Bug 18472 and Bug 18483 to make part of Koha. ---End quote--- After the enhancement has been put to "In discussion", I kindly ask the Koha community to vote about Bug 18483 as outlined in: https://wiki.koha-community.org/wiki/Bug_and_Enhancement_Discussion Thanks and kind regards Marc Véron Koha Support Schweiz www.koha-support.ch Contributing to Koha since 2012

2 1