- Koha - lists.katipo.co.nz

Missing Bub Records
by Nasiru Yakubu 26 Sep '20

26 Sep '20

Hi, I am assisting a colleague who have Kaha version 19.11.08.000 installed and hosted by bywatersolutions. On using Z39.50 to import records the records cannot be found (on the OPAC or the Cataloging section of the staff interface) after the import but they can be seen in the reservoir. Has anyone experienced this before? -- M Nasiru Yakubu mobile: +234 818 747 4227 Skype ID: nasyak <https://orcid.org/0000-0002-5952-228X>

2 1

Import notes with line break
by Tiago Murakami 26 Sep '20

26 Sep '20

Hi, I need to import notes with line breaks. I try to use "space space", "<br />" and "line break in marcedit and it did not work. Which character should I use? Thanks in advance -- Tiago Murakami

2 1

How to add code to Marc record and display it in opac?
by Pavlo Bobesiuk 26 Sep '20

26 Sep '20

Hi everyone. Someone tried to add code of embed book to marc record and display it in the opac html5 media player? I have an idea to convert the first pages of books into flipbooks ( www.anyflip.com) and put code in marc record to be able to read them in opac media player. For example I would like to add this code: <iframe style="width:550px;height:350px" src=" http://online.anyflip.com/mepon/fath/" seamless="seamless" scrolling="no" frameborder="0" allowtransparency="true" allowfullscreen="true" ></iframe> to marc record of some book in 856u field, but in opac i see only code, I don't see frame with flip book. help me please realize this idea Paolo -- З повагою Павло Бобесюк=))

2 1

Koha 20.05.04 released
by Lucas Gass 26 Sep '20

26 Sep '20

Hello everyone! The Koha community is proud to announce the release of Koha 20.05.04. Koha 20.05.04 is a security release including 1 security fix, 23 enhancements, and 40 bugfixes. The full release notes are available here: https://koha-community.org/koha-20-05-04-released/ Debian packages are ready and can be downloaded here: https://download.koha-community.org/ -- Lucas Gass Web Developer

4 4

DBMS auto increment issue
by Daniel Owens 26 Sep '20

26 Sep '20

I am running Koha 20.05.02.000. I have corrupted data due to the DBMS auto increment issue. How can I deal with corrupted data? I tried following the advice to remove the affected lines from deleted* tables, but in the two items I checked, I could not find those ids. To find the ids listed in the About Koha - System Information message, I searched in the affected tables (deletedbiblios and deleteditems) using phpmyadmin. So I am confused about how to deal with the corrupted data. Can anyone suggest a way forward for me? Daniel

2 1

(no subject)
by Vincent Van Gogh 26 Sep '20

26 Sep '20

How can I make my koha library to searchable in google search engine?

2 1

rebuild_zebra daemon locks memcached?
by Alvaro Cornejo 24 Sep '20

24 Sep '20

Hi Since our update to 19.11.09 we start having problems with kona. We initially thought it was apache since without any notice, koha stop responding. When doing ps-ef |grep apache we got hundreds of entries even though we have very low load. Max 3 users at a time. Restarting apache solved the issue for a while On the server we only have koha and mod_pagespeed. Boith using the same instance of memcached. We disabled mod_pagespped and for a while, it looked like it was the problem, but after a couple of days, the issue returned. using netstat we found that there were lots of CLOSE_WAIT connections to port 11211. So we decided to configure two instances of memcached in two different ports. One for koha and one for mod_pagespeed. The issue of CLOSE_WAIT connections is less often now. However they are almost always related to perl . # sudo netstat -tulpan |grep 11211 gives us tcp 1 0 127.0.0.1:54368 127.0.0.1:11211 CLOSE_WAIT 1411/perl And checking the perl process: #ps -ef |grep 1411 bibliot+ 1411 1407 0 Sep18 ? 00:01:44 /usr/bin/perl /usr/share/koha/bin/migration_tools/rebuild_zebra.pl -daemon -sleep 5 Also, we noticed that, at anytime, memcached port has at least 10-15 connections split between memcached process and starman workers Is that normal? mod_pagespeed didn´t have any problem since it is configured to use an independant memcached instance Koha 19.11.09 Ubuntu bionic memcached 1.5.6 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

1 0

Re: [Koha] ElasticSearch Shuts Down on Server Reboot [Was: Installing ElasticSearch]
by Charles Kelley 24 Sep '20

24 Sep '20

Hello again, all! In our latest exchange, on 24 Sept 2020 at 09:01, the Koha Discussion Group circulated: It looks like my exuberance was premature. I spent much of yesterday > updating records. Towards the end of the day, I exported the entire > database -- both bibliographic and item records. Then I rebooted the > server. While the Koha interface came up, none of the titles I searched was > found. Instead, I got this error from the either Koha or the Linux box, to > wit: > > **Software error:** >> >> Unable to perform your search. Please try again. >> >> For help, please send mail to the webmaster ([*no address given*]), giving >> this message and the date and time of the error. > > > Mason James wrote: > $ sudo systemctl enable elasticsearch This worked! I've rebooted several times, checked my recent saves, and everything is intact. Thank you! Luis Moises Rojas wrote: Try to set ES as a service > Thanks for everything, all! Your advice and suggestions all worked perfectly. Linux is new to us as system administrators, and we aren't used to this level of detail. 気を付けて。 /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

ElasticSearch Shuts Down on Server Reboot [Was: Installing ElasticSearch]
by Charles Kelley 24 Sep '20

24 Sep '20

Hello, all! In our latest exchange, on 23 Sept. 2020 at 08:47, I wrote: Success! After several dozen tests, I'm glad and relieved that ElasticSearch > is successfully installed and it works smoothly. > It looks like my exuberance was premature. I spent much of yesterday updating records. Towards the end of the day, I exported the entire database -- both bibliographic and item records. Then I rebooted the server. While the Koha interface came up, none of the titles I searched was found. Instead, I got this error from the either Koha or the Linux box, to wit: *Software error:* > > Unable to perform your search. Please try again. > > For help, please send mail to the webmaster ([*no address given*]), > giving this message and the date and time of the error. > I didn't lose my work from yesterday because I had a backup copy of the authority and bibliographic files, and I had a backup copy of the previous day's installation of Koha. I was prepared to upload the files into the previous day's installation if I had to. However, by rebooting ElasticSearch manually, we could search again. Must I reboot ElasticSearch everytime we reboot the server? How does one get ElasticSearch to come up when the server is rebooted besides through manual intervention? Surely, there must be an automatic way. Many thanks for everyone's help in this. -- 気を付けて。 /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 4

Temporary workarounds for bug 23091 to charge overdue fines on formerly lost items
by Joelle Hannert 23 Sep '20

23 Sep '20

I recently discovered that our library is being impacted by bug 23091 - Add options to charge new or restore forgiven overdues when a lost item is returned. <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23091> I'm curious to hear if others have a good workaround process for re-charging overdues manually when items are returned, or are you just forgiving the fines until there is a fix? I'm worried about how to clearly communicate to circ staff how to properly re-calculate overdue fines once assumed lost items are returned...especially with our library having reduced open days (so less days when a fine should have accrued) during COVID. -- Joelle Hannert Library Technical Services Coordinator Northwestern Michigan College (231) 995-1684 Work days: M, T, Th, F

1 1