February 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

Fwd: update error
by Katrin Fischer 29 Mar '22

29 Mar '22

Hi Ana, please always keep conversation on the mailing list, so others can help you too. It looks like REGEXP_REPLACE might be a feature only available in newer MySQL versions. It doesn't seem to appear in the 5.7 manual, but only in the 8.0 manual, but I am having trouble finding the version it was introduced in. What OS are you using and is updating the DBMS or switching to MariaDB an option? Katrin -------- Forwarded Message -------- Subject: RE: update error Date: Tue, 4 Jan 2022 12:10:58 +0000 From: anabela semedo <anabela556(a)hotmail.com> To: Katrin Fischer <katrin.fischer.83(a)web.de> Hi Katrin, thanks for your time. I use the mysql, version 5.7.38 I still couldn't solve it. do I have to uninstall everything? Upgrade to 21.05.00.016 [14:16:28]: Bug 24387 - Rename opac_news with additional_contents ERROR: {UNKNOWN}: DBI Exception: DBD::mysql::db do failed: FUNCTION koha.biblioteca.REGEXP_REPLACE does not exist at /usr/share/koha/lib/C4/Installer.pm line 738 Thanks again, Ana Bela *De:*Katrin Fischer [mailto:katrin.fischer.83@web.de] *Enviada:* sábado, 1 de janeiro de 2022 10:53 *Para:* anabela semedo <anabela556(a)hotmail.com>; Koha <koha(a)lists.katipo.co.nz> *Assunto:* Re: update error Hi Ana, better to copy the error into the email as attachments will be removed on the mailing list: Upgrade to 21.05.00.016 [14:16:28]: Bug 24387 - Rename opac_news with additional_contents ERROR: {UNKNOWN}: DBI Exception: DBD::mysql::db do failed: FUNCTION koha.biblioteca.REGEXP_REPLACE does not exist at /usr/share/koha/lib/C4/Installer.pm line 738 Are you using MySQL or MariaDB and which is the version? Katrin On 30.12.21 17:36, anabela semedo wrote: hello ever one i have a problem here, trying to update koha to the latest version and i have this error here that i am not able to resolve. can anybody help me? thankyou. Ana Bela Semedo

3 2

ElasticsearchCrossFields enabled returns no search results on OPAC
by Aleisha Amohia 13 Mar '22

13 Mar '22

Hi all, ElasticsearchCrossFields is a great syspref to enable if you need to search across indexes, for example your search term includes both title and author keywords. We've discovered this only works on the staff client, and returns no results when searching on the OPAC. After some investigation, this is because the OPAC will add a `suppress:false` to the search query, to hide records that are suppressed in OPAC. I'm not sure why, but this combination of suppress:false and ElasticsearchCrossFields means no results are returned in the OPAC. Has anyone seen this before or know a fix, or why it happens? I've reported this bug: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30141 -- 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.

2 3

Biblio_metadata timestamps updating for no reason?
by Bales (US), Tasha R 07 Mar '22

07 Mar '22

Good morning, I’m seeing updated timestamps in biblio_metadata and I can’t figure out why. I’m working on a test system where no updates are taking place, and I am not running any jobs to link authorities to bib records, or any other jobs that should be updating records. What could be causing biblio_metadata timestamps to be updated? For example, I see 200 records updated in the last 30 minutes, and in the Modification Logs for those records, I don’t see any recent logged actions. I’m trying to implement a process that depends on timestamps, and this is throwing me off. I’ve used the “ps aux” and “ps aux | koha” command several times, but don’t see anything obvious, though I might not know what to look for. If you have any ideas, thank you in advance! 😊 Tasha Bales Enterprise Services http://isesi.web.boeing.com/

2 2

C4::Heading::MARC21
by Thomas Klausner 03 Mar '22

03 Mar '22

Hi! A few days ago I asked this in IRC, but got no response, so I'm trying here: I have a question regarding C4::Heading::MARC21: https://github.com/Koha-Community/Koha/blob/master/C4/Heading/MARC21.pm#L49 and #167 define some hardcoded mappings which subfields to include/display eg in the popup window when selecting an authority. But we have some data needed to properly identify the correct auth in a subfield that is not included in this mapping (i.e. 150g). Would you accept additions to these mapping in upstream? Or do we have to patch our local instance? Or could these mapping be moved into some config files? Greetings, domm -- #!/usr/bin/perl https://domm.plix.at for(ref bless{},just'another'perl'hacker){s-:+-$"-g&&print$_.$/}

2 2