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

Give a try to RabbitMQ (background jobs rewrite) - POC!
by Jonathan Druart 26 Feb '20

26 Feb '20

Hi devs, I have submited a proof of concept (POC) on bug 22417 (Delegate background jobs execution). The idea would be to isolate our background jobs code (the one in the .pl) into module then use RabbitMQ to process them. More stuffs on the bug! https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22417 Cheers, Jonathan

4 4

DateTime->now usage
by Tomas Cohen Arazi 02 May '19

02 May '19

Hi, on testnig bug 22453 [1] I noticed that we do the wrong thing in many places, actually: $ git grep 'DateTime\->new' Do you agree we should be using dt_from_string instead? The consequences are for those having the DB server and/or the plack server running on some timezone and having koha-conf.xml point to another one. [1] https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22453 -- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F

4 3

Discussion of account types / labels
by Barton Chittenden 01 May '19

01 May '19

The accounts system uses the following codes to show what kind of fee or credit has been issued: A = Account management fee C = Credit F = Overdue fine FOR = Forgiven FU = Overdue, still accruing L = Lost item LR = Lost item returned/refunded M = Sundry N = New card PAY = Payment W = Writeoff The labels, such as 'Account management fee' and 'Overdue fine' are hard coded in various template toolkit files. This is problematic for a number of reasons: 1) It's not obvious where these are defined -- most other constants in Koha are in authorized values. https://koha-community.org/manual/18.05/en/html/faq.html#fines-table is the only place where a koha user can find them all in one place. 2) Because they're not in the database, they can't be used in reports (at least without kludgy case statements). 3) They're not available outside the web interface, so SIP2 and any API endpoints must show the raw codes. 4) 'FU' is a common abbreviation for an obscenity in English, and this has a tendency to show in up in a lot of places where it really shouldn't.

6 7

Removal of hidelostitems syspref
by Tomas Cohen Arazi 01 May '19

01 May '19

Hi all, I wanted to ask for opinions about removing the mentioned syspref. This is proposed on bug 8619, in which Owen already made a proposal for an enhancement so this is painless for users. Thanks for your feedback. -- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F

4 3

Signoff request
by Marcel de Rooy 01 May '19

01 May '19

Hi all, I have a few bugs waiting for quite some time in the queue and I need your help to get them further. https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20310 Article requests Just 3 simple patches Wrote them more than a year ago, last rebase May 2018 https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21533 Do not allow password recovery for administrative locked patrons Small follow-up on 21336, only one patch changing two lines Written in October, still applies https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21535 Anonymize function in Patron should not scramble email addresses Small followup on 21336, just one patch, 5 insertions, 2 deletions Also written in October, rebased https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21036 Fix a bunch of older warnings Three small patches, resolving a few warnings Written July 2018, last change October Thanks, Marcel

3 2

Jenkins / koha-testing-docker issues
by Tomas Cohen Arazi 25 Apr '19

25 Apr '19

Hi all, I'm trying to fix the issues preventing some jenkins tasks to run as they should. Sorry for the inconvenience. -- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F

1 0

Serial: numbering patterns: how to make it more clear that months and weekdays start from 0 ?
by Victor Grousset 24 Apr '19

24 Apr '19

Hi :) , That might not be clear, even for developer, and even less for a librarian. How could this info be delivered reliably to the user? To avoid running in circle during too long before realizing that? Even more hard to understand when there are cases like biannual where if you start from February, it will work even if you assumed that January was 1. But if you start from February, there will be issues after one year. Should there be tooltips? The related fields are marked with a red dot in the following screenshot. https://framapic.org/4P2ZzbgJpuvA/SIleKzEuYVaG.png Cheers, -- Victor Grousset, dev support/maintenance BibLibre, Services en logiciels libres pour les bibliothèques BibLibre, Libre/Open Source software and services for libraries

3 2

koha-testing-docker - production use
by Waylon Robertson 18 Apr '19

18 Apr '19

I am trying to move my already existing 17.05 koha install, on a old ubuntu-minimal docker, to koha-testing-docker, figure all it needs is a change of config, and then i can stop the db docker container, only... it is ignoring my changes to koha-conf.xml inside sites/kohadev.my changes are there, and yet koha-rebuild-zebra etc are just ignoring them. I've also tried changing .env and defaults.env to match my creds before docker-compose up, and it seems like all options are taken into account, except the HOSTNAME, or DB_HOSTNAME or DB_HOSTno variation works. I am thinking, maybe its better to just start from a debian docker image, and start from there, build it up myself?I need to do this, as the docker i have, won't boot up on my new centos 7 system, mpm_itk says something about seccomp, and stops apache from running perl.

2 1

Call for News: April 2019 Newsletter
by kohanews 17 Apr '19

17 Apr '19

Hello all! I'm collecting news for the April 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

Re: [Koha-devel] [Koha] Should password be mandatory to send
by BOUIS Sonia 16 Apr '19

16 Apr '19

Hi Katrin, Thank you for this review of Bugzilla tickets. I can see that I'm not the only one to think that there's a lack of a notification to welcome our new users. I thought that it will be simpler to use ACCTDETAILS but it seems that it's more complicated than I expected. Perhaps a new notification could be a nice idea. Sonia Message: 2 Date: Sun, 14 Apr 2019 21:01:35 +0200 From: Katrin Fischer <katrin.fischer.83(a)web.de> To: koha(a)lists.katipo.co.nz, Koha Devel <koha-devel(a)lists.koha-community.org> Subject: Re: [Koha-devel] [Koha] Should password be mandatory to send ACCTDETAILS notice Message-ID: <f781ac8a-3e4f-6582-49e6-52bc04d79723(a)web.de> Content-Type: text/plain; charset="utf-8"; Format="flowed" Hi Sonia, I think the ACCTDETAILS notice is a bit difficult. Last I checked I think it required you to enter email, userid and password before saving the patron the first time in order to work right. As it avoids the message queue there is no way to tell if the notice was sent correctly and there is no way to send it again. There are some bugs filed in this context: *Bug?9097* <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9097> - 'Welcome mail' for new library users *Bug?15834* <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15834> - Options to supress e-mail generated by AutoEmailOpacUser *Bug?18543* <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18543> - Automated emails for new patron accounts with the AutoEmailOpacUser preference I don't see a reason why password should be mandatory, other than it might lead to messages being sent out incomplete for libraries using it for this feature. I think it might be a bit nicer to realize the idea of a separate 'welcome mail', that goes through the message queue and have an option to send it again if needed. Hope that makes sense, Katrin On 11.04.19 09:31, BOUIS Sonia wrote: > Hello, > We wanted to send notices to our new external patrons using ACCDETAILS notice but, we have seen that in members/memberentry.pl, there's a checking to be sure there's a password for the patron. > We don't use the password (this field is in the "BorrowerUnwantedField" system preference in our Koha) because we send our patrons in the university directory with a specific password not created in Koha. > We would like to use the ACCTDETAILS notices to send our new patron a summary of the services provided by the library and to explain how they could connect to their account or how to change their password. We don't want to send them the password by email. > > Do you see a reason to keep checking if there's a password in memberentry.pl or do you think we could remove it? > > Thanks in advance for your thoughts. > > Cheers > > Sonia BOUIS > ------------------------------------------------------ > Responsable du Service des applications documentaires Biblioth?ques > universitaires Universit? Jean Moulin Lyon 3 ADRESSE G?OGRAPHIQUE > > Manufacture des Tabacs | 6 cours Albert Thomas | LYON 8e ADRESSE > POSTALE > Biblioth?que de la Manufacture | 1C avenue des Fr?res > Lumi?re | CS 78242 - 69372 LYON CEDEX 08 > > Ligne directe : 33 (0)4 78 78 79 03 > > http://bu.univ-lyon3.fr<http://bu.univ-lyon3.fr/>| Suivez-nous > > Facebook<https://www.facebook.com/bulyon3/> | > Twitter<https://twitter.com/bulyon3>| > Instagram<https://www.instagram.com/bu.lyon3/?hl=fr> > --------------------------------------------------- > L'Universit? Jean Moulin est membre de l'Universit? de Lyon > > _______________________________________________ > Koha mailing list http://koha-community.org Koha(a)lists.katipo.co.nz > https://lists.katipo.co.nz/mailman/listinfo/koha

1 0