April 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

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

Moving Curbside Pickup plugin to Koha core
by Jonathan Druart 07 Jul '22

07 Jul '22

Hello, I have been sponsored to move the Curbside Pickup plugin to Koha core. If you are using this plugin and have enhancement requests or want to highlight some existing bugs, let us know on the bug report. https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30650 I am aware of the different issues opened on the github repository of the project and will take them into account as much as I can. Regards, Jonathan

1 1

Export tool failure Koha 21.11.03.000
by Evan Stewart 21 Jun '22

21 Jun '22

Hello, I seem to be having a problem with the Export data tool (Tools > Export Data). When I click the Export link, I get a "503 Service Unavailable" message. All other tools I try are working fine. I'm running Koha on AWS (see details below). My local server versions of Koha (running on Debian) are working fine. Just the AWS install is having the export tool failure. Has anyone experienced this problem with exporting data? Hosting Environment: AWS Lightsail, 2GB RAM OS: Debian 10 Koha: 21.11.04.001 Server: Apache 2.4.38 Any thoughts on how to troubleshoot to discover the cause? Thanks, Evan Stewart

3 4

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

Koha 22.05 release dates
by Fridolin SOMERS 09 May '22

09 May '22

Hi dear community, Here is the timeline for the 22.05 major release: * April 29 - "Soft" feature freeze : nothing big or with high risk of side-effects will be included into the final release if not marked as Passed QA * Mai 6 - "Hard" feature freeze : nothing considered as an improvement will be pushed if not marked as Passed QA * Mai 11 - String freeze : draft of release notes published * Mai 18 - Beta : Only bug fixes considered major, critical or blocker will be pushed * Mai 26 - Final release Let me know if you have any request ;) -- Fridolin SOMERS <fridolin.somers(a)biblibre.com> Software and system maintainer 🦄 BibLibre, France

3 4