February 2023 - 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

Koha and IPV6
by Michael Kuhn 28 Apr '23

28 Apr '23

Hi Our library can access the the future virtual machine running Koha only via IPV6. I coulnd't find the terms IPV4 or IPV6 neither in https://wiki.koha-community.org/wiki/System_requirements_and_recommendations nor in the current Koha manual. Thus my question (since until now I have implemented only Koha-installations with IPV4): Is Koha able to run just with IPV6 addresses, also when using Let's Encrypt? Are there maybe some caveats? 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

3 3

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

500 Internal Server Error
by Thomas Daly 13 Mar '23

13 Mar '23

I'm finding that the Koha instance's intranet site is crashing with an Internal Server Error. It first happened when I tried to change the superlibrarian's user ID. I couldn't recover the system at all, and had to delete and re-create the instance. It has recurred in the installer when selecting the language. Log files are being filled with repeated errors about missing database tables, e.g. indexer-output.log: DBD::mysql::st execute failed: Table 'koha_zilib.zebraqueue' doesn't exist at /usr/share/koha/lib/Koha/Database.pm line 152. DBD::mysql::st fetchrow_arrayref failed: fetch() without execute() at /usr/share/koha/lib/Koha/Database.pm line 152. DBD::mysql::st execute failed: Table 'koha_zilib.zebraqueue' doesn't exist at /usr/share/koha/lib/Koha/Database.pm line 152. DBD::mysql::st fetchrow_arrayref failed: fetch() without execute() at /usr/share/koha/lib/Koha/Database.pm line 152. plack-intranet-error.log: [2023/02/27 14:28:08] [WARN] DBD::mysql::st fetchrow_hashref failed: fetch() without execute() at /usr/share/koha/lib/Koha/Database.pm line 152. [2023/02/27 14:28:08] [WARN] DBD::mysql::st execute failed: Table 'koha_zilib.language_descriptions' doesn't exist at /usr/share/koha/lib/Koha/Database.pm line 152. [2023/02/27 14:28:08] [WARN] DBD::mysql::st fetchrow_hashref failed: fetch() without execute() at /usr/share/koha/lib/Koha/Database.pm line 152. [2023/02/27 14:28:08] [WARN] DBD::mysql::st execute failed: Table 'koha_zilib.language_descriptions' doesn't exist at /usr/share/koha/lib/Koha/Database.pm line 152. [2023/02/27 14:28:08] [WARN] DBD::mysql::st fetchrow_hashref failed: fetch() without execute() at /usr/share/koha/lib/Koha/Database.pm line 152. [2023/02/27 14:28:08] [WARN] DBD::mysql::st execute failed: Table 'koha_zilib.systempreferences' doesn't exist at /usr/share/koha/lib/Koha/Database.pm line 152. [2023/02/27 14:28:08] [WARN] DBD::mysql::st execute failed: Table 'koha_zilib.systempreferences' doesn't exist at /usr/share/koha/lib/Koha/Database.pm line 152. [2023/02/27 14:28:08] [WARN] DBD::mysql::st execute failed: Table 'koha_zilib.systempreferences' doesn't exist at /usr/share/koha/lib/Koha/Database.pm line 152. [2023/02/27 14:28:08] [WARN] DBD::mysql::st execute failed: Table 'koha_zilib.systempreferences' doesn't exist at /usr/share/koha/lib/Koha/Database.pm line 152. [2023/02/27 14:28:08] [WARN] Install required, redirecting to Installer at /usr/share/koha/lib/C4/Auth.pm line 762. plack-error.log: DBD::mysql::st execute failed: Table 'koha_zilib.systempreferences' doesn't exist at /usr/share/koha/lib/Koha/Database.pm line 152. DBD::mysql::st execute failed: Table 'koha_zilib.systempreferences' doesn't exist at /usr/share/koha/lib/Koha/Database.pm line 152. Template process failed: file error - /usr/share/koha/intranet/htdocs/intranet-tmpl/prog/en-GB/modules/installer/s tep1.tt: not found at /usr/share/koha/lib/C4/Templates.pm line 127. Template process failed: file error - /usr/share/koha/intranet/htdocs/intranet-tmpl/prog/en-GB/modules/installer/s tep1.tt: not found at /usr/share/koha/lib/C4/Templates.pm line 127. Any help appreciated.

1 1

Can't delete fresh created biblio. DBI Exception: DBD::mysql::db do failed: Duplicate entry
by DHIM IT 12 Mar '23

12 Mar '23

Dear colleagues, I have problem on one of koha instance Version 22.05.09.000. If I try to delete some biblio, fresh created too, I get this error: An error has occurred! Error 500 From: /var/log/koha/koha/plack-error.log {UNKNOWN}: DBI Exception: DBD::mysql::db do failed: Duplicate entry '61703-marcxml-MARC21' for key 'deletedbiblio_metadata_uniq_key' at /usr/share/koha/lib/C4/Biblio.pm line 2867 At the same time biblio landed in to the table deletedbiblio. After deleting of record from deletedbiblio and trying to delete the record again, it works. Maybe have somebody idea about the error? Mit besten Grüßen IT-Manager Eugen Bastron

3 5

Can the Koha Mailing List and DMARC become friends?
by David Liddle 09 Mar '23

09 Mar '23

Greetings, all! At the encouragement of one of the mailing list administrators, I would like to present a situation and a proposal to you all. Normally, I would write from my work account, david.liddle(a)wycliff.de, since one of the hats I wear is that of a Koha system administrator. One of my other hats, however, is that of the email administrator for our corporate domains. And the latter hat has precedence over the former. To help protect our email domains from being used fraudulently, I have implemented DMARC policies according to current recommendations. You can read more about the Domain-based Message Authentication, Reporting & Conformance protocol at https://dmarc.org/. The policies direct that only messages from authorized sources should be allowed to send mail from wycliff.de and our other domains; messages from all unauthorized sources should be quarantined. With DMARC policies in place, messages that I send from my work account to the Koha mailing list get quarantined by email providers that comply with the policies' directives. Why? It happens because the Koha mailing list spoofs the email address of the original sender. As a result, there is a significant number of subscribers who did not receive the messages at all or had to fetch them from quarantine. Some unknown number will have been marked as spam. There are well-meaning reasons for this behavior within an honest, friendly community such as the Koha mailing list. However, email spoofing is one of the chief means by which fraudsters engage in phishing, data exfiltration, and ransomware attacks. In my opinion, the Koha community ought to avoid the practice of email spoofing. Therefore, I have a proposal to make: -- The Koha Mailing List is based on the Mailman list system. According to its release notes, Mailman 2.1 supports what the developers call "DMARC mitigations". -- Mailman DMARC Mitigations are described here: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/handlers/d… ++ I PROPOSE that the mailing list subscribers support the implementation of DMARC mitigations to the Koha mailing list. -- The result of the implementation would be that messages submitted to the list would no longer spoof the sender's address, but rather be altered so that the messages come from the list's own address, koha(a)lists.katipo.co.nz. They *should* be delivered successfully to all recipients. A reply to the message would return to the list, and a reply to all could include the original sender's address explicitly. -- If you agree (or disagree) with this proposal, you'll need to indicate that in your own clever way, because there's no voting mechanism in a mailing list. Thank you for being so kind and forbearing as to read this far! I hope that you'll give my proposal your earnest consideration. Regards, David Liddle After-credits scene: For you intrepid readers, I would like to boldly suggest something even more daring than changing the list's sending practices. Please consider changing the platforms of the Koha email and chat discussions to one such as Discourse: -- The Discourse software and community seems to have a fair bit in common with the character and nature of Koha's. You can read more about the platform at https://www.discourse.org/. -- Not only is it a web forum, but it can handle email submissions, replies, notifications, and digests. (And it would always send from a legitimate address.) -- It has migration tools that appear able to import archives such as those used by this list. -- It has chat integration for real-time messaging that can also be perused later. -- It has functions for search, categorization, and groups that a mailing list does not.

5 5

Modify Patron Transaction Invoices and Fee Receipts
by Ms. Naveen Ali 09 Mar '23

09 Mar '23

Dear members, I'd like to modify the Patron Transaction Invoices and Fee Receipts. In fact all the print options available on the Patron Screen (Summary, Slip, Quick Slip, Overdues, Check In Slip) I can't identify them in the Notices and Slips Tool Please provide support. With best regards, Naveen Ali ITM-JE (EAKL) Inst Representative for HEC Digital Library Resources. NEDUET, Karachi.

5 7

KOHA upgrade error
by zen zenitram 03 Mar '23

03 Mar '23

Good morning all, we are trying to upgrade our koha database but too many duplicate entry shows. ERROR - {UNKNOWN}: DBI Exception: DBD::mysql::db do failed: Duplicate entry 'ar' for key 'PRIMARY' at /usr/share/koha/lib/C4/Installer.pm line 739 This is the first error i encountered when upgrading koha from v20.05 to the latest version that is 22.11 and i already found the fix. The next error is " ERROR - {UNKNOWN}: DBI Exception: DBD::mysql::db do failed: Duplicate entry '20534' for key 'import_biblios.PRIMARY' at /usr/share/koha/lib/C4/Installer.pm line 739". we tried to locate this duplicate entry and it points to biblios in reservoir entry. Anyone of you encountered this kind of error while upgrading? I need help on how we gonna fix it. Thank you!

2 1