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

Enable libraries to moderate OPAC self-registrations
by Alex Buckley 14 Sep '22

14 Sep '22

Kia ora/Hello Koha community, I am currently working on reviving bug 25090 <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25090> ( Moderate OPAC self-registrations before a patron account is created ). *New proposed functionality:* Step 1: The library enables both the new 'PatronSelfRegistrationModeration' syspref and the existing 'OpacResetPassword'syspref. Step 2: When a user submits an OPAC self-registration their Koha patron account is not created immediately - i.e. they cannot yet log into the OPAC. Step 3: A pending registration link appears at the bottom of the staff client home page (like what's currently done with new purchase suggestions, or OPAC patron modification requests). Step 4: Librarians can click on the link to go to a page to approve or decline the registration. Step 4a: If approved the user is sent an email notice, containing their Koha username and an OPAC reset password link. Step 4b: If declined the user is sent a different email notice. *The rationale for adding this feature:* You can currently limit the circulation of self-registered patrons - by using the PatronSelfRegistrationDefaultCategory syspref and creating circulation rule(s) for that category. However, users only need an OPAC login (without the ability to circulate) to access electronic content providers (integrated with Koha via STunnel/SIP2). Some electronic content providers charge libraries based on their usage. Meaning it might not be optimal having anyone from around the world self-registering for a library OPAC login and accessing electronic content from some providers, therefore, incurring extra costs for the library. Bug 25090 was originally developed in the early days of the pandemic to ensure new self-registering OPAC users accessing 3rd party databases were coming from acceptable locations i.e. they were members of the organisation the library is in. More details can be found here: https://www.catalyst.net.nz/blog/mental-health-education-resource-library-n… *Questions I would like to hear your thoughts on please:* Q1: Are you in favour of this as a new feature in Koha? Q2: Would you prefer a new database table be added for self-registrations awaiting approval, or should I use the borrowers_modifications table - as is used by OPAC patron modification requests? Q3: How would you envisage this self-registration moderation feature fitting in with the existing PatronSelfRegistrationVerifyByEmailand PatronSelfRegistrationDefaultCategory sysprefs? Any thoughts much appreciated. Kind regards, Alex

5 16

Handling normalized phone number data
by dcook＠prosentient.com.au 14 Sep '22

14 Sep '22

Hi all, I've been working lately on https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23817 in an effort to let staff users easily search phone numbers in the Patrons module. Currently, phone number searching doesn't work if you have punctuation or other formatting inconsistent with your search query. So I'm proposing normalizing phone numbers. Normalizing the search query is easy, but normalizing the data in the database is harder. In older versions of Koha, I used SQL to normalize the phone column in the WHERE clause, but that's seemingly impossible now that we're using DataTables and the REST API. So it seems to me the only way forward is to normalize the data in the database. I've attached a patch which provides a Koha::Patron->phone() set method which normalizes the phone number before it's saved in the database, but I don't know what other Koha folk think about that. Thoughts? David Cook Senior Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia Office: 02 9212 0899 Online: 02 8005 0595

1 0

Call for news - Newsletter September 2022
by Koha Newsletter 13 Sep '22

13 Sep '22

I'm collecting news for this month's newsletter. Send anything noteworthy to: kohanews (at) gmail (dot) com News criteria: -------------- * News items can be of any length, images are fine. * Please send your text in plain text or as simple HTML (no Word / Google documents etc) * Anything and everything Koha. * Submit by the 26th of the month. For events: * Please include dates for past events. One month back is the cut-off. * Announcements for future events with dates to be announced are fine, e. g. Kohacon. 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! Michael Kuhn Editor, Koha Community Newsletter

1 0

Forward this to librarians prone to contribute: Monday 26th: patch testing session to help enhancements and bug fixes to be released
by Victor Grousset/tuxayo 08 Sep '22

08 Sep '22

Hi :) And also come, developers, admins, trainers, etc if you like a dedicated time with the community to test patches. Let's meet at any moment in the following timeframe: 13h-19h UTC / 14h-20h UK/ 9h-15h US East/6h-12h US West The place is https://visio.chapril.org/koha Here is a resource about how to test patches using sandboxes: https://wiki.koha-community.org/wiki/Sandboxes Modalities: The idea is to test patches to contribute to Koha. That's one of the **easiest and best way** to contribute to Koha. There is a huge need of testing to unblock patches and it would make a sizable difference in the pace of development of Koha if we reduce this bottleneck. No need for particular skills, just basic Koha usage. You can come an leave at any moment, even for a short time it's possible to get simple stuff moving forward. We will use a VoIP call with chat tool to speak and eventually screenshare. It's possible to join without sound and only use chat. So if you are at the front desk and there are not much patrons you can still test patches ^^ And also it's easier if you aren't comfortable with oral english. No need to have a local Koha instance. Just with a web browser we can use the sandboxes [1] to have temporary Kohas to test most of patches and do whatever we want without bad consequences. Cheers, [1] https://wiki.koha-community.org/wiki/Sandboxes -- Victor Grousset/tuxayo

1 0

Libraries using MARC 880 will need a fix...
by dcook＠prosentient.com.au 08 Sep '22

08 Sep '22

Hi all, A couple months ago I wrote a fix for "Bug 15187 - Adding 880 Fields to index-list in order to Increase Search for ALL non-latin Scripts" for Zebra. While it worked in terms of adding 880 to the indexing, it created an unexpected problem with the search result display, since the MARC records in the search results are fetched from Zebra and not MySQL. Yesterday, I raised "Bug 31532 - Zebra search results incorrect because of Bug 15187". This uses pure Zebra configuration to use the same mechanism as Bug 15187 but only at the indexing stage. Records retrieved from Zebra will still be the original sent from Koha to Zebra. It's actually the original solution I wrote for Bug 15187 before thinking there was an easier way. Fwiw, Elasticsearch indexes the 880 in its own way in the Koha code. David Cook Senior Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia Office: 02 9212 0899 Online: 02 8005 0595

1 0

Regular Koha Mailing list down ?
by Marcel de Rooy 07 Sep '22

07 Sep '22

Hi CHris, It seems that the mails to the regular Koha ML (katipo one) are not coming thru since September 1. The archive also shows August entries. Do you know how to resolve? Thanks, Marcel

2 1

Re: [Koha-devel] [Koha] DBMS auto increment fix not working
by Michael Kuhn 06 Sep '22

06 Sep '22

Hi Marcel Unfortunately it seems like the mailing list is not accepting my original answer to your e-mail (I tried twice). Instead after some days I received an e-mail with the subject "Undelivered Mail Returned to Sender", telling me The mail system <koha(a)lists.katipo.co.nz>: connect to lists.katipo.co.nz[202.70.130.220]:25: Connection refused I don't even know if this e-mail is getting through. There's probably something wrong with the mailing list when not accepting answers. 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 Am 30.08.22 um 13:17 schrieb Marcel de Rooy: > Hi, > > The fact that it will no longer happen under MariaDB 10.5.15 does not guarantee that you still suffer the consequences of older occurrences. > The wiki promises a script but it never made it probably. But the easiest 'solution' is deleting the records in the deleted_* tables that have a corresponding id in the normal tables. > After that verify that your autoincrement pointers on the normal tables are higher than the maximum id values in the deleted tables. If they would not be, you may bump into the issue again one day. > > Marcel > > ________________________________ > Van: Koha <koha-bounces(a)lists.katipo.co.nz> namens Michael Kuhn <mik(a)adminkuhn.ch> > Verzonden: donderdag 25 augustus 2022 11:03 > Aan: Koha <koha(a)lists.katipo.co.nz> > Onderwerp: [Koha] DBMS auto increment fix not working > > Hi > > In our library we are using Debian 11 with MariaDB 10.5.15 and Koha > 21.05.14. > > When deleting bibliographic records in the staff client, some deletions > produce the message: "An error has occurred! Error 500 / This message > may have been caused by any of the following reasons: etc." In such > cases Koha menu "About Koha > System information" shows the message > aubout data problems, saying > > Some of your tables have problems with their auto_increment values > which may lead to data loss. > > You should not ignore this warning. > > The problem is that InnoDB does not keep auto_increment across SQL > server restarts (it is only set in memory). So on server startup the > auto_increment values are set to max(table.id)+1. > > To know how to avoid this problem see the related wiki page: DBMS auto > increment fix > > > According to > https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwiki.koha… the problem > shouldn't appear with MariaDB 10.5.15 but as a trial we have implemented > the solution described there and have restarted everything - still the > problem persists. > > In such cases file "plack-error.log" shows the following: > > {UNKNOWN}: DBI Exception: DBD::mysql::db do failed: Duplicate entry > '6187-marcxml-MARC21' for key 'deletedbiblio_metadata_uniq_key' [for > Statement " > INSERT INTO deletedbiblio_metadata (biblionumber, > format, `schema`, metadata) > SELECT biblionumber, format, `schema`, metadata FROM > biblio_metadata WHERE biblionumber=? > "] at /usr/share/koha/lib/C4/Biblio.pm line 2907 > > I suspect this behavior indeed looks like the original auto_increment > problem described in bugs 18242, 18651, 18966, 19106 and 20271 but the > reason may in fact not be the same since the described problem shouldn't > appear at all in MariaDB 10.5.15. > > Does anyone have an idea what is happening and how we can solve it? > > 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 https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.admink… > _______________________________________________ > > Koha mailing list https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fkoha-commu… > Koha(a)lists.katipo.co.nz > Unsubscribe: https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.kat… > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha(a)lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

1 0

Koha Community Newsletter: August 2022
by Koha Newsletter 29 Aug '22

29 Aug '22

The Koha Community Newsletter for August 2022 is here: https://koha-community.org/koha-community-newsletter-august-2022/ Many thanks to everyone who submitted articles and news to this newsletter! Please feel free to email me with any corrections or suggestions. -- Michael Kuhn Editor, Koha Community Newsletter

1 0

Difficulties with JSON::Validator after upgrading to 22.05
by Philippe Blouin 26 Aug '22

26 Aug '22

Hi folks! Got a really weird error in my logs right now: "is_bool" is not exported by the JSON::Validator::Util module "is_num" is not exported by the JSON::Validator::Util module "str2data" is not exported by theJSON::Validator::Util module Can't continue after import errors at /usr/share/perl5/JSON/Validator/Schema.pm line 7. BEGIN failed--compilation aborted at /usr/share/perl5/JSON/Validator/Schema.pm line 7. Compilation failed in require at /usr/share/perl5/Mojo/Base.pm line 134. BEGIN failed--compilation aborted at /usr/share/perl5/JSON/Validator/Schema/Draft4.pm line 2. Compilation failed in require at /usr/share/perl5/Mojo/Base.pm line 134. BEGIN failed--compilation aborted at /usr/share/perl5/JSON/Validator/Schema/OpenAPIv2.pm line 2. Compilation failed in require at /inlibro/git/koha-v22-dev-blou/Koha/REST/V1.pm line 25. BEGIN failed--compilation aborted at /inlibro/git/koha-v22-dev-blou/Koha/REST/V1.pm line 25. Compilation failed in require at (eval 22) line 1. Which ruins most table displays. The error is weird in many ways, including the fact that /usr/share/perl5/JSON/Validator/Util.pm DOES export is_bool and friend in its header. cpan tells me I have the latest version, etc... I have Ubuntu 20.04, which I'm upgrading now to 22.04, but I don't expect much to change there considering the error. Any suggestion? Best regards, -- Philippe Blouin, Directeur de la technologie Tél. : (833) 465-4276, poste 230 philippe.blouin(a)inLibro.com inLibro | pour esprit libre | www.inLibro.com <http://www.inLibro.com>

2 3

Re: [Koha-devel] Mojolicious controllers for Koha plugins
by dcook＠prosentient.com.au 22 Aug '22

22 Aug '22

Awesome! Thanks, Kyle! I would love to get this into 22.11. David Cook Senior Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia Office: 02 9212 0899 Online: 02 8005 0595 From: Kyle Hall <kyle(a)bywatersolutions.com> Sent: Friday, 19 August 2022 1:14 AM To: dcook(a)prosentient.com.au Cc: koha-devel(a)lists.koha-community.org; Tomas Cohen Arazi <tomascohen(a)theke.io>; Renvoize, Martin <martin.renvoize(a)ptfs-europe.com> Subject: Re: Mojolicious controllers for Koha plugins Excellent! Tested and signed off on everything :) Kyle On Thu, Aug 18, 2022 at 3:04 AM <dcook(a)prosentient.com.au <mailto:dcook@prosentient.com.au> > wrote: Thanks, Kyle! Leveraging some past work, I was able to put something together fairly quickly. I’ve posted it to https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31380 It has two dependent bug reports but I’ve posted patches for them too, and they’re fairly straightforward. It should be very easy to test, so hopefully you can have a look and let me know what you think. David Cook Senior Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia Office: 02 9212 0899 Online: 02 8005 0595 From: Kyle Hall <kyle(a)bywatersolutions.com <mailto:kyle@bywatersolutions.com> > Sent: Tuesday, 16 August 2022 9:27 PM To: dcook(a)prosentient.com.au <mailto:dcook@prosentient.com.au> Cc: koha-devel(a)lists.koha-community.org <mailto:koha-devel@lists.koha-community.org> ; Tomas Cohen Arazi <tomascohen(a)theke.io <mailto:tomascohen@theke.io> >; Renvoize, Martin <martin.renvoize(a)ptfs-europe.com <mailto:martin.renvoize@ptfs-europe.com> > Subject: Re: Mojolicious controllers for Koha plugins That sounds great to me David! I'll 100% assist you with testing and qa! On Tue, Aug 16, 2022 at 3:42 AM <dcook(a)prosentient.com.au <mailto:dcook@prosentient.com.au> > wrote: Hi all, I was just writing a Koha plugin to do a big data export, but I realize that it’s probably going to timeout, because Koha plugins run under Plack::App::CGIBin which buffers the entire response before it returns it to Apache to return to the client browser. It’s the reason Koha uses CGI instead of Plack for export.pl <http://export.pl> While we can use Mojolicious controllers with Koha plugins when it adds REST API endpoints, we can’t do that for Koha plugins themselves. This is a topic that I’ve touched on before, and there are challenges when it comes to Authentication and Templates, but they’re solvable challenges: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26791 “Build Mojolicious controller replacement for export.pl <http://export.pl> ” https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28325 “Build Mojolicious controller replacement for tools-home.pl <http://tools-home.pl> ” We could just start by supporting “tool” and “report” with the Mojolicious controllers, and that would just mean plugins-home.pl <http://plugins-home.pl> detecting that there is Mojolicious support in that plugin, and then building a URL to “/staff/plugins/run” instead of “/cgi-bin/koha/plugins/run.pl <http://run.pl> ” for instance. That Mojolicious controller would really just need to check authentication/authorization, which is very doable with a fairly minor refactor. If I could get the support of just a couple other people, I’d be happy to do a lot of the authoring (or testing or whatever needs to be done just to get it done). By using Mojolicious controllers for select plugins, we’d also be able to shake out any issues without causing any regressions in core Koha, and then hopefully be able to start refactoring core Koha too… Anyways, please give it some consideration, and ask me if you have any questions. I’ll be looking more into export problems tomorrow, so I might end up going a different route for the sake of time in the short-term, but I think we should still be looking at shifting away from CGI and Plack::App::CGIBin due to their limitations… David Cook Senior Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia Office: 02 9212 0899 Online: 02 8005 0595 -- Kyle M. Hall Loose Cannon, ByWater Solutions <mailto:kyle@bywatersolutions.com> kyle(a)bywatersolutions.com <http://bywatersolutions.com/> https://bywatersolutions.com <http://bywatersolutions.com/what-is-koha/> What is Koha? -- Kyle M. Hall Loose Cannon, ByWater Solutions <mailto:kyle@bywatersolutions.com> kyle(a)bywatersolutions.com <http://bywatersolutions.com/> https://bywatersolutions.com <http://bywatersolutions.com/what-is-koha/> What is Koha?

2 2