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

How to make self-referential URLs in Koha
by dcook＠prosentient.com.au 30 Jan '23

30 Jan '23

Hi all, With some recent code, I've been using creating self-referential URL in Koha using CGI->url(), and passing it as a value. With CGI, the URL is correct (ie starting with /cgi-bin/koha). With Plack, it's not, because the OPAC is mounted as "/opac". I worked around this by rewriting the self-referential URL in my code, but I was wondering if anyone else had any thoughts on this. I've noticed there are a few places in Koha where we use CGI->url() and I'm guessing we may have unexpected bugs in Plack-enabled Koha as a result. Of course, one workaround would be to have /opac and /intranet aliases or URL rewriting in Apache, so that the self-referential URLs created by Plack still end up resolving. I wonder if that's the easiest path forward. In the past, I have wondered if we could get rid of "/cgi-bin/koha" as a path prefix all together (especially as cgi-bin scares security tools), but it's so deeply embedded in Koha at this point that it seems a huge task to replace it. Anyway, just throwing that out there. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Online: 02 8005 0595

6 8

String Freeze Notice
by Joy Nelson 12 Aug '22

12 Aug '22

Greetings! Just a quick note that string freeze will go into effect at the end of day 12/16/2019 for the maintenance branches. Maintenance releases scheduled for the 23rd. Translations can begin on the 17th. Thanks! -- Joy Nelson President, Koha Division ByWater Solutions <http://bywatersolutions.com> Support and Consulting for Open Source Software Phone/Fax (888)900-8944 What is Koha? <http://bywatersolutions.com/what-is-koha/>

3 3

Deploying Koha at scale
by Tomás 19 Aug '20

19 Aug '20

Hi folks. Theke Solutions has started a project some time ago, sponsored by ByWater Solutions to generate the tools and pipelines to provide a reliable Docker implementation for deploying Koha in production environments. We have just finished the housekeeping a few days ago so we are not embarrassed by our commit messages and leftovers :-D and want to propose it for community adoption anytime soon. The project lives here for now: https://gitlab.com/thekesolutions/koha-docker What you will find there is a Docker image that can be used to run any of the different Koha services/pieces on separate containers, or all inside a single one. We aimed to target different deployment scenarios, from a small library running it on a desktop computer to a multi-cluster K8s setup. A helm chart is part of the roadmap. You will notice there are a couple issues to be addressed [1]. For instance, the shipped docker-compose.yml is outdated regarding the MySQL/MariaDB server and we definitely need more on the README. Thanks to ByWater for supporting this effort, and now that people are talking about this, let's start the conversation \o/ [1] https://gitlab.com/thekesolutions/koha-docker/-/issues El jue., 11 jun. 2020 a las 4:52, <dcook(a)prosentient.com.au> escribió: > Hi all, > > For a long time, I've been thinking about how Koha could scale better, and > I'm wondering what other people are thinking about this topic. I think > Mengu > is probably the best expert on this topic that we have on Earth, so > especially curious about his input. > > It's relatively easy to add more Apache web servers, more MySQL nodes, and > more Elasticsearch nodes. but the same might not be said for other parts of > Koha like the following: > > 1. Zebra > a. In theory, you could load balance queries to a cluster of Zebra > listeners > b. But indexing updates to many Zebra databases could be tricky (I > don't know if Zebra's database can support many readers). I suppose you > could alter rebuild_zebra.pl to update multiple databases in a variety of > different ways. I imagine Mengu could speak to this, as I recall him > talking > once about needing to do work to make Zebra scale? > > 2. I'm not familiar enough with the SIP server to say > a. Off the top of my head, I think a TCP load balancer would be > good > enough here > > 3. Z3950 Responder? > a. I'm not familiar with this daemon > > 4. What about cronjobs? Only 1 instance should execute the cronjobs. > a. I suppose a person could disable cronjobs on all Koha nodes > except for 1? It wouldn't be very robust in terms of availability but it > would technically work most of the time. > > Any other thoughts? > > David Cook > Systems Librarian > Prosentient Systems > 72/330 Wattle St > Ultimo, NSW 2007 > Australia > > Office: 02 9212 0899 > Online: 02 8005 0595 > > > -- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F

4 4

An idea for consolidating staff interface header search forms
by Owen Leonard 07 Aug '20

07 Aug '20

I'm playing around with the idea of eliminating all the many search form include files (serials-search.inc, cat-search.inc, checking-search.inc, etc.) and replacing them with a single template which can be processed in different ways. For instance, in the circulation-home.tt template, "[% INCLUDE 'circ-search.inc' %]" would be replaced with "[% PROCESS header_searches.inc searches="circulation_searches" %]" In header_searches.inc (see https://gitlab.com/snippets/1994424) an array of search forms and their labels would be output according to the "searches" variable passed to the include file for processing. Unfortunately this doesn't appear to be translatable, but Bug 20988 might make it possible. Does this sound like a worthwhile pursuit? A sensible way to leverage Template toolkit's functionality? Thanks, -- Owen -- Web Developer Athens County Public Libraries (740) 737-6006 https://www.myacpl.org

4 10

--username and --password in process_message_queue.pl
by Tomas Cohen Arazi 03 Aug '20

03 Aug '20

Hi everyone. I'm finishing my work to make SMTP something configurable from the UI with multiple options and per-library configs [1]. I am right now tweaking all the places that send emails so they use this configurations. The only place where things aren't clear regarding what to do, is process_message_queue.pl, which has the following parameters: --username --password They are used to authenticate the SMTP request. The current behaviour is that all email-related stuff points to localhost, and those params are used to authenticate the SMTP connection. Does anyone use them? Is is ok to assume they should supersede the ones defined in the new configuration? Have a great weekend you all [1] https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22343 -- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F

2 1

Koha Community Newsletter: July 2020
by Koha Newsletter 31 Jul '20

31 Jul '20

The Koha Community Newsletter for July 2020 is here: https://koha-community.org/koha-community-newsletter-july-2020/ 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. -- Chad Roseburg Editor, Koha Community Newsletter

1 0

ModBiblio function error
by Stephen Graham 31 Jul '20

31 Jul '20

Hi All - I have a script which uses the ModBiblio function (i.e. https://perldoc.koha-community.org/19.11.x/C4/Biblio.html#ModBiblio) I haven't used the script for a while, and we've upgraded to 19.11 since I ran it last. Running the script today and I'm getting the following "error": oAuth error: Database unavailable (109) authorities Bib-1 I'm seeing this 4-5 times for each bibilo I've updated. The update does work. The record looks fine in staff/OPAC, it's findable etc. I've only updated 10 records on our test server, and before I update any more I'm just wondering why I'm getting this message and it will have an adverse effect on our indexing/database if I just ignore and update the reamining 6000+ records? Any advice would be most welcome! Cheers, Stephen -------------------------------------- Stephen Graham Library Technology Consultant Content and Collections Team Library and Computing Services University of Hertfordshire Tel: 01707 286111 Ext: 77751 Email: s.graham4(a)herts.ac.uk<mailto:s.graham4@herts.ac.uk>

5 9

Safari browser and Koha
by dcook＠prosentient.com.au 31 Jul '20

31 Jul '20

Hi all, Does anyone use Safari with Koha? I had someone using it the other day and they weren't able to upload a MARC file to the Staged MARC Management. I just had them use Firefox instead and it was fine though. What's our stance on Safari support? David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Online: 02 8005 0595

5 6

Connecting Koha to OCLC via Z39.50 server
by Monica Benavides 29 Jul '20

29 Jul '20

Our library recently created a z39.50 server (Koha 20.05). We are implementing OCLC Discovery. They can successfully connect to our server, but the connection closes during the attempt to retrieve the data (init 1020 error). How do we allow the connections to stay open in order for OCLC to retrieve our information? Thanks in advance! This XML file does not appear to have any style information associated with it. The document tree is shown below. <zs:searchRetrieveResponse xmlns:zs="http://www.loc.gov/zing/srw/"> <zs:version>1.2</zs:version> <zs:echoedSearchRetrieveRequest> <zs:version>1.2</zs:version> <zs:queryType>pqf</zs:queryType> <zs:query>@attr 1=1211 @attr 5=100 471460745</zs:query> <zs:maximumRecords>5</zs:maximumRecords> <zs:recordPacking>xml</zs:recordPacking> <zs:recordSchema>marcxml</zs:recordSchema> <zs:extraRequestData> <zs:target>REDACTED/biblios</zs:target> <zs:max-sockets>60</zs:max-sockets> </zs:extraRequestData> </zs:echoedSearchRetrieveRequest> <zs:diagnostics xmlns:diag="http://www.loc.gov/zing/srw/diagnostic/"> <diag:diagnostioc> <diag:uri>info:srw/diagnostic/l/2</diag:uri> <diag:details> session_shared: target closed connection during init </diag:details> <diag:message>System temporarily unavailable</diag:message> </diag:diagnostic> </zs:diagnostics> </zs:searchRetrieveResponse> -- *Monica Benavides* *Library Assistant/Testing Center Coordinator* –––––––––––––––––––––––––––––––––––––––––––––––––––– *Rocky Mountain University of Health Professions* 122 East 1700 South, Building 3, Provo, Utah 84606 Direct: 385.375.8772 *|* Campus: 801.375.5125 –––––––––––––––––––––––––––––––––––––––––––––––––––– *Stay connected, learn more!* Blog <https://rmuohp.edu/about-the-university/university-news/> | Facebook <https://www.facebook.com/RMUoHP> | Twitter <https://twitter.com/rmuohp> | YouTube <https://www.youtube.com/user/TheRMUoHP> | rm.edu

2 1

Signoff request
by Marcel de Rooy 29 Jul '20

29 Jul '20

Hi all, I submitted patches on bug 20472. https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20472 Add digital scan as optional format to Article Requests Please have a look. More work to follow. Marcel

1 0