- Koha - lists.katipo.co.nz

Open Ended Due Dates, Permanent Loans, Etc.
by Charles Kelley 16 Sep '21

16 Sep '21

Hi, all! Is there a way to make an open ended due date? That is, if a person checks out a book, Koha does not assign a due date, *per se*, rather it merely marks it checked-out. I guess this be might be considered a permanent or semi-permanent loan but it would not be a transfer. Mind you, if a patron puts a hold on such a book, the patron who checked out the book would have to surrender it. The book would still be one of the library's holdings so that the library can avail it to the patrons and track it for property management reasons. (The OPAC would list it only *CHECKED OUT* or *BORROWED*.) Mind you, I am trying to avoid a proliferation and plethora of LOCs and CCODEs. I know this is a nightmare and it defeats the purpose of a library of shareable works. It would be rarely used, of course, but I can imagine a scenario in which it would arise. Many thanks, all! -- 気を付けて。 /ki wo tukete/ = Take care. -- Charles. Charles Kelley, MLS PSC 704 Box 1029 APO AP 96338 Charles Kelley Tsukimino 1-Chome 5-2 Tsukimino Gaadenia #210 Yamato-shi, Kanagawa-ken 〒242-0002 JAPAN +1-301-741-7122 [US cell] +81-80-4356-2178 [JPN cell] mnogojazyk(a)aol.com [h] cmkelleymls(a)gmail.com [p] linkedin.com/in/cmkelleymls <http://www.linkedin.com/in/cmkelleymls> Meeting Your Information Needs. Virtually.

2 1

Time to translate: string freeze to prepare 20.11.10 release
by Fridolin SOMERS 16 Sep '21

16 Sep '21

Hi, String freeze is into effect 🥶 The 20.11.x maintenance branch is preparing for 20.11.10 release 📦 This means it's the right time to head over to the translation platform: https://translate.koha-community.org/projects/ Keep in mind that translations must be done with priority on higher version 21.05 🔥 Happy translating 🌎🌍🌏 -- Fridolin SOMERS <fridolin.somers(a)biblibre.com> Software and system maintainer 🦄 BibLibre, France

1 0

Re: [Koha] How to Update and Upgrade Koha
by Charles Kelley 16 Sep '21

16 Sep '21

Hello, all! In our latest exchange, on 16 Sept. 2021 at 09:00 [JST], I received the following from Hector Gonzalez Jaime <cacho(a)genac.org>: [Originally 15 Sept. 2021 at 18:25]: Hi, as with anything else, you should first have a good (tested) backup of > everything. Koha, server software, and database. > > Then, if you used the debian packages, you should check which version you > are "tracking", something like: > > grep -Ri koha /etc/apt/* > > would return something like: > > /etc/apt/sources.list.d/koha.list:deb > http://debian.koha-community.org/koha 19.11 main > > That means there is a file /etc/apt/sources.list.d/koha.list which you > should edit and change to the version you want to track now. The content > of the file would be: > > deb http://debian.koha-community.org/koha 21.05 main > > if you want to track koha 21.05 > > Then you would: > > apt-get update > apt-get upgrade > > and it should do the upgrade. With the following exception, if apt-get > upgrade says it would need to update mariadb-server or mysql-server, then > you should upgrade that first and separately, like this: > > apt-get update > apt-get install mariadb-server-10.3 > apt-get upgrade > > If you don't upgrade mariadb first, it will be DOWN when koha wants to > upgrade the database, leaving you with a half upgraded system. (And using > that backup). > > Hope this helps. > [A few minutes later, at 18:44, he sent this:] I forgot something, if koha requires additional software to be installed, > when you run apt-get upgrade it will say something like this: > > The following packages have been kept back: > koha-common > > In this case, you will need to do: > > apt-get dist-upgrade > > which will install the needed packages and then it will upgrade koha. > Many thanks! This will help enormously. We will be upgrading on a test/demonstration/development machine before we do so to the production machine. I've been involved in upgrades and updates of too many other software packages to know not to do so on the production machine right off. Only after the staff are satisfied that the test machine functions properly is the production machine updated or upgraded. Thanks again! -- 気を付けて。 /ki wo tukete/ = Take care. -- Charles. Charles Kelley, MLS PSC 704 Box 1029 APO AP 96338 Charles Kelley Tsukimino 1-Chome 5-2 Tsukimino Gaadenia #210 Yamato-shi, Kanagawa-ken 〒242-0002 JAPAN +1-301-741-7122 [US cell] +81-80-4356-2178 [JPN cell] mnogojazyk(a)aol.com [h] cmkelleymls(a)gmail.com [p] linkedin.com/in/cmkelleymls <http://www.linkedin.com/in/cmkelleymls> Meeting Your Information Needs. Virtually.

1 0

New community member introduction and question
by david＠penkler.net 15 Sep '21

15 Sep '21

Hi, I work as a volunteer in a non-profit association that runs the library for culture and religion at the Theological Centre in Meylan near Grenoble in France. My main task is cataloguing. We receive many books through book donations and bequests with the result that we have a large number of duplicates (circa 2500 books out of some 40000). We are setting up a framework to sell the duplicates for a token amount. To this end we have added a item.notforloan value "For Sale" which we use to generate a report of books for sale from which we create a virtual shelf that can be consulted by the patrons. I am trying to figure out how to add a "Price" column with items.price to the Holdings tab of the opac details page for folks viewing the "For Sale" virtual shelf in the "Normal View". The price is shown in the "Marc view". Any advice is gratefully accepted. Thanks, -David Penkler

3 4

Cannot see Google Login Link
by Mihai Rosu 14 Sep '21

14 Sep '21

Hi Everyone, I used the following guides to attempt to get Google Authentication to work on a Koha installation: https://sjamso.blogspot.com/2020/01/koha-and-googles-oauth-20-api-to.html#c… and https://koha-community.org/manual/17.05/html/02_administration.html?highlig… However, I cannot seem to be able to get the Google Login link to show up on the Login page. Does anyone have any ideas what the issue may be? Thank you, Mihai Rosu Rudolf Steiner Branch Chicago 4249 N. Lincoln Ave Chicago, IL 60618-1953 mrosu(a)rschicago.org 773.562.6254 www.rschicago.org

2 9

Unable to login in Web Installer 21.5
by Sanjay Uchcharia 14 Sep '21

14 Sep '21

Sir, I've installed Koha on Ubuntu 20.04 but I'm unable to login in Web Installer 21.5 with the username & password.

5 4

Re: [Koha] Batch check outs timing out after upgrade and migration
by Matthew Lindfield Seager 14 Sep '21

14 Sep '21

Hi Katrin, Memcached is installed and running according to the About Koha page. Following the second lot of instructions at https://wiki.koha-community.org/wiki/Troubleshooting_memcached I can see that it has been handling requests. I also compared the old server (post upgrade to 21.05) with the new server and both have the same configuration in `/etc/memcached.conf`. According to the about page configuration is coming from koha-conf.xml but I'm not sure where to find that file (and it doesn't seem like Memcached is the culprit so I didn't bother installing mlocate to find it). The only mentions of Plack I can see are on the Perl Modules info page: - Plack::Middleware::ReverseProxy (0.14) - 0.16 - Plack::Middleware::LogWarn (0.001002) - 0.001002 I could not find any info in the Wiki about Plack other than the ~2017 Plack page <https://wiki.koha-community.org/wiki/Plack> and a brief mention on the Performance page <https://wiki.koha-community.org/wiki/Performance>. Is there anything I need to do to enable it? Both old and new server have a single warning on the System information tab: "System preference 'KohaAdminEmailAddress' does not contain a valid email address. Emails will not be sent." Comparing the Server Information page for the old server (which is super slow after the 21.05 upgrade but doesn't time out) with the new server (which is super slow AND times out), the only differences are: - Minor Koha version (old server is 21.05.02.003, new server is 21.05.03.001) - Slightly different kernel release and version (old is 5.4.0-84-generic, #94-Ubuntu; new is 5.4.0-81-generic, #91-Ubuntu) - Different MySQL versions (old is "mysql Ver 15.1 Distrib 10.3.31-MariaDB, for debian-linux-gnu (x86_64) using readline 5.2", new is "mysql Ver 8.0.26-0ubuntu0.20.04.2 for Linux on x86_64 ((Ubuntu))" Thanks so much for some additional places to look for issues! If something in there gives a clue or if anyone has any other suggestions for things to check I'm all ears! Matt On Mon, 13 Sept 2021 at 07:01, <koha-request(a)lists.katipo.co.nz> wrote: > Date: Sun, 12 Sep 2021 12:46:57 +0200 > From: Katrin Fischer <katrin.fischer.83(a)web.de> > To: koha(a)lists.katipo.co.nz > Subject: Re: [Koha] Batch check outs timing out after upgrade and > migration > Message-ID: <219ecc3c-ed9a-d27c-7074-962422505f80(a)web.de> > Content-Type: text/plain; charset=utf-8; format=flowed > > Hi Matthew, > > is there anything on the "About Koha" page that might give a clue? > > * Is Memcached running? > * Is Plack configured and running? > * Is there any error or warning displayed on the System information tab? > > Hope this helps, > > Katrin >

3 4

Call for news - Newsletter September 2021
by Koha Newsletter 13 Sep '21

13 Sep '21

Hi I'm collecting news for the September 2021 Koha Community Newsletter. Please send anything noteworthy to: kohanews (at) gmail (dot) com News criteria: * News items can be of any length. * Images are fine. * Anything and everything Koha. * Submit by the 26th of the month. Text format criteria: * Just structured plain text, or * HTML text to include tables or similar For events: * Consider adding your event to the Koha Community calendar at https://koha-community.org/calendar/ Thank you! Michael Kuhn Editor, Koha Community Newsletter

1 0

Import in koha 21.05 all users from LDAP
by Tadas G 13 Sep '21

13 Sep '21

Hello, We have Koha 21.05 installed and configured to work with AD. Everything is fine, users can login to Koha using AD credentials, but in Patron list they appear only after successful authorisation. It is quite annoying, because if you want to assign book to the reader, he/she has to be in patron list. Is it possible to create Cron job to import users to patron list automatically from AD (it is enough to import only a few fields, all other fields can be updated after user login)? Thanks for the answers

4 3

Batch check outs timing out after upgrade and migration
by Matthew Lindfield Seager 12 Sep '21

12 Sep '21

Hi All, I'm a Koha newbie so I hope this is the appropriate forum for this question, please let me know if not! I'm the ICT Manager in a small school in Phnom Penh that had a working Koha installation. One of our physical servers died and, rather than replace it to get back up to full redundancy, we decided to move our on-prem servers to an IaaS provider (Linode). In the process of restoring Koha onto the new server I discovered we were running Koha 20.05 on the old server and 21.05 on the new server. I then made the fateful mistake of proceeding with both changes at once (despite knowing better 😔). I upgraded the old server to 21.05 and then backed up and restored onto the new server (both Ubuntu 20.04 LTS). I also added TLS using Let's Encrypt at the same time. It all seemed to go smoothly but we're now experiencing slow performance when checking out and looking up patrons and we're getting gateway timeouts when we try to use Batch Check Out. Does anyone have any tips on how to troubleshoot this? So far I've: - checked specs (new server is a "dedicated" 4GB VM with specs equivalent to or better than the old server) - tried to find any configuration differences between the old server and the new server - looked through the wiki pages on performance <https://wiki.koha-community.org/wiki/Performance> and tuning <https://wiki.koha-community.org/wiki/Koha_Tuning_Guide> to see if there's anything we'd done on the old server but not on the new In the process I discovered that the old server was running on MariaDB 10.3.31 whereas I installed MySQL 8.0.26 on the new server. Could that be the source of all our issues or is that a red herring? To rule out MariaDB as the issue I've tried backing up the new server and restoring it on to an even newer server with MariaDB installed but so far I've not been successful in getting Koha running on MariaDB, despite successfully running the restore (after adjusting the SQL dump to change from MySQL's `utf8mb4_0900_ai_ci` collation to MariaDB's `utf8mb4_general_ci `). Has anyone got any nuggets of wisdom? I fear our next best option might be to create a new (MariaDB) server from the original back ups and manually re-enter the past 4 days worth of borrowing and returns 😔 Regards, Matt

2 1