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

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

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

Request for Libraries using Koha to participate in the 2021 Library Automation Perceptions survey
by Marshall Breeding 03 Nov '22

03 Nov '22

To all libraries using Koha: I'm collecting data for the 2021 edition of the International Library Automation Perceptions survey. This survey, conducted annually since 2007, provides an opportunity for libraries to register their perceptions of the strategic automation products they use, organizations that provide these products, and the quality of support delivered. The survey also probes at considerations for migrating to new systems and the level of interest in open source products. As open source software supported both by the general community and by a variety of different service organizations, some special considerations apply to Koha. In the libraries.org directory, Koha is represented by a combination of the name Koha and the primary support organization involved. (For example Koha - Catalyst IT, Koha -- ByWater Solutions). Libraries relying entirely on community support or internal resources are represented as Koha - Independent. If there are any special support arrangements not covered by these conventions, just mention that in the comments area of the survey. In this way the survey will be able to reflect both the functionality of the Koha software and the quality of support provided. This model of representing libraries using Koha isn't perfect, but is a pragmatic approach that aggregates all users of Koha while also segregating the different support scenarios. Participation in this survey will help amplify the visibility of Koha among those interested in library automation. While the numeric rating scales support the statistical results of the study, it's the comments offered that provide the most insight into the current state of library automation satisfaction. Comments will be published in the survey results, redacted to conceal text that might identify the individual or organization responding. The raw data for the survey will not be shared, but reports are available that provide a variety of ways to view results. Please help your fellow librarians who might be in the process of evaluating library automation options by responding to the survey. Any information regarding vendor performance and product quality can be helpful when making strategic decisions regarding automation alternatives. A large number of responses strengthen the impact of the survey and the subsequent report. If you have responded in previous years, please respond again this year to help identify any trends regarding improvement or worsening of the products or support services. For more information about the survey, for instructions on how to participate, and to see results of previous year's survey reports, see: https://librarytechnology.org/perceptions/2021/invite/ I hope that all libraries using Koha will respond. Feel free to forward this request to any other library-related list. You can view the report summarizing the results of last year's survey, including data from all previous editions, here: https://librarytechnology.org/perceptions/2020/ Please let me know if there are any questions regarding the survey. Marshall Breeding Editor, Library Technology Guides www.librarytechnology.org Marshall.breeding(a)librarytechnology.org twitter.com/mbreeding

1 1

Error
by Himanshu Aggarwal 20 Jun '22

20 Jun '22

While doing batch record modification I am getting following error Cannot enqueue this job. (The error was: Job has not been enqueued. See the Koha logfile for more information). Kindly help -- Assistant Librarian, Confucius Institute Scholar 13-14, R.D. National College, Bandra (W.)

4 7

Koha on Debian 10
by Clogher Historical Society 09 Jun '22

09 Jun '22

Hi, Thanks for the replies, it seems that I need to be running Debian 9 ( Stretch) not version 10 (Buster) but there is someone called: mtj on IRC who is working on Debian 10. There doesn't seem to be a downgrade option in Debian so reinstalling the whole operating system is pretty awkward. I hope (MTJ) includes Debian 10 support soon. Best Regards, Aindriú

5 7

plack with koha soruce package
by vinod kumar 21 Apr '22

21 Apr '22

Hello Friends, I am a library professional and have been using Koha in my library for the last 2 years. I have Koha 20.05.05 installed on Ubuntu 20.04. I have installed Koha using source tar package and not using koha-common installation. I have studied various koha articles to use in Koha to boost speed. But in all articles, enabling plack steps given only for koha-common installation only, using koha-plack command. In my case, I have installed Koha using tar source package, so no such commands were found. Can Anyone guide me how to enable the plack package for Koha tar source package installation. I will be thankful to you. Thanks,

2 4

Switching Koha to ElasticSearch... any problems?
by Mason James 13 Apr '22

13 Apr '22

hi Folks does anyone have any experience running Koha with ES? i've done some basic testing (on 20.11) - it seems to work well and its speed is impressive! (🦄 + 🌈) - is it generally safe to run in production? - any major problems, or missing areas of functionality? any advice or info would be welcomed cheers, Mason

4 3

Database upgrade problems from KOHA 19.05 to KOHA 21.11
by Harald Schaefer 01 Apr '22

01 Apr '22

Dear all, now I am promoted from a plain KOHA user to the system administrator of the computer hosting a KOHA installation of a railway museum in Germany. My first task was to upgrade the system from Ubuntu 16.04 to 20.04 and upgrading the KOHA system. I have tried this first twice on some local copies. In the test runs the database upgrade works fine. In the update run of the production system it stops at this point: Upgrade to 20.12.00.049 [19:01:13]: Bug 28108 - Move action logs 'SERIAL CLAIM' and 'ACQUISITION CLAIM' to a new 'CLAIMS' module Upgrade to 20.12.00.050 [19:01:13]: Bug 28108 - Add new systempreference OpacHiddenItemsHidesRecord Upgrade to 21.05.00.000 [19:01:13]: Koha 21.05.00 release Log started: 2022-03-29 19:04:34 # some other program In thetest runs it continues Upgrade to 21.05.00.000 [17:49:33]: Koha 21.05.00 release Upgrade to 21.06.00.000 [17:49:33]: Increase DBRev for 21.06  Run, rabbit run.  Dig that hole, forget the sun, And when at last the work is done Don't sit down it's time to dig another one. The rabbitmq log show these entries for the time 2022-03-29 19:00:36.018 [info] <0.595.0> started TCP listener on [::]:5672 2022-03-29 19:00:36.018 [info] <0.266.0> Running boot step cluster_name defined by app rabbit 2022-03-29 19:00:36.018 [info] <0.266.0> Running boot step direct_client defined by app rabbit 2022-03-29 19:00:36.158 [notice] <0.103.0> Changed loghwm of /var/log/rabbitmq/rabbit(a)tools.log to 50 2022-03-29 19:00:36.496 [info] <0.8.0> Server startup complete; 0 plugins started. 2022-03-29 19:03:25.195 [info] <0.777.0> rabbit_stomp: default user 'guest' enabled 2022-03-29 19:03:25.281 [info] <0.793.0> started STOMP TCP listener on [::]:61613 2022-03-29 19:03:25.329 [info] <0.765.0> Plugins changed; enabled [amqp_client,rabbitmq_stomp] 2022-03-29 19:03:27.678 [info] <0.800.0> RabbitMQ is asked to stop... Is there any way to continue the database upgrade? I have other applications running on the system and I do not want to start the complete upgrade process again. It seems that the not executed scripts are in /usr/share/koha/intranet/cgi-bin/installer/data/mysql/db_revs Basically the upgraded KOHA is running. Best regards Harald

4 6

Koha version 21.11.01 error 500 when saving authoratie
by Pedro Miguel Nunes Ferreira 01 Apr '22

01 Apr '22

Hello When i try to save an authoraty in the menu /cgi-bin/koha/authorities/authorities-home.pl and i make a change in the field 200, when i save i get error 500, but it saves the authoraity. If i change any other field instead of 200 , for example 300,400....and so on , it works perfectly The error i get in plack-error.log is, Can't call method "tag" on an undefined value at /usr/share/koha/lib/C4/Heading.pm line 69. What could be the problem. Thanks for the help --

1 0