- Koha - lists.katipo.co.nz

KOHA instalation on Cent OS 6.8
by paulson kf 16 Apr '17

16 Apr '17

Hi, I am trying to install KOHA ( latest stable version ) in Cantos 6.8 . I have a dedicated server with three website running successfully in it . I need to park my KOHA along with these website . CentOS.6.3 is that latest official documentation published on KOHA ( https://wiki.koha-community.org/wiki/Koha_3.10_on_Centos_6.3_x86_64_en ) . I have tried this but not getting succeeded . Any one have any information about this. Best Regards, Paulson k f

2 1

Call for news: April 2017 Newsletter
by kohanews 14 Apr '17

14 Apr '17

I'm collecting news for the April newsletter. Send anything noteworthy to: k o h a news AT gmail dot com News criteria: --------------------------- ** For events **: - Please include dates for past events. If I can't find dates I may not add it. - Announcements for future events with dates T.B.A. are fine ...Eg., Kohacon - For past events , **** one month back is the cut-off ****. * News items can be of any length. * Images are fine * Anything and everything Koha. * Submit by the 26th of the month. If you are working on an interesting project or development related to Koha, please let me know and I'll include it in the development section. -- Chad Roseburg Editor, Koha Community Newsletter

1 0

Due Date - Settings - Help
by SATISH 13 Apr '17

13 Apr '17

Hi, I am noticing an issue with "due date", it looks correct from the perspective of Koha. But, with my personal practical perspective, I am facing a problem. With Koha 16.5/Package Installation/ Ubuntu 14.04 Desktop / My Koha Library is set for 13 days of Loan Period (excluding Sunday - defined in the calendar) in Circulation Policy. Let us assume, one book's "Due Date" is: **11-4-2017** as shown in the Koha. (1) In case of *Late/Delayed Renewal,* let us assume after two days from due date(**) - Renewal performed on 13-4-2017 - the next due date Koha shows is - 25-4-2017 (which means, Koha counts 13 days from 11-4-2017 instead of from 13-4-2017, ie, the day on which renewal is made, ie, calculated from 2 days prior date) ------------------------------------------------------------------------ (2) In case of actual/fresh checkout on 13-4-2017 (which means, Koha counts 13 days from 13-4-2017 and the due date is 27-4-2017) --------------------------------------------------------------------------- (3) In case of *Early/Pre Date Renewal*, let us assume, before one day from due date (**) Renewal performed on 10-4-2017 - the next due date is - 25-4-2017 (which means, Koha counts 13 days from 11-4-2017 instead of from 10-4-2017) I am aware, conceptually, it might be wrong, but, my intention of asking this question is, whatever it may be the DUE DATE and whatever it may be the RENEWAL DATE, it has to count "Loan Period" (in my case 13 days) as per the RENEWING DATE. i,e the day on which renewal is performed, because, some of the users may not follow the due dates, they may come prior to due-date or after due-date and pay* late fee (fine)*. and also libraries using, rotating date stamping seals (at least in my place), need to be changed manually and put "date" stamp on due date slips accordingly and frequently since, we follow Library time table for checkout-renewals for each course/subject/class of students on particular day. My expectation is: the "due date" should appear same in all the three cases mentioned above. It has to calculate from the date on which "action" is performed. Therefore, Kindly advice, how to achieve this ? Are there any settings in Koha. --- With Thanks Satish MV Librarian Govt. Engineering College, Hassan. Karnataka. --

2 2

Re: [Koha] Error : Undefined subroutine CGI
by Rejeesh K.Nair 13 Apr '17

13 Apr '17

Thank you guys, I will work on this and let you know the progress. Thanks & Regards, Rejeesh K.Nair m: +91 (0) 9495316906 e: rejeeshknair(a)gmail.com <https://www.facebook.com/rejeeshnairk> <https://twitter.com/rejeeshknair> <http://in.linkedin.com/in/rejeeshknair> <https://www.instagram.com/rejeeshknair/>

4 8

Publisher Authority Type
by Krishna K 13 Apr '17

13 Apr '17

Hi, At the school library where we are setting up Koha, as part of migrating data, we plan to set up a new authority type for Publisher. We would like to import publisher data from an excel into the publisher authority type, then import the biblio with references to these publishers. I am unable to find detail instructions for the same. Could any of you help me with this please ? Also, which are the MARC tags we should use for illustrator, translated by and for editor fields ? Thanks for the support of this forum. -- Regards, Krishna

3 3

Update on Coce cached cover images
by Agnes Rivers-Moore 13 Apr '17

13 Apr '17

Hello Koha users I'm writing to let you know about a feature I have been testing - cover images from a Coce server hosted by Bywater. The ability to use Coce has been in Koha since 3.20 but required setup of a server to make it work. Recently, Bywater offered a hosted Coce server for anyone to use. There may also be other Coce servers available in the wider Koha community! It needs Koha libraries to use it for a time for it to work well (accumulate cached image links), so I am hoping you'll consider the option. The method is that a server (at Bywater for me) collects and caches links to jacket images from multiple sources; right now Open Library, Google Books and Amazon. Our Koha then gets the links from that server, and in time that means it can call for image links from three sources in a single search, and pick one to display. Pros: We are getting more cover images - specifically more for older titles and DVDs in addition to those that we got from Amazon. I philosophically approve of using Open Library, and now we can use it and Google Books and Amazon as well. Also the intermediate Coce server protects us from any data gathering that might be collected by Amazon or Google when we fetch a jacket image through their APIs. You can see some more advantages here: https://galencharlton.com/blog/2013/08/playing-around-with-coce/ It is really easy to set up now that each Koha system does not need to set up their own Coce server. Cons: The "Coce" server only collects and saves the image links when a Koha system requests the jacket image, so it takes time and use by a range of libraries for the server to gather a useful collection of cached links. We find that the return is not fast enough to load images reliably when the Coce server does not yet have a cached link for that title, so a refresh may be needed to load the images. Also right now it is only available for the OPAC, not the staff interface. I have created bug 18421 requesting that enhancement. We would have preferred to run it on the staff side only for a while before turning it on for the OPAC. In practice: See http://manual.koha-community.org/3.22/en/administration.html#coceimages. Use URL https://coce.bywatersolutions.com or alternate Coce server address. If https: does not work try http:. We are running both Amazon.ca and Coce at the same time, and loading 2 images for some items, one from each source, until Coce has enough links built up. This is not the intended use! I know it looks untidy but we are prepared to live with that until we can turn off the separate Amazon cover service and rely on getting everything from Coce. It is currently working on our catalogue at http://koha.hanoverlibrary.ca/cgi-bin/koha/opac-main.pl To see it in action, search for "Peter" and notice the titles that have only one image - those would have no jacket from Amazon. Many thanks to Frédéric Demians and everyone involved in writing Coce, and support at Bywater and Equinox for help testing this. <mailto:frederic@tamil.fr> Agnes -- Agnes Rivers-Moore CEO / Chief Librarian Hanover Public Library 451 10th Ave, Hanover, ON, N4N 2P1 Tel: 519.364.1420 x 1244 | Fax: 519.364.1747 Email: arm(a)hanover.ca<mailto:arm@hanover.ca> | Web: www.hanoverlibrary.ca<http://www.hanoverlibrary.ca> Facebook Hanover Public Library | Twitter @HanoverLibrary Support your library! Could you volunteer, make a donation, or remember us in your will? The Hanover Library uses email to communicate service messages to members who provide an address during registration or who contact us by email. Please contact the library to change your email preferences.

2 1

Re: [Koha] SQL help please
by Kerrie Stevens 13 Apr '17

13 Apr '17

Hi Katrin, Again, this is giving me everything at QLD, not items ONLY held at QLD… I’m sure there must be a way to do it… Thanks, Kerrie Stevens From: Katrin Fischer [mailto:Katrin.Fischer.83@web.de] Sent: Wednesday, April 12, 2017 5:27 PM To: Kerrie Stevens <KStevens(a)harvest.edu.au> Cc: koha(a)lists.katipo.co.nz Subject: Aw: [Koha] SQL help please Hi Kerrie, I think DISTINCT is not quite what you want here, but this seems to work for one of our libraries with multiple branches: SELECT i.itemnumber, b.title, b.author, i.itemcallnumber, i.barcode, i.homebranch FROM items i LEFT JOIN biblio b ON (i.biblionumber=b.biblionumber) WHERE homebranch = "QLD" AND i.biblionumber not in (SELECT biblionumber FROM items WHERE i.homebranch != "QLD") ORDER BY i.itemcallnumber Hope this helps, Katrin Gesendet: Mittwoch, 12. April 2017 um 07:20 Uhr Von: "Kerrie Stevens" <KStevens(a)harvest.edu.au<mailto:KStevens@harvest.edu.au>> An: "koha(a)lists.katipo.co.nz<mailto:koha@lists.katipo.co.nz>" <koha(a)lists.katipo.co.nz<mailto:koha@lists.katipo.co.nz>> Betreff: [Koha] SQL help please I have this report that lists all the items in our QLD library but I want to restrict it to items ONLY held in our QLD library and not another branch... I don't know where to put the DISTINCT tag? Please advise: SELECT items.itemnumber, biblio.title, biblio.author, items.itemcallnumber, items.barcode FROM items LEFT JOIN biblio ON (items.biblionumber=biblio.biblionumber) WHERE items.homebranch='QLD' ORDER BY items.itemcallnumber Thanks for your help, Kerrie Stevens Harevst Bible College _______________________________________________ Koha mailing list http://koha-community.org Koha(a)lists.katipo.co.nz<mailto:Koha@lists.katipo.co.nz> https://lists.katipo.co.nz/mailman/listinfo/koha

2 2

Splitting SQL Reports Library
by Barton Chittenden 13 Apr '17

13 Apr '17

Some time ago, Brooke started the process of splitting the Koha SQL Reports Library (https://wiki.koha-community.org/wiki/SQL_Reports_Library) into more manageable sections, starting with SQL Reports Holds (https://wiki.koha-community.org/wiki/SQL_Reports_Holds) SQL Reports patrons ( https://wiki.koha-community.org/wiki/SQL_Reports_Patrons) SQL Reports circulation ( https://wiki.koha-community.org/wiki/SQL_Reports_Circulation) Brooke copied the Holds, Patrons and Circulation reports, unfortunately, many of these have fallen out of sync with the main SQL Reports Library. At one of the recent Koha Development Meetings, it was decided that we need to move forward with splitting the reports out. I took the first step tonight, by deleting any reports that were exact duplicates, leaving a link in the old library. See https://wiki.koha-community.org/wiki/SQL_Reports_Library#Patrons_with_Holds…. This points to the full report at https://wiki.koha-community.org/wiki/SQL_Reports_Holds#Patrons_with_Holds_W… . If you have or edited queries that deal with holds, patrons or circulation, please check to see if your query is in the most recent form in one of the new pages, and leave a link to it from the header in the old SQL Reports Library. I would also like to move the other sections, although in those cases I would prefer to move the *entire* section, and simply leave a link from the old section to the new page, simply because creating the links is a lot of work. Thanks, --Barton

4 3

SQL help please
by Kerrie Stevens 12 Apr '17

12 Apr '17

I have this report that lists all the items in our QLD library but I want to restrict it to items ONLY held in our QLD library and not another branch... I don't know where to put the DISTINCT tag? Please advise: SELECT items.itemnumber, biblio.title, biblio.author, items.itemcallnumber, items.barcode FROM items LEFT JOIN biblio ON (items.biblionumber=biblio.biblionumber) WHERE items.homebranch='QLD' ORDER BY items.itemcallnumber Thanks for your help, Kerrie Stevens Harevst Bible College

2 2

No patron search results in Koha 16.05.09
by Michael Kuhn 12 Apr '17

12 Apr '17

Hi Today I updated a Koha installation from 3.20.03 to 16.05.09 (oldstable) via "apt-get install koha-common". * OS: Debian GNU/Linux 8 (Linux 3.16.0-4-amd64 #1 SMP) * Perl-Version: 5.020002 * Apache-Version: 2.4.10 (Debian) * Zebra-Version: 2.0.59 * Plack is not in use After the update the patron search via Koha menu "Patrons" is no more working. After searching for a patron just the header line with "Card / Name / Date of birth etc" appears but no actual results. Using the Koha menu "Circulation" patron search is working, e. g. in "Check out" where it is possible to enter patron card number or partial name. And of course all these patrons can be found in the database using SQL. Could this be a bug? 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

6 11