- Koha - lists.katipo.co.nz

SQL query on number of days to get a book
by Suresh Kumar Tejomurtula 28 May '18

28 May '18

Hi, Query on orders(books) which are received in library and an email is triggered to members. This report may be useful in calculating number of days we are taking to get a suggested book. Here iam considering mail sent to a member as a value for calculating the number of days taken to get a book. SELECT aqorders.ordernumber, aqorders.biblionumber,aqorders.datereceived,aqorders.basketno, biblio.title,biblio.author, items.barcode,suggestions.date, suggestions.suggesteddate, message_queue.time_queued,(TO_DAYS(message_queue.time_queued)-TO_DAYS(suggestions.suggesteddate)) as days FROM aqorders LEFT JOIN biblio on (aqorders.biblionumber=biblio.biblionumber) LEFT JOIN items on (biblio.biblionumber=items.biblionumber) LEFT JOIN suggestions on (suggestions.biblionumber=items.biblionumber) LEFT JOIN borrowers on (borrowers.borrowernumber=suggestions.suggestedby) LEFT JOIN message_queue on (message_queue.borrowernumber=suggestions.suggestedby) where suggestions.status='Available' and items.itype='BK' GROUP by suggestions.title Hope this is useful for other members. -- Regards T. Suresh Kumar

2 1

18.05.00 - do not upgrade if itemtype defined at biblio level
by Jonathan Druart 28 May '18

28 May '18

Hi all, A critical bug has been found in 18.05.00 (bug 20825). If item types are defined at biblio level (item-level_itypes=biblio), you should *not* upgrade to 18.05.00. Sorry about that. Regards, Jonathan https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20825

4 4

To whom it may concern: Introducing Koha 18.05
by Michael Kuhn 28 May '18

28 May '18

Hi To whom it may concern: The webpage https://koha-community.org/ still says "Introducing Koha 17.11" instead of "Introducing Koha 18.05". Best wishes: Michael -- Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz T 0041 (0)61 261 55 61 · E mik(a)adminkuhn.ch · W www.adminkuhn.ch

2 1

MySQL query for serials late issues
by Suresh Kumar Tejomurtula 28 May '18

28 May '18

Hi, Below is my updated version of serials query for finding late issues based on the already existing query in koha sql reports library. Hope is it useful for other members. SELECT @kp:=@kp+1 as S_No,serial.serialseq, DATE_FORMAT(serial.planneddate, "%d %b %Y" ) as Planneddate, DATE_FORMAT(subscription.startdate, "%d %b %Y" ) as Startdate, DATE_FORMAT(serial.publisheddate, "%d %b %Y" ) as publisheddate, biblio.title, CASE WHEN serial.status = '3' or serial.status = '7' THEN 'LATE' WHEN serial.status = '1' THEN 'EXPECTED' END AS STATUS, CASE WHEN subscription.periodicity = '4' THEN 'Weekly' WHEN subscription.periodicity = '5' THEN 'Fortnightly' WHEN subscription.periodicity = '7' THEN 'Monthly' WHEN subscription.periodicity = '8' THEN 'Bi-Monthly' WHEN subscription.periodicity = '9' THEN 'Quarterly' WHEN subscription.periodicity = '10' THEN 'Semi-Annual' WHEN subscription.periodicity = '13' THEN 'Irregular' END as Frequency, CASE WHEN subscription.periodicity = '4' and (TO_DAYS(curdate())-TO_DAYS( publisheddate))>7 THEN 'Late' WHEN subscription.periodicity = '4' and (TO_DAYS(curdate())-TO_DAYS( publisheddate))<7 THEN 'Expected' WHEN subscription.periodicity = '5' and (TO_DAYS(curdate())-TO_DAYS( publisheddate))>14 THEN 'Late' WHEN subscription.periodicity = '5' and (TO_DAYS(curdate())-TO_DAYS( publisheddate))<14 THEN 'Expected' WHEN subscription.periodicity = '7' and (TO_DAYS(curdate())-TO_DAYS( publisheddate))>30 THEN 'Late' WHEN subscription.periodicity = '7' and (TO_DAYS(curdate())-TO_DAYS( publisheddate))<30 THEN 'Expected' WHEN subscription.periodicity = '7' and (TO_DAYS(curdate())-TO_DAYS( publisheddate))>30 THEN 'Late' WHEN subscription.periodicity = '9' and (TO_DAYS(curdate())-TO_DAYS( publisheddate))<90 THEN 'Expected' WHEN subscription.periodicity = '9' and (TO_DAYS(curdate())-TO_DAYS( publisheddate))>90 THEN 'Late' WHEN subscription.periodicity = '10' and (TO_DAYS(curdate())-TO_DAYS( publisheddate))>180 THEN 'Late' WHEN subscription.periodicity = '10' and (TO_DAYS(curdate())-TO_DAYS( publisheddate))<180 THEN 'Expected' WHEN subscription.periodicity = '13' and (TO_DAYS(curdate())-TO_DAYS( publisheddate))>30 THEN 'Late' WHEN subscription.periodicity = '13' and (TO_DAYS(curdate())-TO_DAYS( publisheddate))<30 THEN 'Expected' END as Status_calculated, DATE_FORMAT(subscription.enddate, "%d %b %Y" ) as enddate, (TO_DAYS(curdate())-TO_DAYS( publisheddate)) AS 'Delay Days', left(aqbasket.basketname,7)) as PONumber, CASE WHEN subscription.aqbooksellerid = 'xx' THEN 'Vendor1' WHEN subscription.aqbooksellerid = 'XX' THEN 'Vendor2' END as Vendor FROM serial LEFT JOIN serialitems on (serial.serialid=serialitems.serialid) LEFT JOIN subscription on (serial.subscriptionid=subscription.subscriptionid) LEFT JOIN subscriptionhistory on (serial.subscriptionid=subscriptionhistory.subscriptionid) LEFT JOIN subscriptionroutinglist on (serial.subscriptionid=subscriptionroutinglist.subscriptionid) LEFT JOIN biblioitems on (biblioitems.biblionumber=serial.biblionumber) LEFT JOIN biblio on (biblio.biblionumber=biblioitems.biblionumber) LEFT JOIN aqbooksellers on (subscription.aqbooksellerid=aqbooksellers.id) LEFT JOIN aqbasket on (subscription.aqbooksellerid=aqbasket.booksellerid), (select @kp:= 0) AS kp WHERE serial.planneddate < CURDATE() AND serial.STATUS NOT IN ('2','5','8','42','7') and (serial.planneddate>=subscription.startdate and serial.planneddate<=subscription.enddate) and subscription.closed='0' order by biblio.title -- Regards T. Suresh Kumar

1 0

Koha 18.05.00 released
by Jonathan Druart 28 May '18

28 May '18

Hello everybody, It is with great pleasure that the Koha community announces the release of Koha 18.05, a major release of the Koha open source integrated library system. Read the full release notes here: https://koha-community.org/koha-18-05-released/ If you do not usually read the release notes, you should at least read the new "Important notes" section at the top. The Debian packages for this new version will be available soon. Stay tuned! They are supposed to work out-of-the-box on: * Debian Jessie (8) * Debian Stretch (9) * Ubuntu Xenial (16.04 LTS) And should work without too much trouble under Ubuntu Bionic (18.04 LTC), check the install wiki page for more information. Cheers, Jonathan

12 19

Re: [Koha] Koha upgrade from 17.11 to 18.05
by Father Vlasie 28 May '18

28 May '18

I found out how to do it. The method was listed in the Ubuntu install instructions: https://wiki.koha-community.org/wiki/Koha_on_ubuntu_-_packages#Upgrade_Inst… I like answering my own questions, it gives me a sense of progress. :) FV

2 1

Elastic search error
by Arshad Iqbal 28 May '18

28 May '18

Hello everyone I have successfully upgraded 17.11.06 to 18.05. In system preferences i have changed Elastic search engine instead of zebra server for data searching. I got these error. Software error: Can't locate Catmandu/Store/ElasticSearch.pm in @INC (you may need to install the Catmandu::Store::ElasticSearch module) (@INC contains: /usr/share/koha/lib /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.24.1 /usr/local/share/perl/5.24.1 /usr/lib/x86_64-linux-gnu/perl5/5.24 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.24 /usr/share/perl/5.24 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at /usr/share/koha/lib/Koha/SearchEngine/Elasticsearch/Search.pm line 50. BEGIN failed--compilation aborted at /usr/share/koha/lib/Koha/SearchEngine/Elasticsearch/Search.pm line 50. Software error: [Mon May 28 09:26:47 2018] search.pl: Can't locate Catmandu/Store/ElasticSearch.pm in @INC (you may need to install the Catmandu::Store::ElasticSearch module) (@INC contains: /usr/share/koha/lib /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.24.1 /usr/local/share/perl/5.24.1 /usr/lib/x86_64-linux-gnu/perl5/5.24 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.24 /usr/share/perl/5.24 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at /usr/share/koha/lib/Koha/SearchEngine/Elasticsearch/Search.pm line 50. [Mon May 28 09:26:47 2018] search.pl: BEGIN failed--compilation aborted at /usr/share/koha/lib/Koha/SearchEngine/Elasticsearch/Search.pm line 50. Compilation failed in require at /usr/share/koha/lib/Koha/SearchEngine/Search.pm line 54. -- *Muhammad Arshad Iqbal* Assistant Librarian at Publishing and Student Affairs Directorate, National University of Science and Technology (NUST) Islamabad. Phone number:051-90851371 Cell no.+923444900809

2 1

squeeze vs. main
by Father Vlasie 26 May '18

26 May '18

Hello everyone, I have found a discrepancy in the documentation, this page (http://download.koha-community.org) says to use: deb http://debian.koha-community.org/koha squeeze main And the wiki page (https://wiki.koha-community.org/wiki/Debian) says: deb http://debian.koha-community.org/koha stable main What is the difference between "squeeze" and “main”? Thank you, FV

2 1

Koha upgrade from 17.11 to 18.05
by Father Vlasie 25 May '18

25 May '18

Hello everyone, I am new to this mailing list. I am the IT person for the St. Photios Orthodox Theological Seminary in Etna, California, U.S.A. I have been working on and off with Koha for about a year. We are finally getting close to cataloguing our library. I am very excited for the new 18.05 release but when I try to upgrade through my Debian (4.9.0-6-amd64 #1 SMP Debian 4.9.82-1+deb9u3 (2018-03-02)) system I get the following feedback: ---- root@owl:# apt-get update Get:1 http://security.debian.org stretch/updates InRelease [94.3 kB] Get:2 http://security.debian.org stretch/updates/main Sources [140 kB] Get:3 http://security.debian.org stretch/updates/main amd64 Packages [353 kB] Ign:4 http://deb.debian.org/debian stretch InRelease Get:5 http://deb.debian.org/debian stretch-updates InRelease [91.0 kB] Hit:6 http://deb.debian.org/debian stretch Release Get:8 http://security.debian.org stretch/updates/main Translation-en [165 kB] Get:9 http://debian.koha-community.org/koha stable InRelease [4,566 B] Get:10 http://debian.koha-community.org/koha stable/main amd64 Packages [18.8 kB] Fetched 867 kB in 1s (519 kB/s) Reading package lists... Done W: Conflicting distribution: http://debian.koha-community.org/koha stable InRelease (expected 17.11 but got 18.05) ---- If I try to upgrade anyway it holds koha-common back: ---- root@owl:# apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages have been kept back: koha-common libmoo-perl The following packages will be upgraded: libprocps6 procps 2 upgraded, 0 newly installed, 0 to remove and 2 not upgraded. ---- Any help would be much appreciated! Sincerely, Father Vlasie St. Photios Orthodox Theological Seminary 510 Collier Way, Etna, CA 96027, U.S.A. www.spots.school

1 0

Subject Cloud
by Rubén Fernández Asensio 25 May '18

25 May '18

Hi all, I run a small library and I want to allow OPAC users to browse our holdings by topic. Most of our holdings use the 653a MARC21 field as subject headings. I enabled the "OPAC Cloud" preference. Then I tried to build the tag database as instructed: export KOHA_CONF=/etc/koha/sites/biblioteko/koha-conf.xml; /usr/share/koha/bin/cronjobs/build_browser_and_cloud.pl -t 653a -c The command exited successfully, as far as I could tell. Now the OPAC shows a "Subject Cloud" link, but it only displays the following text: "Note: This feature only available to French catalogs where ISBD subjects have been populated, and an index built by separate script." According to HEA (https://hea.koha-community.org/systempreferences) at least 89 libraries around the world use this feature, and I can't believe they're all French language libraries. What are the exact requirements to have this working? Does any of you use this feature, and can guide me step by step? Rubén Fernández

2 3