- Koha - lists.katipo.co.nz

zebra - item-level_itypes errors
by Tom Hanstra 19 Apr '17

19 Apr '17

I'm installing Koha 16.11 and picked up the 06 release. Installation went fine, however when indexing with Zebra, I'm getting a number of records which give the error: item-level_itypes set but no itemtype set for item (item#) at /usr/share/koha/lib/Koha/Schema/Result/Item.pm line 698 I saw a thread suggesting that these types of records might have the onloan value not set to NULL, but I checked and all of my records have onloan either set to NULL or to a valid date value. I also saw that some of these problems might have been fixed by bug 17502. It is not clear to me if that bug fix was included in the 16.11.06 tar package. Do I have database problems with these records? If so, what should I be looking for? Or is there something else that can cause this problem? Or is the patch missing from this download? Thanks in advance for any pointers I can get. Tom -- *Tom Hanstra* *Sr. Systems Administrator* hanstra(a)nd.edu <http://library.nd.edu/>

3 4

Hello
by Brian Trippodo 18 Apr '17

18 Apr '17

Hi everyone! My name is Brian and I just started working at Queens University of Charlotte two weeks ago. For the past 10 ½ years I had been working for an Innovative library using Millennium & Sierra. I'm very excited about learning all about a new ILS and making sure Koha is being utilize in the most effective manner possible. So far, I've been listening to some webinars about the 16.11 release, looking at the manual, and I also found a Koha newbie wiki. But, I was wondering if any of you wonderful people might have some suggestions on other resources to help me get up to speed on all things Koha? Thanks in advance for any suggestions you all might have! Kind Regards, Brian Brian Trippodo Systems & Electronic Resources Librarian Queens University of Charlotte | Everett Library 1900 Selwyn Avenue | Charlotte, NC 28274 T: 704.688.2766 | E: trippodob(a)queens.edu<mailto:trippodob@queens.edu>

2 1

Need feedback on lists (virtual shelves) permissions
by Marcel de Rooy 18 Apr '17

18 Apr '17

Hi all, On Bugzilla report 18228 https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18228 I have proposed to merge the currently separated Add and Delete permission for entries on a list into a new Change permission. This BZ attachment https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=60943 shows you the new options: Change is allowed for Nobody (readonly), Owner only, or Anyone seeing the list. Owen suggested to hide the "Anyone seeing the list" option for private lists. As a plea in favor of the new design, I would add that (apart from simplifying something that confused people) we could see the list as a document containing lines. If we allow someone to change the document, he is able to add and delete lines. In Koha we are actually not interested in who added a line (entry to the list). The information is saved but only used in context of the old permission scheme. We follow a similar principle with e.g. biblios or patrons: if we have edit/modify/change permission, we can add and delete a biblio, a patron, etc. So, my main question is now: Would you consider this as a welcome simplification or as feature loss? Are you heavily leaning on the separation of add and delete permissions? If you can add a response on the Bugzilla report, please do. Otherwise reply to the list. Thanks, Marcel

1 1

ElasticSearch (authorityserver&biblioserver) path
by Abdulsalam Yousef 18 Apr '17

18 Apr '17

Hello All, We would like to know the alternative path of (authorityserver&biblioserver) in koha-conf.xml file for ElasticSearch instead of the following Zebra path here <listen id="biblioserver" >unix:/var/run/koha/zebradb/bibliosocket</listen> <listen id="authorityserver" >unix:/var/run/koha/zebradb/authoritysocket</listen> Thanks in advance.

2 3

Facets show more link with elastic search
by Abdulsalam Yousef 18 Apr '17

18 Apr '17

Hello all, We are facing a problem in Facets show more link with elastic search, Selecting facets show more link doesn't show more results of (Authors, Topics, ...etc) except (Home an Holding branches work perfectly), Instead of this, It shows the following messages *No results found!* You did not specify any search criteria. Error: Unable to understand your search query, please rephrase and try again. We are using Koha 16.11.01 with ElasticSearch as a search engine Thanks in advance.

2 5

List of Email to SMS Gateways
by Eric Phetteplace 17 Apr '17

17 Apr '17

Hi list, Not sure if others who are setting up the SMS notification feature will find this useful, but I found a wonderfully comprehensive listing of telephone server provider email domains: https://mfitzp.io/list-of-email-to-sms-gateways/ Best, Eric Phetteplace Systems Librarian California College of the Arts libraries.cca.edu | vault.cca.edu 510.594.3660 2>/dev/null

2 1

Import staged MARC records with ElasticSearch engine
by Abdulsalam Yousef 17 Apr '17

17 Apr '17

Hello all, - Importing MARC records into catalog form (Manage staged MARC records) in staff client GUI using ElasticSearch engine is very slow and accidentally stops after importing some hundreds of records, That we may spend 3 days to import about 26000 record only, Is that normal? or there are any other configurations should be done first with ElasticSearch engine? - We are using Koha 16.11.01. Thanks in advance.

3 2

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