- Koha - lists.katipo.co.nz

temporarily suspend fines
by Margo Duncan 13 Mar '20

13 Mar '20

Good morning, Our spring break has been extended and we would like to temporarily suspend fines or automatically extend due dates in Koha, instead of individually adjusting accounts. Is there a way to do this globally? We have a lot of circulation rules. Thanks in advance, Margo Margo Duncan, MLS Electronic Resources & Collection Development Librarian Robert R. Muntz Library The University of Texas at Tyler 903.566.7174 | mduncan(a)uttyler.edu<mailto:mduncan@uttyler.edu>

2 1

Re: [Koha] multiple Koha zebra problem
by dcook＠prosentient.com.au 13 Mar '20

13 Mar '20

Hi George, I’m glad that my email helped! It does feel strange, but that’s the way SysV scripts work. Think about it like a shebang at the top of a script. While it starts with a #, it is still parsed by computers as more than just a comment. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 From: George Mikuchadze <gmikuchadze(a)gmail.com> Sent: Friday, 13 March 2020 4:11 PM To: dcook(a)prosentient.com.au Subject: Re: [Koha] multiple Koha zebra problem Many thanks for your reply, I updated this line (very strange because the line is a comment in the script) and it started without any problem! George Mikuchadze On Fri, Mar 13, 2020 at 3:26 AM <dcook(a)prosentient.com.au <mailto:dcook@prosentient.com.au> > wrote: Hi George, I notice that you didn't answer Katrin's questions. Answering those questions is really important, or we can't really help you very well. Now, it sounds to me like you've installed Koha from either a "git clone" or a tarball, and that you're running multiple Koha instances from multiple Koha codebases, which may or may not be running the same version. I'm guessing that you copied "misc/bin/koha-zebra-ctl.sh" to /etc/init.d/koha-zebra-daemon, /etc/init.d/koha1-zebra-daemon, etc. However, it sounds like you haven't updated the following line within that file: # Provides: koha-zebra-daemon You'll need to update that to match the filename. That's why you're getting that error. I think Ubuntu 14.04 used upstart as an init system while Ubuntu 16.04 should be using systemd. Systemd can be pretty strict when it comes to interpreting SysV style scripts like "misc/bin/koha-zebra-ctl.sh", so that's probably where the difference lies. Now, if you're only running 1 version of Koha (ie 3.22.21), I'd highly recommend that you don't use git/tarball installations, and instead switch to using Debian packages. It will make your life much easier (and it'll make it easier for you to get support from the Koha Community). Cheers, David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 -----Original Message----- Date: Thu, 12 Mar 2020 12:11:08 +0400 From: George Mikuchadze <gmikuchadze(a)gmail.com <mailto:gmikuchadze@gmail.com> > To: koha(a)lists.katipo.co.nz <mailto:koha@lists.katipo.co.nz> , katrin.fischer.83(a)web.de <mailto:katrin.fischer.83@web.de> , Irakli Garibashvili <igar(a)hotmail.com <mailto:igar@hotmail.com> > Subject: [Koha] multiple Koha zebra problem Message-ID: <CAJR6aCBHjT3XBNtvb_Unejw+5cUO9QU7JwfDatskrxPBEWDEnw(a)mail.gmail.com <mailto:CAJR6aCBHjT3XBNtvb_Unejw%2B5cUO9QU7JwfDatskrxPBEWDEnw@mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" Dear Katrin, Many thanks for Your reply. The problem is the following: We use multiple koha-s (with the same number of zebra daemons), now we want to install koha v3.22.21 on ubuntu 16.04. When I activate koha-zebra-daemon for the second instance of koha (koha1), I get the error: ---------------------------------------------------------------------------------------------------------------------- $ sudo update-rc.d koha1-zebra-daemon defaults insserv: script koha1-zebra-daemon: service koha-zebra-daemon already provided! insserv: exiting now! update-rc.d: error: insserv rejected the script header ----------------------------------------------------------------------------------------------------------------------- Here is the content of koha1-zebra-daemon: ............................................................................................................... .............the same as for instance of koha, koha2, koha3....................... USER=koha GROUP=koha DBNAME=koha1 NAME=koha-zebra-ctl.$DBNAME LOGDIR=/var/log/koha1 ERRLOG=$LOGDIR/koha-zebradaemon.err STDOUT=$LOGDIR/koha-zebradaemon.log OUTPUT=$LOGDIR/koha-zebradaemon-output.log KOHA_CONF=/etc/koha1/koha-conf.xml RUNDIR=/var/run/koha1/zebradb LOCKDIR=/var/lock/koha1/zebradb # you may need to change this depending on where zebrasrv is installed ZEBRASRV=/usr/bin/zebrasrv ZEBRAOPTIONS="-v none,fatal,warn" .................................................................................................... .............the same as for instance of koha, koha2, koha3........... The main strange is the following: it (the same version of koha and zebra) works without any problem on Ubuntu 14.04! Thanks in advance George Mikuchadze

1 0

Omeka / OHMS issue
by Chad Roseburg 13 Mar '20

13 Mar '20

We have a new installation of Omeka. When I try to upload an OHMS XML file, whether zipped or not, I get the error: LogicException OHMS file must be validated before retrieving the list of columns. Along with a stack trace. Any Omeka users run into this one? Thanks! -- Chad Roseburg Assoc. Director / IT Automation Dept. North Central Regional Library

3 3

Re: [Koha] multiple Koha zebra problem
by dcook＠prosentient.com.au 13 Mar '20

13 Mar '20

Hi George, I notice that you didn't answer Katrin's questions. Answering those questions is really important, or we can't really help you very well. Now, it sounds to me like you've installed Koha from either a "git clone" or a tarball, and that you're running multiple Koha instances from multiple Koha codebases, which may or may not be running the same version. I'm guessing that you copied "misc/bin/koha-zebra-ctl.sh" to /etc/init.d/koha-zebra-daemon, /etc/init.d/koha1-zebra-daemon, etc. However, it sounds like you haven't updated the following line within that file: # Provides: koha-zebra-daemon You'll need to update that to match the filename. That's why you're getting that error. I think Ubuntu 14.04 used upstart as an init system while Ubuntu 16.04 should be using systemd. Systemd can be pretty strict when it comes to interpreting SysV style scripts like "misc/bin/koha-zebra-ctl.sh", so that's probably where the difference lies. Now, if you're only running 1 version of Koha (ie 3.22.21), I'd highly recommend that you don't use git/tarball installations, and instead switch to using Debian packages. It will make your life much easier (and it'll make it easier for you to get support from the Koha Community). Cheers, David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 -----Original Message----- Date: Thu, 12 Mar 2020 12:11:08 +0400 From: George Mikuchadze <gmikuchadze(a)gmail.com> To: koha(a)lists.katipo.co.nz, katrin.fischer.83(a)web.de, Irakli Garibashvili <igar(a)hotmail.com> Subject: [Koha] multiple Koha zebra problem Message-ID: <CAJR6aCBHjT3XBNtvb_Unejw+5cUO9QU7JwfDatskrxPBEWDEnw(a)mail.gmail.com> Content-Type: text/plain; charset="UTF-8" Dear Katrin, Many thanks for Your reply. The problem is the following: We use multiple koha-s (with the same number of zebra daemons), now we want to install koha v3.22.21 on ubuntu 16.04. When I activate koha-zebra-daemon for the second instance of koha (koha1), I get the error: ---------------------------------------------------------------------------------------------------------------------- $ sudo update-rc.d koha1-zebra-daemon defaults insserv: script koha1-zebra-daemon: service koha-zebra-daemon already provided! insserv: exiting now! update-rc.d: error: insserv rejected the script header ----------------------------------------------------------------------------------------------------------------------- Here is the content of koha1-zebra-daemon: ............................................................................................................... .............the same as for instance of koha, koha2, koha3....................... USER=koha GROUP=koha DBNAME=koha1 NAME=koha-zebra-ctl.$DBNAME LOGDIR=/var/log/koha1 ERRLOG=$LOGDIR/koha-zebradaemon.err STDOUT=$LOGDIR/koha-zebradaemon.log OUTPUT=$LOGDIR/koha-zebradaemon-output.log KOHA_CONF=/etc/koha1/koha-conf.xml RUNDIR=/var/run/koha1/zebradb LOCKDIR=/var/lock/koha1/zebradb # you may need to change this depending on where zebrasrv is installed ZEBRASRV=/usr/bin/zebrasrv ZEBRAOPTIONS="-v none,fatal,warn" .................................................................................................... .............the same as for instance of koha, koha2, koha3........... The main strange is the following: it (the same version of koha and zebra) works without any problem on Ubuntu 14.04! Thanks in advance George Mikuchadze

1 0

[KOHA] SQL CIRCULATION REPORT
by muiru james 12 Mar '20

12 Mar '20

Dear All, My library uses DDC scheme of classification and we are looking for a report that will count items checked out allowing us to select day(s) of issue, select itemtype and group the statistics by DDC 10 broad classes. *EXAMPLE* IN a date range say 1st-31st March 2020. *DDC Class | NO. of books issued* 000 - 12 100 - 26 200 - 157 . . . 900 - 230 The report can generate statistics for a day, month, quarter, e.t.c. Any assistance however close will be greatly appreciated. Thank you as you prepare to help James

2 3

multiple Koha zebra problem
by George Mikuchadze 12 Mar '20

12 Mar '20

Dear Katrin, Many thanks for Your reply. The problem is the following: We use multiple koha-s (with the same number of zebra daemons), now we want to install koha v3.22.21 on ubuntu 16.04. When I activate koha-zebra-daemon for the second instance of koha (koha1), I get the error: ---------------------------------------------------------------------------------------------------------------------- $ sudo update-rc.d koha1-zebra-daemon defaults insserv: script koha1-zebra-daemon: service koha-zebra-daemon already provided! insserv: exiting now! update-rc.d: error: insserv rejected the script header ----------------------------------------------------------------------------------------------------------------------- Here is the content of koha1-zebra-daemon: ............................................................................................................... .............the same as for instance of koha, koha2, koha3....................... USER=koha GROUP=koha DBNAME=koha1 NAME=koha-zebra-ctl.$DBNAME LOGDIR=/var/log/koha1 ERRLOG=$LOGDIR/koha-zebradaemon.err STDOUT=$LOGDIR/koha-zebradaemon.log OUTPUT=$LOGDIR/koha-zebradaemon-output.log KOHA_CONF=/etc/koha1/koha-conf.xml RUNDIR=/var/run/koha1/zebradb LOCKDIR=/var/lock/koha1/zebradb # you may need to change this depending on where zebrasrv is installed ZEBRASRV=/usr/bin/zebrasrv ZEBRAOPTIONS="-v none,fatal,warn" .................................................................................................... .............the same as for instance of koha, koha2, koha3........... The main strange is the following: it (the same version of koha and zebra) works without any problem on Ubuntu 14.04! Thanks in advance George Mikuchadze

1 0

How to show contents?
by Rizwan Majeed 12 Mar '20

12 Mar '20

Dear All How I can show formatted contents of a book in OPAC? Regards!

2 1

Warning for the ClaimReturnedWarningThreshold
by Holly Interleaf 12 Mar '20

12 Mar '20

Hi All, I am just testing the enhancements to the Claims Returned lost status in the 19.11 release of KOHA, from this bug: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14697. Great feature, but I've had reports from some of the libraries that I support that the ClaimReturnedWarningThreshold may not be working correctly. Can I just check, how is the warning generated by that system preference supposed to look? For example, a client has saved the system preference as "Warn librarians that a patron has excessive return claims if the patron has claimed the return of more than 3 items." They then created a new patron and checked out a few items to them. When they marked the first item with the "Claim Return" option on the checkout table a note started to appear in the warning area under "Attention" on the upper right hand side of the circulation page: "Return claims: Patron has 1 RETURN CLAIMS." As they marked more items with "Claim Return", the number in the message rose, but no other warning appeared. Is this the warning a librarian will get? If so, shouldn't this have appeared only after 4 items had been marked as "Claim Return" on that patron account? Thanks, Holly <http://www.interleaf.ie/> *Holly Cooper* Systems Librarian hc(a)interleaf.ie <csq(a)interleaf.ie> +353-1-286-5855 A98 YD30 www.interleaf.ie <http://www.interleaf.ie/products-services/Library-Applications/Scooter> <http://www.interleaf.ie/products-services/Library-Applications/Koha> <http://www.interleaf.ie/products-services/PC-Reservation-and-Print-Manageme…>

2 1

Missing barcode number ascending order -SQL query
by Yatheesh lis 12 Mar '20

12 Mar '20

Hi Can anyone help me to get missing barcode number -SQL query. I tried one -SQL query available on koha wiki I am not getting in proper order it shows only starting ending

2 2

Koha Circulation not displaying anything after check out
by Admire Mutsikiwa 11 Mar '20

11 Mar '20

I have updated a Koha instance running on Ubuntu 18.04LTS to Koha version 19.11.03.000 from Koha version 19.02. When an Item is checked out it displays on the headings (Due date, title, ,) but with no corresponding information . On returns, it is behaving as is expected. Kind Regards, Admire Mutsikiwa University of Zimbabwe

2 1