- Koha - lists.katipo.co.nz

502 apache error
by vinod mishra 14 Sep '20

14 Sep '20

Hello I have upgraded Koha 16.11 to 20.05, on Ubuntu 18.04 with Mariadb 10.4. Everything is fine but Koha stops working sometime with the below error, however some network related work is going on in our computer center where Koha server is managed by them. All the applications are working like institute website, library website, etc. but only Koha is having the problem below. May I know if this is a Koha related issue or any network issue? The proxy server received an invalid response from an upstream server. The proxy server could not handle the request Reason: Error reading from remote server Apache/2.4.29 (Ubuntu) Server at 192.168.1.134 Port 80 With Regards, Vinod Kumar Mishra, Assistant Librarian, Biju Patnaik Central Library (BPCL), NIT Rourkela, Sundergadh-769008, Odisha, India. Mob:91+9439420860 URL: http://vinod.itshelp.co.in/ ORCID ID: http://orcid.org/0000-0003-4666-7874 *"Spiritual relationship is far more precious than physical. Physical relationship divorced from spiritual is body without soul" -- Mahatma Gandhi*

1 0

Digital Library Training
by mohan pradhan 14 Sep '20

14 Sep '20

VuFind Software is going to organize a training course on Digital Library. If interested, you are kindly requested to fill-up the* on-line form <https://forms.gle/Ur8ERJ23MX2MpYrXA>* . For details of the course click the *brochure*. <https://drive.google.com/file/d/1xf4obi3RxExVvwuvrefIQL6AsP_S5HLu/view?usp=…> The last date of filling application form is 20th September, 2020. The seat is limited to 25 participants. Based on the application, the successful participants will be announced on 25th September, 2020 and the link for online payment will also be sent to the successful participants in their email. The training course will start from 5th October , 2020. Prof. Mohan Raj Pradhan, Ph. D. Training Coordinator VuFindSoftware web: training.vufnd.org

1 0

Re: [Koha] CKJ and Other Non-Roman Searching
by Charles Kelley 14 Sep '20

14 Sep '20

Hello, all! Please excuse the late response. In our latest exchange, on 12 Sept. 2020 at 9:01 AM, Nicolas Legrand < nicolas.legrand(a)bulac.fr> wrote: A good day, אהלן, こんにちは, > > Ho, mine also :). > 8-) Been there. > [skip, skip, skip] > Tuning Zebra to search CKJ or languages written with arabic script was a real > pain with Zebra, it is a no brainer with Elastic Search. With the ICU module > enabled, it works very well for CKJ and handles glyphe similarities. For > example, the Library of Congress catalogues Farsi with alef maksura U+0649 > instead of yeh U+06CC. We imported the farsi records from the Library of > Congress and we were unable to find the documents searching with a farsi > keyboard yielding the letter yeh. You can parameter Zebra to handle this > and say U+0649 = U+06CC. With Elastic Search and ICU, you don't have to, > it just works. We lost some day the possibilities to search CKJ with Zebra > and didn't understand how to get it back. Zebra is certainly a very good > search engine. But it's weird and hard to tune. We don't even have to > ask ourselves how to tweak Elastic Search to do it. It just works. > > Note that for Chinese, enabling QueryAutoTruncate with Elastic Search may lead > to weird results when you type a full chinese name or title. As of 18.05 > this is the case, I didn't check yet if this improved since then. We enabled > it only when “*” is added at the end of a word > Ugh! Thank you for your account. It will help us as we further implement Kona on our site. We'll be following one of the first rules of software updating: Update or upgrade on a copy. > Best regards, יאללה ביי, それでは、また, > You, too. -- 気を付けて。 /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

Feedback option in OPAC
by vinod mishra 13 Sep '20

13 Sep '20

Hello Seen there is a report Problem option in latest Koha which emphasizes problems only can it be made like feedback? or is there any option so that users can send messages to the library via Koha as the library desk can send messages which populates on the user account on login. Your suggestions please. With Regards, Vinod Kumar Mishra, Assistant Librarian, Biju Patnaik Central Library (BPCL), NIT Rourkela, Sundergadh-769008, Odisha, India. Mob:91+9439420860 URL: http://vinod.itshelp.co.in/ ORCID ID: http://orcid.org/0000-0003-4666-7874 *"Spiritual relationship is far more precious than physical. Physical relationship divorced from spiritual is body without soul" -- Mahatma Gandhi*

1 0

JS Add links out to Wikipedia for authors broken in 19.11 with bug 25237
by Alvaro Cornejo 12 Sep '20

12 Sep '20

Hi After Bug 25237, the JS https://wiki.koha-community.org/wiki/JQuery_Library#Add_links_out_to_Wikipe… stopped working. the bug changed the <h5 ...> for <span ...> - <h5 class="author"> + <span class="results_summary author h3"> - [% IF ( author ) %]<h5 class="author">by <a href="/cgi-bin/koha/opac-search.pl?q=au:[% author |url %]">[% author | html %]</a></h5>[% END %] + [% IF ( author ) %]<span class="results_summary author h3">by <a class="contributors" href="/cgi-bin/koha/ opac-search.pl?q=au:[% author |url %]">[% author | html %]</a></span>[% END %] among others similar changes. This breaks the JS "hook" var names = $('h5.author a').not('.authlink'); How can I hook it to the <span> ? I tried several combinations like var names = $('h3.author a').not('.authlink'); var names = $('result_summary.author a').not('.authlink'); var names = $('getElementsByClassName(' result_summary author h3')[1]').not('.authlink'); But have not succeeded. I´m pretty sure is something trivial but didn't see it Regards Alvaro |----------------------------------------------------------------------------------------| Stay safe / Cuídate/ Reste sécurisé *7* Switch off as you go / Apaga lo que no usas / Débranchez au fur et à mesure. *q *Recycle always / Recicla siempre / Recyclez toujours P Print only if absolutely necessary / Imprime solo si es necesario / Imprimez seulement si nécessaire

2 2

Re: [Koha] CKJ and Other Non-Roman Searching
by Charles Kelley 11 Sep '20

11 Sep '20

Hello, all! In our latest exchange, on 11 Sept. 2020 at 9:01 AM, i.e., on 20 Sept. 2020 at 23:43, Katrin Fischer wrote: By default Koha is not set up to search for records with non-Latin scripts. > You will need to activate ICU and rebuild your Zebra index. See: > > https://wiki.koha-community.org/wiki/ICU_chains_configuration > > Hope this helps, > I'll be looking into configuring ICU chains. Thank you for the clarification. -- 気を付けて。 /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

koha backup issue mariadb 10.4
by vinod mishra 11 Sep '20

11 Sep '20

Hello Installed fresh Koha 20.05 for some testing on ubuntu 18.05 everything seems well but automatic default backup creating in /var/spool/koha/library is missing even running the backup.sh file manually does not generate any backup. Please not 10.4 MariaDB does not allow to set a root password by default as its new feature. With Regards, Vinod Kumar Mishra, Assistant Librarian, Biju Patnaik Central Library (BPCL), NIT Rourkela, Sundergadh-769008, Odisha, India. Mob:91+9439420860 URL: http://vinod.itshelp.co.in/ ORCID ID: http://orcid.org/0000-0003-4666-7874 *"Spiritual relationship is far more precious than physical. Physical relationship divorced from spiritual is body without soul" -- Mahatma Gandhi*

1 0

upgrade stuck (Tē tōia, tē haumatia)
by vinod mishra 11 Sep '20

11 Sep '20

Hello Why upgrade of schema stuck at "(Tē tōia, tē haumatia)" ? however, once I escape and again upgrade it goes well. Is there any problem in escaping and executing the upgrade command again? MariaDB 10.4 and Ubuntu 18.4 koha 20.05 With Regards, Vinod Kumar Mishra, Assistant Librarian, Biju Patnaik Central Library (BPCL), NIT Rourkela, Sundergadh-769008, Odisha, India. Mob:91+9439420860 URL: http://vinod.itshelp.co.in/ ORCID ID: http://orcid.org/0000-0003-4666-7874 *"Spiritual relationship is far more precious than physical. Physical relationship divorced from spiritual is body without soul" -- Mahatma Gandhi*

2 1

CKJ and Other Non-Roman Searching
by Charles Kelley 11 Sep '20

11 Sep '20

Hi, all! My library has an extensive catalog in CJK, Russian, and a few other languages that write in non-Roman writing systems. We can import such records into Koha and export the records from Koha. Provided we make sure the applications (BBEdit, EndNote, Excel, Word, to name a few), browsers (Chrome, Firefox, IE, Safari, etc.), OSs (Linux, Mac OS, and Windows) can handle UTF-8, all is well -- for importing and exporting. But getting Koha to search CJK has been fruitless, and we are terribly frustrated. How does one get Koha to search CJK and Arabic, Cyrillic, Hebrew, and other non-Roman writing systems for that matter)? Koha 20.05 running on Debian 9.4 "Stretch". Many thanks. -- 気を付けて。 /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.

3 2

Re: [Koha] Koha Digest, Vol 179, Issue 10
by mohan pradhan 10 Sep '20

10 Sep '20

VuFind Software is going to organize a training course on Digital Library. If you are interested you are kindly requested to fill-up the* on-line form <https://forms.gle/Ur8ERJ23MX2MpYrXA>* . For details of the course click the *brochure*. <https://drive.google.com/file/d/1xf4obi3RxExVvwuvrefIQL6AsP_S5HLu/view?usp=…> The last date of filling application form is 20th September, 2020. The seat is limited to 25 participants. Based on the application, the successful participants will be announced on 25th September, 2020 and the link for online payment will also be sent to the successful participants in their email. The training course will start from 5th October , 2020. Prof. Mohan Raj Pradhan, Ph. D. Training Coordinator VuFindSoftware web: training.vufnd.org On Thu, Sep 10, 2020 at 5:46 AM <koha-request(a)lists.katipo.co.nz> wrote: > Send Koha mailing list submissions to > koha(a)lists.katipo.co.nz > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.katipo.co.nz/mailman/listinfo/koha > or, via email, send a message with subject or body 'help' to > koha-request(a)lists.katipo.co.nz > > You can reach the person managing the list at > koha-owner(a)lists.katipo.co.nz > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Koha digest..." > > > Today's Topics: > > 1. Upgrade from Koha 3.08.07 (Nigel Titley) > 2. Re: Upgrade from Koha 3.08.07 (Nigel Titley) > 3. Re: Upgrade from Koha 3.08.07 (Nigel Titley) > 4. Re: Upgrade from Koha 3.08.07 (Nigel Titley) > 5. Re: Upgrade from Koha 3.08.07 (Alex Shepherd) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 9 Sep 2020 15:34:04 +0100 > From: Nigel Titley <nigel(a)titley.com> > To: Koha <Koha(a)lists.katipo.co.nz> > Subject: [Koha] Upgrade from Koha 3.08.07 > Message-ID: <267bdf94-19e3-3067-3807-a35cdfd4d013(a)titley.com> > Content-Type: text/plain; charset=utf-8 > > I'm running an extremely antique version of Koha 3.08.07 on Debian Squeeze. > > For various reasons (mainly the fact that the system is enormously > stable) nothing has been upgraded for a long while but it's getting to > the point where I need to upgrade it. I'm planning at the same time to > move Koha off onto a new system running the latest Ubuntu LTS. I'm happy > with installing a brand-new Koha but how do I go about transferring the > data. I've found instructions for shifting the database but will the > database schema upgrade work with that huge a jump? It's not a huge > library, just a couple of thousand books. > > Thanks for any help that anyone can offer. > > Nigel > > > ------------------------------ > > Message: 2 > Date: Wed, 9 Sep 2020 15:53:05 +0100 > From: Nigel Titley <nigel(a)titley.com> > To: koha(a)lists.katipo.co.nz > Subject: Re: [Koha] Upgrade from Koha 3.08.07 > Message-ID: <bef5964a-be28-c06f-cf44-3cccb32a4c07(a)titley.com> > Content-Type: text/plain; charset=utf-8 > > > > On 09/09/2020 15:34, Nigel Titley wrote: > > I'm running an extremely antique version of Koha 3.08.07 on Debian > Squeeze. > > > > For various reasons (mainly the fact that the system is enormously > > stable) nothing has been upgraded for a long while but it's getting to > > the point where I need to upgrade it. I'm planning at the same time to > > move Koha off onto a new system running the latest Ubuntu LTS. I'm happy > > with installing a brand-new Koha but how do I go about transferring the > > data. I've found instructions for shifting the database but will the > > database schema upgrade work with that huge a jump? It's not a huge > > library, just a couple of thousand books. > > > > Thanks for any help that anyone can offer. > > And answering my own question, it looks like it might be possible to > export the book inventory in MARC format and the Patrons as a CSV file. > And possibly the transactions in an offline format? If the worst comes > to the worst I can lose the transactions. > > Does that sound like a plan? > > Nigel > > > ------------------------------ > > Message: 3 > Date: Wed, 9 Sep 2020 17:24:23 +0100 > From: Nigel Titley <nigel(a)titley.com> > To: koha(a)lists.katipo.co.nz > Subject: Re: [Koha] Upgrade from Koha 3.08.07 > Message-ID: <aec68d67-8021-7d5e-22d6-ba8ccfea9df0(a)titley.com> > Content-Type: text/plain; charset=utf-8 > > > > And answering my own question, it looks like it might be possible to > > export the book inventory in MARC format and the Patrons as a CSV file. > > And possibly the transactions in an offline format? If the worst comes > > to the worst I can lose the transactions. > > > > Does that sound like a plan? > > And answering my own question again it looks like that all I have to do > is dump the database on the old machine, copy it across and install it > on the new machine. The schema upgrade *should* be able to cope as I'm > running a koha instance later than 3.4 > > Nigel > > > ------------------------------ > > Message: 4 > Date: Wed, 9 Sep 2020 18:13:32 +0100 > From: Nigel Titley <nigel(a)titley.com> > To: koha(a)lists.katipo.co.nz > Subject: Re: [Koha] Upgrade from Koha 3.08.07 > Message-ID: <b432b667-4107-5bb4-d014-721fee640565(a)titley.com> > Content-Type: text/plain; charset=utf-8 > > > > On 09/09/2020 17:24, Nigel Titley wrote: > > > >> And answering my own question, it looks like it might be possible to > >> export the book inventory in MARC format and the Patrons as a CSV file. > >> And possibly the transactions in an offline format? If the worst comes > >> to the worst I can lose the transactions. > >> > >> Does that sound like a plan? > > > > And answering my own question again it looks like that all I have to do > > is dump the database on the old machine, copy it across and install it > > on the new machine. The schema upgrade *should* be able to cope as I'm > > running a koha instance later than 3.4 > > And this indeed worked... so everyone please ignore my witterings. The > procedure I followed was > > 1. Install latest koha on the new machine > 2. Use mysqldump to dump the whole koha database on the old machine > 3. Copy across to new machine > 4. Use "koha-create --create-db <library>" to create a koha instance on > the new machine > 5. Drop the new empty database <koha_library> created by step 4 > 6. Create a new empty database <koha_library> > 7. Use mysql to import the dump you made in step 2 into <koha_library> > 8. Run koha-upgrade-schema <library> > 9. Run koha-rebuild-zebra -v -f <library> > 10. Restart apache (possibly not necessary but doesn't do any harm) > > I now seem to have a fully functional new koha on a new machine > > Thanks everyone (I know no one said anything but you were all there in > spirit) > > Nigel > > > > > ------------------------------ > > Message: 5 > Date: Thu, 10 Sep 2020 09:16:17 +1200 > From: Alex Shepherd <kiwi64ajs(a)gmail.com> > To: Nigel Titley <nigel(a)titley.com> > Cc: koha(a)lists.katipo.co.nz > Subject: Re: [Koha] Upgrade from Koha 3.08.07 > Message-ID: <94140BC3-13A9-445F-94E3-A6C9E48F92B5(a)gmail.com> > Content-Type: text/plain; charset=utf-8 > > Thanks Nigel for reporting your success. I have an upgrade from Ubuntu > 16.04 / Koha 17.11 and wonder about such things. In need to clone my VM and > try and upgrade but I’ve been putting t off... > > Your success of a much harder upgrade is very encouraging. > > Regards > Alex Shepherd > > Sent from my iPad > > > On 10/09/2020, at 5:14 AM, Nigel Titley <nigel(a)titley.com> wrote: > > > > > > > >> On 09/09/2020 17:24, Nigel Titley wrote: > >> > >>> And answering my own question, it looks like it might be possible to > >>> export the book inventory in MARC format and the Patrons as a CSV file. > >>> And possibly the transactions in an offline format? If the worst comes > >>> to the worst I can lose the transactions. > >>> > >>> Does that sound like a plan? > >> > >> And answering my own question again it looks like that all I have to do > >> is dump the database on the old machine, copy it across and install it > >> on the new machine. The schema upgrade *should* be able to cope as I'm > >> running a koha instance later than 3.4 > > > > And this indeed worked... so everyone please ignore my witterings. The > > procedure I followed was > > > > 1. Install latest koha on the new machine > > 2. Use mysqldump to dump the whole koha database on the old machine > > 3. Copy across to new machine > > 4. Use "koha-create --create-db <library>" to create a koha instance on > > the new machine > > 5. Drop the new empty database <koha_library> created by step 4 > > 6. Create a new empty database <koha_library> > > 7. Use mysql to import the dump you made in step 2 into <koha_library> > > 8. Run koha-upgrade-schema <library> > > 9. Run koha-rebuild-zebra -v -f <library> > > 10. Restart apache (possibly not necessary but doesn't do any harm) > > > > I now seem to have a fully functional new koha on a new machine > > > > Thanks everyone (I know no one said anything but you were all there in > > spirit) > > > > Nigel > > > > > > _______________________________________________ > > > > Koha mailing list http://koha-community.org > > Koha(a)lists.katipo.co.nz > > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > Koha mailing list > Koha(a)lists.katipo.co.nz > https://lists.katipo.co.nz/mailman/listinfo/koha > > > ------------------------------ > > End of Koha Digest, Vol 179, Issue 10 > ************************************* >

1 0