November 2022 - Koha - lists.katipo.co.nz

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

Koha 21.11.09 released
by Arthur 11 May '23

11 May '23

The Koha community is pleased to announce the release of version 21.11.09. For full release notes, please visit https://koha-community.org/koha-version-21-11-09-released/ <https://koha-community.org/koha-21-11-09-released/> Thanks! 🚀

3 4

Analytical cataloguing causing a searching warning
by Aleisha Amohia 31 Mar '23

31 Mar '23

Hi Koha community! We're having some trouble with analytical cataloguing - linking host and child records. We have EasyAnalyticalRecords enabled, and UseControlNumber disabled. When we link the host item using the barcode, the detail page for the child item shows this warning above the title: "There was an error searching for analytic records, please see the logs for details." The Plack Intranet error log shows the following errors: [2022/02/15 13:59:09] [WARN] CCL parsing error (10014) Embedded truncation not supported ZOOM for query: Host-item=(BIBLIO_TITLE /) at /usr/share/koha/lib/C4/Search.pm line 241. [2022/02/15 13:59:09] [WARN] Warning from simple_search_compat: CCL parsing error (10014) Embedded truncation not supported ZOOM at /usr/share/koha/intranet/cgi-bin/catalogue/detail.pl line 152. I have tried also manually linking the host item by cataloguing directly into the 773 of the child item, the searching warning still shows. I have also tried enabling UseControlNumber and putting the 001 of the host record into 773$w of the child item, which has usually worked (the warning disappears), however this method does not work for us because the library doesn't usually fill in the 001. We'd rather keep UseControlNumber disabled. Is this a problem that other libraries have other seen? Have you been able to solve it while keeping EasyAnalyticalRecords enabled and UseControlNumber disabled? Would appreciate any help. Thanks all! -- Aleisha Amohia (she/her) Koha Developer Catalyst IT - Expert Open Source Solutions www.catalyst.net.nz CONFIDENTIALITY NOTICE: This email is intended for the named recipients only. It may contain privileged, confidential or copyright information. If you are not the named recipient, any use, reliance upon, disclosure or copying of this email or its attachments is unauthorised. If you have received this email in error, please reply via email or call +64 4 499 2267.

4 5

Upgrade to 21.11 Fails
by Bruce A. Metcalf 16 Mar '23

16 Mar '23

Greetings, Yes, I'm slow on the uptake, I've been running oldoldstable for some time now. With the release of 22.11, it's time for me to move up. My system was installed from deb packages under Debian 10, and has been updating fine. After an update (with no error messages), I find I am unable to access either the OPAC or the admin interfaces. Both give an "Internal Server Error" message, with a note that a 500 error was thrown by the ErrorDocument handler as well. Probably something simple, but not something I can see or find in the release notes. Help! Regards, / Bruce / Bruce A. Metcalf Augustan Library

6 16

Question on path for custom xsl files (OPAC and Staff client)
by Bruns, Anke 24 Feb '23

24 Feb '23

Hi, we have some settings of our own in some XSL files, e.g. /usr/share/koha/opac/htdocs/opac-tmpl/bootstrap/{langcode}/xslt/MARC21slim2O PACResults.xsl as well as for the staff client in e.g. /usr/share/koha/intranet/htdocs/intranet-tmpl/prog/{langcode}/xslt/MARC21sli m2intranetResults.xsl All works fine when we copy and rename these files, keeping our own versions in /usr/share/koha/opac/htdocs/opac-tmpl/bootstrap/{langcode}/xslt/ resp. /usr/share/koha/intranet/htdocs/intranet-tmpl/prog/{langcode}/xslt/ For us, however, it would be easier to store them in another place, e.g. (for the OPAC): /usr/share/koha/opac/htdocs/<our_directory>/<instancename>/{langcode}/xslt/ so we could hold all our files in one place (<our_directory), together with e.g. logos and other pictures etc, which we could easily tar and transport to another server when migrating an instance. But, alas, this doesn't seem to work - obviously the parameters XSLTDetailsDisplay, XSLTResultsDisplay, OPACXSLTDetailsDisplay and OPACXSLTResultsDisplay expect the files in the same directories as the standard versions. Is there any rule what paths are possible for our own xsl files/settings? Thanks in advance and best regards, Anke -- Anke Bruns M.A. (LIS) Arbeitsgruppe "Anwendungs- und Informationssysteme" E-Mail: anke.bruns(a)gwdg.de --------------------------------------- Gesellschaft für wissenschaftliche Datenverarbeitung mbH Göttingen (GWDG) Burckhardtweg 4, 37077 Göttingen, URL: https://gwdg.de Support: Tel.: +49 551 39-30000, URL: https://gwdg.de/support Sekretariat: Tel.: +49 551 39-30001, E-Mail: gwdg(a)gwdg.de Geschäftsführer: Prof. Dr. Ramin Yahyapour Aufsichtsratsvorsitzender: Prof. Dr. Norbert Lossau Sitz der Gesellschaft: Göttingen Registergericht: Göttingen, Handelsregister-Nr. B 598 --------------------------------------- Zertifiziert nach ISO 9001 ---------------------------------------

4 9

Sorry, your Google login failed
by tony.h 18 Jan '23

18 Jan '23

Greetings, I'm having trouble getting the Google login to work since upgrading/rebuilding Koha (we rebuilt the VPS and followed the install guide: https://wiki.koha-community.org/wiki/Debian) *The problem:* 1) I can log in through my local account, no problem. 2) I then try to login through my Google account 3) After pressing allow from the accounts.google.com site, a message is displayed: /Sorry, your Google login failed. .../ The full message is below. "Log in to your account Google login Sorry, your Google login failed. The email address you are trying to use is not associated with a borrower at this library. Please note that the Google login will only work if you are using the e-mail address registered with this library. If you want to, you can try to log in using a different account Log in with Google If you do not have a Google account, but do have a local account, you can still log in:" There are no errors in the Apache log files. *Configuration* Since we had troubles, I'm following the testing guide to configure the OAuth login: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10988#c68 I removed the Google OAuth entries: DELETE FROM systempreferences WHERE variable LIKE 'GoogleO%'; I then ran the upgrade schema tool, as I did when I imported the db: sudo koha-upgrade-schema keiin_lib I added values back in admin panel (Home › Administration › System preferences > Google OpenID Connect I confirmed the 4 values are displayed in the MySQL DB: SELECT * FROM systempreferences WHERE variable LIKE 'GoogleO%'; Any thoughts? Tony -- View this message in context: http://koha.1045719.n5.nabble.com/Sorry-your-Google-login-failed-tp5895227.… Sent from the Koha-general mailing list archive at Nabble.com.

5 5

Koha releases are available 🎁
by Mason James 16 Jan '23

16 Jan '23

kia ora community, the latest Koha packages and tarballs are ready release notes are here... https://koha-community.org/koha-21-11-03-released https://koha-community.org/koha-21-05-11-released https://koha-community.org/koha-20-11-15-released https://koha-community.org/koha-19-11-26-released cheers, Mason

2 2

Cannot add biblio records
by Παναγιώτης Θ 05 Jan '23

05 Jan '23

Hello to everyone, I am installing Koha for the first time in a local theological library and I would very much appreciate your help. The task I was delegated to, is transfering an custom local library database, based on Unimarc, to Koha. I have installed Ububtu 22.04 in a VM and installed Koha with UNIMARC flavor without any errors. After transforming biblio and authorities records from the old db, using MarcEdit, in a form and type so that can be added to Koha, I encountered the following problem: All biblio records (using Stage MARC records for import tool) seem to be held in reservoir and do not appear in the catalog. Inspecting further the problem, I discovered that I cannot add a biblio record manualy, either!!! I have searched in previous mails in the list many hours and on the internet but I havent found anything similar. I followed tutorials and documentation but I still can't add any biblio record. The volume of new information is really big and maybe It is something simple that I am missing but really I cannot understand this behaviour. This is my setup Koha version: 22.05.00.000 OS version ('uname -a'): Linux panais-virtual-machine 5.15.0-52-generic #58-Ubuntu SMP Thu Oct 13 08:03:55 UTC 2022 x86_64 Perl interpreter: /usr/bin/perl Perl version: 5.034000 Perl @INC: /usr/share/koha/lib /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.34.0 /usr/local/share/perl/5.34.0 /usr/lib/x86_64-linux-gnu/perl5/5.34 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.34 /usr/share/perl/5.34 /usr/local/lib/site_perl /var/lib/koha/library3/plugins MySQL version: mysql Ver 8.0.31-0ubuntu0.22.04.1 for Linux on x86_64 ((Ubuntu)) Apache version: Server version: Apache/2.4.52 (Ubuntu) Memcached: Servers: 127.0.0.1:11211 | Namespace: koha_library3 | Status: running. | Config read from: koha-conf.xml Zebra version: Zebra 2.2.3 (C) 1994-2020, Index Data Zebra is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. SHA1 ID: 6deac2408d36773b991ada867da4a9393bcc658e Using ICU Zebra status: Running Message broker: Using RabbitMQ Date and time: 11/08/2022 15:06 Time zone: Used: Europe/Athens | Config: Undefined | Environment (TZ): Undefined I look forward to any kind of help, It has been the last month that I am trying to setup Koha and I have to admit that I am really overwhelmed with this staff that is definitely very new to me. I have a IT background and work with a librarian that helps me with the library glossary part. Thanks again for your time, Panagiotis PS. Koha's features are really exciting and hope we can manage to make the transition!

3 2

Patron search not working after upgrade to version 22
by Evan Stewart 06 Dec '22

06 Dec '22

Hello, I recently upgraded my Koka 21 to 22. Everything seemed to be working fine until I tried searching for patrons. Using the intranet portal to search for patrons provides zero results. I see my patrons in the borrowers table, but the GUI won't display them. It's like the search function sees no results. I upgraded to version 22.05.02, but the same problem still occurs. I'm using Raspberry Pi OS (Buster). I can add a new patron, but even the new patron does not show in the search results. Is there a way to refresh the indexer that handles patron searching? Any other suggestions? -Evan Stewart Africa's Hope, USA

5 15

Another DBI Exception for foreign key constraint in upgrade to Koha
by David L. Whelchel 05 Dec '22

05 Dec '22

Hi, The following message was sent and held by the moderator as being too long ten days ago. I have been unable to update to the current version because of this issue. I have removed the detail about the environment and installation that I included and that are usually asked for in a bug report. I will send the details if they are wanted Hi All, It seems like that for every other update I experience a DBI Exception in the update process. In the latest upgrade of 22.05.04-1 to 22.05.05-1 I have received the message: Upgrade to 22.05.04.002 [14:33:32]: Bug 31086 - Do not allow null values in branchcodes for reserves ERROR - {UNKNOWN}: DBI Exception: DBD::mysql::db do failed: Cannot change column 'branchcode': used in a foreign key constraint 'reserves_ibfk_4' at /usr/share/koha/lib/C4/Installer.pm line 739 Indeed, there are null values for branchcodes in the reserves table as I do not have any courses or reserves in my system. Is there a fix for this error? I have included the console log below: Thanks --Dave ------------------------------------------------------------------------------- David L. Whelchel 725 SE Derby Street Pullman, WA 99163 whelchel(a)pullman.com

7 8