September 2023 - Koha - lists.katipo.co.nz

Restore the default Marc Framework
by Victor Barroso Oliveira 04 Sep '24

04 Sep '24

Hello, how to restore the default Marc Framework to the original pattern? koha version 22.05.05 ubuntu 20 Thanks, Victor

4 5

Elastic search for Arabic
by Mohamad F Barham 29 Aug '24

29 Aug '24

Dears, Any one up to help in enhancing elastic search for arabic, specially "ال التعريف " at the beginning of word removal Regards Mohamad Barham System Engineer | Information Technology Department Birzeit University P.O.Box. 14, Birzeit, Palestine Tel: + 970 22982012 | Mob: +970 597 861929 | Ext: 5616 mbarham(a)birzeit.edu | www.birzeit.edu<http://www.birzeit.edu/> ~~~~~~~~~~~~~~~~~~~~~~~~~~ The information contained in this communication is intended solely for the use of the individual or entity to whom it is addressed and others authorized to receive it. It may contain confidential or legally privileged information. If you are not the intended recipient you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this information is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by responding to this email and then delete it from your system. The University is neither liable for the proper and complete transmission of the information contained in this communication nor for any delay in its receipt. ~~~~~~~~~~~~~~~~~~~~~~~~~~

2 4

23.05.x String Freeze
by Fridolin SOMERS 18 Mar '24

18 Mar '24

String freeze for 23.05.04 starts today :) Happy translating. -- Fridolin SOMERS <fridolin.somers(a)biblibre.com> Software and system maintainer 🦄 BibLibre, France

1 5

Re: [Koha] How to copy patron permissions?
by BRANNON, CHRISTOPHER 22 Jan '24

22 Jan '24

Michael, I've had some jQuery in the Koha library for quite a while. You should take a look at https://wiki.koha-community.org/wiki/JQuery_Library#Add_clear_and_preset_pe… There are 3 versions of this for different versions of Koha, but this latest one includes a clear permissions button, a couple of preset permission buttons, and a copy permissions button. Please check it out. We also did a video tutorial on this enhancement in season one of The Terrific Every-Other-Thursday Training Videos. You can find that here: https://youtu.be/M6aQITCJY0U. ___________________________ Christopher Brannon IT Coordinator 702 E Front Ave Coeur d'Alene, ID 83814 (208)769-2315 Ext. 456 cbrannon(a)cdalibrary.org www.cdalibrary.org Keep tabs on us at: Date: Tue, 26 Apr 2022 10:39:58 +0200 From: Michael Kuhn <mik(a)adminkuhn.ch> To: Koha <koha(a)lists.katipo.co.nz> Subject: [Koha] How to copy patron permissions? Message-ID: <abc69231-a587-77d5-01d2-7f98e5b16174(a)adminkuhn.ch> Content-Type: text/plain; charset=UTF-8; format=flowed Hi Is it possible to copy the permissions of another patron when creating a new one? I always thought this would happen when copying/duplicating an existing patron. But when I actually tried it today the permissions were not there with the new patron and I had to set them manually. Best wishes: Michael Kuhn

4 3

Cannot stage authority files in 22.11.
by Raymund Delahunty 15 Oct '23

15 Oct '23

We moved from 21.11 to 22.11 recently and since then attempts to stage and import authority record have failed. We are using the LC-card-number index as the matchpoint and have tried changing the normalisation rule from None to Remove spaces but the stage still fails. We can stage without matching, but when we change the matchpoint afterwards to LC-card-number (auth 010$a) we receive an Error 500. We have also had a problem with diacritics in authority searches when using Zebra and on our test server this is solved using Elasticsearch which we are testing out. But ES has not resolved our auth staging problem. Any ideas? Ray Delahunty University of the Arts London . This email and any attachments are intended solely for the addressee and may contain confidential information. If you are not the intended recipient of this email and/or its attachments you must not take any action based upon them and you must not copy or show them to anyone. Please send the email back to us and immediately and permanently delete it and its attachments. Where this email is unrelated to the business of University of the Arts London or of any of its group companies the opinions expressed in it are the opinions of the sender and do not necessarily constitute those of University of the Arts London (or the relevant group company). Where the sender's signature indicates that the email is sent on behalf of UAL Short Courses Limited the following also applies: UAL Short Courses Limited is a company registered in England and Wales under company number 02361261. Registered Office: University of the Arts London, 272 High Holborn, London WC1V 7EY

2 1

[translate] Migrate Pootle to Weblate
by Jonathan Druart 15 Oct '23

15 Oct '23

Hello everybody, If you are a translator of Koha you should read this. Pootle is dead and we should move to Weblate, which is an active and well maintained project. We have been setting up a test server to let translators see how it goes. THIS IS A TEST SERVER: none of the changes will be saved! There are some changes in how the projects are structured. We will now have 2 projects: "koha" and "koha-manual". Each will contain several "components". One component in Pootle can only track on po file, which means we need one component per po file: https://translate.test.koha-community.org/projects/koha/ shows https://snipboard.io/rtKdTS.jpg It can be a bit disturbing at first, but there is this view: https://translate.test.koha-community.org/languages/es/koha/ that shows the progress per language: https://snipboard.io/UCJ1Ky.jpg The big win are: * We should no longer get "Critical errors: Python brace placeholders" (to be confirmed) * Translation changes will be propagated between the components of a given project, and so between versions: if you modify a string for 23.05 it will also modify it for the other branches! (to be confirmed as well!) guest user (not logged in) can only make suggestions: https://translate.test.koha-community.org/ User reviewer/6Mx1&a2S$HU*1KNbzCZV can accept suggestions. You are welcome to test and provide feedback! There is still a lot of work before effectively doing the migration, but we need first to know if users/translators are happy with it! Let us know! Cheers, Jonathan PS: About the structure of the projects, I've contacted the author of Weblate: https://github.com/WeblateOrg/weblate/discussions/9556 Next version will add a mecanism to structure components within a project!

6 7

The "one manual" idea
by Charillon, Aude 06 Oct '23

06 Oct '23

Hello, In the Koha Documentation team, we have been discussing whether we still need one version of the manual per Koha version. The idea being mooted is that having only one manual for all versions in the future may be better. It's an idea that is still at the exploration stage; at this point we would like to get feedback from a wider group of people, hence this message! I included further down a summary of what has been raised so far. We are particularly interested in your thoughts on the following: - What would be impacted if we decided to move to one manual - that we haven't considered yet (see summary)? What issues may arise, who would they affect, what are your suggestions to solve them? - Are there any specific considerations for translated versions of the manual? - Are there any technical considerations that us non-developers haven't thought of? If you have questions, concerns or just think it's a good idea, it would also be nice to hear from you :-) Thanks, Aude [aude_c on Koha IRC] Documentation Manager for the 23.11 cycle Issues with the current situation - The documentation cycle doesn't match the Koha development cycle. It is near impossible for the Documentation team to document all the new features before the new Koha version is released. The manual published alongside the new Koha version is always behind. - When the manual is updated, the update is made to the master branch - the one that matches the numbering of the Koha version currently in development. This master branch isn't visible (unless you know where to find it). It is possible to "backport" updates to older versions of the manual but this is not straightforward. Because we are behind with documenting features, some updates would have to go back through several older versions of the manual, making the process even less straightforward. I'll be honest: it's rare these days when we backport to older versions. - For library teams, that means the explanation of a feature in their Koha version is more likely to be in a newer version of the manual (than in the one they'll land on when clicking the Help button). One manual - why it would be beneficial - Everything in one place: all the latest additions and improvements to the manual available straight away to everyone everywhere. - Translated manuals: only one version to keep on top of. - Easier to manage by the community. How it could work; questions and concerns identified - What if something changes in a newer version of Koha / only exists in some versions but not others? Wouldn't that be confusing in one manual? We would need to clearly mark sections with the Koha versions it applies to, e.g. "until 22.11", "from 23.05". Aude Charillon Customer Services Consultant PTFS Europe aude.charillon(a)ptfs-europe.com

4 4

Koha not compatible with Plesk Control Panel?
by Alessandro Tedesco 04 Oct '23

04 Oct '23

Hello everyone, I am trying to install the current stable release of Koha on a VPS (OS Ubuntu 22.04.1) managed with the Plesk Control Panel. However, it seems that Koha is not compatible with Plesk. Below the error generated after launching the installation ------------------- # sudo apt-get install koha-common Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: psa : Conflicts: javascript-common but 11+nmu1 is to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. ------------------- I have found that Plesk is not compatible with the javascript-common package required by Koha (https:// talk.plesk.com/threads/cant-install-prometheus-together-with-plesk-on-debia… ). However, it's strange because last year I installed Koha without problems on a VPS with Plesk...maybe the javascript-common package in the latest versions of Koha? Does anyone experience the same issues? Thanks and Kind Regards Alex

3 11

Batch Authority merge
by Andrew R Hartung 02 Oct '23

02 Oct '23

I have a massive amount of authority records that are duplicated. I think I imported some twice. Is there a way to batch or bulk merge or delete them?

3 2

Error when trying to display item OPAC view.
by Andrew Hartung 01 Oct '23

01 Oct '23

I'm getting a error page when trying to see an item's OPAC view. I've verified that the OPAC address is correct in the OPACBaseURL preference. Here are some possibly relevant log files: ==> /var/log/koha/cbc_library/indexer-error.log <== 20230920 14:46:51 cbc_library-koha-indexer: client (pid 1317) killed by signal 15, stopping 20230920 15:14:03 cbc_library-koha-indexer: client (pid 1319) killed by signal 15, stopping ==> /var/log/koha/cbc_library/plack-error.log <== Field 035 must have at least one subfield at /usr/share/perl5/MARC/File/XML.pm line 483. Field 035 must have at least one subfield at /usr/share/perl5/MARC/File/XML.pm line 483. Field 035 must have at least one subfield at /usr/share/perl5/MARC/File/XML.pm line 483. Field 035 must have at least one subfield at /usr/share/perl5/MARC/File/XML.pm line 483. Field 035 must have at least one subfield at /usr/share/perl5/MARC/File/XML.pm line 483. Field 035 must have at least one subfield at /usr/share/perl5/MARC/File/XML.pm line 483. Field 035 must have at least one subfield at /usr/share/perl5/MARC/File/XML.pm line 483. Field 035 must have at least one subfield at /usr/share/perl5/MARC/File/XML.pm line 483. Field 035 must have at least one subfield at /usr/share/perl5/MARC/File/XML.pm line 483. Field 035 must have at least one subfield at /usr/share/perl5/MARC/File/XML.pm line 483. ==> /var/log/koha/cbc_library/plack-intranet-error.log <== [2023/09/20 16:02:01] [WARN] Argument "" isn't numeric in subroutine entry at /usr/share/koha/intranet/cgi-bin/cataloguing/additem.pl line 241. [2023/09/20 16:02:23] [WARN] Use of uninitialized value in string eq at /usr/share/koha/intranet/cgi-bin/cataloguing/addbiblio.pl line 545. [2023/09/20 16:02:35] [WARN] Use of uninitialized value in string eq at /usr/share/koha/intranet/cgi-bin/cataloguing/addbiblio.pl line 545. [2023/09/20 16:02:42] [WARN] Argument "" isn't numeric in subroutine entry at /usr/share/koha/intranet/cgi-bin/cataloguing/additem.pl line 241. ==> /var/log/koha/cbc_library/plack.log <== 192.168.1.207 - - [20/Sep/2023:16:31:30 -0500] "GET /intranet/mainpage.pl HTTP/1.1" 200 45712 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/116.0.0.0 Safari/537.36" ==> /var/log/koha/cbc_library/plack-opac-error.log <== [2023/09/20 14:55:57] [WARN] Use of uninitialized value in hash element at /usr/share/koha/opac/cgi-bin/opac/opac-detail.pl line 678. [2023/09/20 15:13:41] [WARN] Use of uninitialized value in hash element at /usr/share/koha/opac/cgi-bin/opac/opac-detail.pl line 678. [2023/09/20 15:15:26] [WARN] Use of uninitialized value in hash element at /usr/share/koha/opac/cgi-bin/opac/opac-detail.pl line 678. ==> /var/log/koha/cbc_library/worker-error.log <== 20230920 14:46:51 cbc_library-koha-worker: client (pid 1256) killed by signal 15, stopping 20230920 14:46:51 cbc_library-koha-worker-long_tasks: client (pid 1290) killed by signal 15, stopping 20230920 15:14:03 cbc_library-koha-worker: client (pid 1230) killed by signal 15, stopping 20230920 15:14:03 cbc_library-koha-worker-long_tasks: client (pid 1271) killed by signal 15, stopping ==> /var/log/koha/cbc_library/worker-output.log <== Cannot connect to the message broker, the jobs will be processed anyway (Failed to connect: Error connecting to localhost:61613: Connection refused at /usr/share/perl5/Net/Stomp.pm line 27.; giving up at /usr/share/perl5/Net/Stomp.pm line 27. ) at /usr/share/koha/bin/workers/background_jobs_worker.pl line 90. Cannot connect to the message broker, the jobs will be processed anyway (Failed to connect: Error connecting to localhost:61613: Connection refused at /usr/share/perl5/Net/Stomp.pm line 27.; giving up at /usr/share/perl5/Net/Stomp.pm line 27. ) at /usr/share/koha/bin/workers/background_jobs_worker.pl line 90. Cannot connect to the message broker, the jobs will be processed anyway (Failed to connect: Error connecting to localhost:61613: Connection refused at /usr/share/perl5/Net/Stomp.pm line 27.; giving up at /usr/share/perl5/Net/Stomp.pm line 27. ) at /usr/share/koha/bin/workers/background_jobs_worker.pl line 90. Cannot connect to the message broker, the jobs will be processed anyway (Failed to connect: Error connecting to localhost:61613: Connection refused at /usr/share/perl5/Net/Stomp.pm line 27.; giving up at /usr/share/perl5/Net/Stomp.pm line 27. ) at /usr/share/koha/bin/workers/background_jobs_worker.pl line 90.

4 3