- Koha-devel - lists.koha-community.org

Koha Maps
by Marshall Breeding 20 Dec '16

20 Dec '16

I have been following the discussion about how the Koha community can better market itself, including using a map display to emphasize its global impact. Naturally, I would be happy to have the map generated from Library Technology Guides to be used. Doing so would help me ensure that my registry of libraries using Koha is more complete since libraries might be more motivated to be included. Regardless of whether the Koha community decides to rely more on my mapping tool, I will continue to try to obtain data on the many libraries using Koha that are not yet registered on my site or any other database. I continue to think that Koha is most likely the most implemented ILS, but I do not yet have the data to validate that assertion. The purity of working only with open source software and open access data seems to me like an impossible goal. Richard Stallman, who I heard speak last year, takes this concept to its logical conclusion, and ends up with quite a limited realm of software or data which meet his tests for purity. Is the Koha community comfortable using the Google Map API, for example, since it is based on a closed and proprietary information infrastructure and underlying software components that may or may not be open source? Or does it plan to invent its own global mapping ecosystem? I have looked at the Hea tool and I have a hard time imagining it gaining the functionality of a global mapping visual and becoming well populated by the mechanisms provided. Since it is generated mechanically through each instance of Koha, it will be difficult to translate this data to represent the libraries that are actually using Koha in production. Many of the entries shown now (http://hea.koha-community.org/libraries) seem to be duplicates or test implementations. Its single entry for the NExpress Shared Catalog is represented by 53 libraries on my maps. I don't see hea as having the structure has the ability to represent the branches associated with a library system or consortia and many other aspects of tracking the libraries which use any given automation system. I think that many, if not the majority, of Koha implementations globally are based on older or forked versions of Koha, making it difficult or impossible for them to automatically contribute their data to Hea. I also wonder why the Koha development community would divert resources into re-creating such a tool from other efforts to develop and promote Koha. Having maintained a registry of libraries for almost two decades, my experience tells me that it is much more difficult to create and maintain a well-organized list than others might imagine. I have also just re-written the map tool on Library Technology Guides to generate the display more quickly when there are a very large number of libraries. Although it depends on how quickly the Google API responds, it now builds the maps in a few seconds, compared to almost a minute previously. I have also added some basic search selection tools at the bottom of the page: https://librarytechnology.org/libraries/map.pl?ILS=Koha I'll be interested to hear further discussion on the topic. Marshall Breeding marshall.breeding(a)librarytechnology.org<mailto:marshall.breeding@librarytechnology.org> www.librarytechnology.org/<http://www.librarytechnology.org/> twitter.com/mbreeding http://www.linkedin.com/in/breeding http://scholar.google.com/citations?user=NnvfJ5cAAAAJ

2 1

Re: [Koha-devel] Enabling Arabic and Kurdish Indexing
by Paul A 20 Dec '16

20 Dec '16

At 04:11 PM 12/20/2016 +0000, MHE I.T. Admin (DRR) wrote: >Than you for the prompt response, Yes they are in the same folder as >(/etc/koha/zebradb/etc) and it is on 0644 Is there a typo? (it was suggested that this is crucial) Recommended: koha/zebradb/etc ... Found: /etc/koha/zebradb/etc ... (our system confirmed, and happy with 644) /---/ <http://www.indexdata.com/yaz/doc/yaz-icu.html> neither confirms nor denies that multiple lang options are possible, rather than the default <icu_chain locale=""> -- if you can get your server to find the file, have you tried both with and without the default? Maybe putting the default below specifics? Best -- Paul >Can you list several languages inÂ words-icu.xml likeÂ > > > <icu_chain locale="ar"> >. > >. > >. > >. > </icu_chain> > > > > > > <icu_chain locale="ku"> >. > >. > >. > >. > </icu_chain> > > >On 20 December 2016 at 15:57, Barton Chittenden ><<mailto:barton@bywatersolutions.com>barton(a)bywatersolutions.com> wrote: > >On Tue, Dec 20, 2016 at 10:15 AM, MHE I.T. Admin (DRR) ><<mailto:admin@mhe-krg.org>admin(a)mhe-krg.org> wrote: >15:58:14-20/12 zebraidx(9140) [warn] default.idx:13: Could not load >icuchain config 'words-icu.xml' > > >I see two unrelated issues in your logs. The most crucial was > >Could not load icuchain config 'words-icu.xml' > > >This is what's causing the indexes to fail. > >words-icu.xml should be in the same directory asÂ >koha/zebradb/etc/default.idx. Make sure that it's there, and that it's >readable. > >See > ><https://wiki.koha-community.org/wiki/ICU_chains_configuration>https://wiki.koha-community.org/wiki/ICU_chains_configuration > >The second issue is that you don't have item types for some of your items. >That won't cause issues with searching, but it will cause errors when you >try to check the items in or out. The item numbers are given in the error >messages, and you can use sql to find the barcodes. > >--Barton > > > > >-- > >I.T Admin (Dr. D.R. Roshani) ><http://www.mhe-krg.org>Ministry of Higher Education >T. +964.XXX.XXX XXX | E. <mailto:admin@mhe-krg.org>admin(a)mhe-krg.org >_______________________________________________ >Koha-devel mailing list >Koha-devel(a)lists.koha-community.org >http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >website : http://www.koha-community.org/ >git : http://git.koha-community.org/ >bugs : http://bugs.koha-community.org/ --- Maritime heritage and history, preservation and conservation, research and education through the written word and the arts. <http://NavalMarineArchive.com> and <http://UltraMarine.ca>

2 1

Enabling Arabic and Kurdish Indexing
by MHE I.T. Admin (DRR) 20 Dec '16

20 Dec '16

Hi everyone, For our university library (http://library.koyauniversity.org/) we have Koha 16.11. I was hoping that the new version will have a simple setting in Admin interface to enable indexing is any languages by couple check boxes. I can not imagine that there is a function library in the world and not have couple books in Hebrew, Arabic or Persian, so KOHA needs to have easy approach to this not just LATIN BASED languages. Everything works fine with our Koha but have great issue with indexing Arabic and Kurdish titles, (both RTL language, Arabic based alphabets). When search it just list everything and anything. I have followed the instruction here https://wiki.koha-community.org/wiki/Correcting_Search_of_Arabic_records but each time I run # sudo koha-rebuild-zebra -f library it give me error message below and does not index anything at all, so I gave up and reversed the steps. Would you please help? # sudo koha-rebuild-zebra -f library Warning: You passed -x which is already the default and is now deprecated item-level_itypes set but no itemtype set for item (10) at /usr/share/koha/lib/Koha/Schema/Result/Item.pm line 698. item-level_itypes set but no itemtype set for item (718) at /usr/share/koha/lib/Koha/Schema/Result/Item.pm line 698. item-level_itypes set but no itemtype set for item (41) at /usr/share/koha/lib/Koha/Schema/Result/Item.pm line 698. item-level_itypes set but no itemtype set for item (42) at /usr/share/koha/lib/Koha/Schema/Result/Item.pm line 698. item-level_itypes set but no itemtype set for item (1527) at /usr/share/koha/lib/Koha/Schema/Result/Item.pm line 698. item-level_itypes set but no itemtype set for item (1538) at /usr/share/koha/lib/Koha/Schema/Result/Item.pm line 698. item-level_itypes set but no itemtype set for item (1766) at /usr/share/koha/lib/Koha/Schema/Result/Item.pm line 698. item-level_itypes set but no itemtype set for item (1027) at /usr/share/koha/lib/Koha/Schema/Result/Item.pm line 698. item-level_itypes set but no itemtype set for item (645) at /usr/share/koha/lib/Koha/Schema/Result/Item.pm line 698. item-level_itypes set but no itemtype set for item (642) at /usr/share/koha/lib/Koha/Schema/Result/Item.pm line 698. item-level_itypes set but no itemtype set for item (5923) at /usr/share/koha/lib/Koha/Schema/Result/Item.pm line 698. item-level_itypes set but no itemtype set for item (7968) at /usr/share/koha/lib/Koha/Schema/Result/Item.pm line 698. item-level_itypes set but no itemtype set for item (7960) at /usr/share/koha/lib/Koha/Schema/Result/Item.pm line 698. item-level_itypes set but no itemtype set for item (7976) at /usr/share/koha/lib/Koha/Schema/Result/Item.pm line 698. 15:58:14-20/12 zebraidx(9140) [warn] default.idx:13: Could not load icuchain config 'words-icu.xml' 15:58:15-20/12 zebraidx(9140) [fatal] zebra_begin_trans: cannot open register

2 2

Hackfest in Marseille 2017
by Paul Poulain 19 Dec '16

19 Dec '16

Hello everybody, In 2017, the hackfest in Marseille is back to March. 20th-24th to be precise. Feel free to join us ! (registration not yet open) -- Paul Poulain, Associé-gérant / co-owner BibLibre, Services en logiciels libres pour les bibliothèques BibLibre, Open Source software and services for libraries

1 0

Example of serial claim notice
by Marcel de Rooy 19 Dec '16

19 Dec '16

Hi, Can anyone help me with an example of a serial claim notice? Module claimissues does not seem to have a sample notice. Thanks, Marcel

1 0

Koha development meeting reminder - 14 December 2016
by Nick Clemens 13 Dec '16

13 Dec '16

Hi All, The next Koha development meeting is on IRC tomorrow 14 December 2016 at 13:00 UTC You can see what that is in your local time here: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Koha+Developers+I… Agenda is here: https://wiki.koha-community.org/wiki/Development_IRC_meeting_14_December_20… Please make sure to add any topics you wish to discuss. See you all soon! -Nick

1 0

ldap authentication in koha 16.11 become broken when enabling plack
by Mohammad Nashbat 12 Dec '16

12 Dec '16

Hi All, We've recently upgraded to Koha 16.11 which is running on Debian Jessie, we also activated plack which makes the system really faster than before but found out that Koha ldap authentication become broken, but when we disabled plack it works fine with slowness. Any help to make koha ldap integration works with plack is highly appreciated. Thanks & Best Regards, Mohammed Nashbat Library Instructor Alfaisal University ________________________________ DISCLAIMER: This electronic mail transmission contains confidential information intended only for the person(s) named. Any use, distribution, copying or disclosure by any other person is strictly prohibited. If you received this transmission in error, please notify the sender by reply e-mail and then destroy the message. Opinions, conclusions, and other information in this message that do not relate to the official business of Alfaisal University shall understand to be neither given nor endorsed by Alfaisal University. The contents of any attachment to this e-mail may contain software viruses, which could damage your own computer system. While “Alfaisal University” has taken every reasonable precaution to minimize this risk, we cannot accept liability for any damage which you sustain as a result of software viruses. You should carry out your own virus checks before opening the attachment.

1 0

What's on in koha-devel #8
by Jonathan Druart 05 Dec '16

05 Dec '16

Hello librarians and developers, Koha 16.11 and its Debian packages have now been released [1]. As Mirko noted Debian Wheezy is no longer supported and Debian packages won't be provided for 3.22 [2]. I should also added that some important bugs have been reported recently and it may be better to wait for the 16.11.1 version to be released before upgrading [3, 4, 5]. Note that if you database password contain Unicode characters, you should also wait for bug 17720 (CSRF token is not generated correctly). = Refactoring = == Move to the Koha namespace == We keep on moving the C4::Members module code to the Koha namespace and a few subroutine of C4::Circulation are going to be moved as well [6]. == Remove the biblioitems.marcxml field == I have been asking for help on bug 17196 (Move marcxml out of the biblioitems table) for months now and this will certainly be my last attempt to get attention on it. As we are at the beginning of the release we should focus on it to get it pushed soon. That way we will have time to catch and fix bugs if we find some. == Rewrite of the upload feature = A month ago Marcel started to refactor the upload section [7]. This is the groundwork to start improvements in this area. Once this is pushed we will be able to add new features, so please test! = Template Toolkit syntax for notices = Kyle started a discussion some months ago [8] to switch from our home-made syntax for notices to the Template Toolkit syntax. That would bring us a lot of flexibility to write the notices. But to do so, we need a plan! We already started to support this syntax (inside 16.11) but then we have to decide what to do next. Currently the plan would be to replace the default syntax (bug 15278), then reveal in the editor that you can use this new syntax (bug 15277) and finally add documentation to help people writing/porting their own notices (bug 15276). We need to get opinions to know how we could move forward. Kyle is going to start a new topic on the Koha mailing list for that. Stay tuned! = Standardize our EXPORT = A bit more technically, I would need developer's attention on bug 17600 (Standardize the EXPORT). At the end of the last release, very bad bugs appeared at the last minute because of our circular dependencies and the way we export subroutines from routines. Everything is (quickly) explained on that bug and a patchset has been submitted for discussion. If you are aware of how we could fix that cleanly, please jump into the discussion. The next general IRC meeting is on December 7th, 14 UTC. https://wiki.koha-community.org/wiki/General_IRC_meeting_7_December_2016 The next dev IRC meeting is on December 14th, 13 UTC. https://wiki.koha-community.org/wiki/Development_IRC_meeting_14_December_20… Hope to see your there! Cheers, Jonathan [1] https://koha-community.org/koha-16-11-released-2 [2] http://lists.koha-community.org/pipermail/koha-devel/2016-November/043330.h… [3] Bug 17676 - Default COLLATE for marc_subfield_structure is not set [4] Bug 17344 - Can't set guarantor in quick add brief form [5] Bug 17709 - Article request broken [6] Bug 17677 - Move C4::Circulation code to the Koha namespace [7] Bug 17501 - Koha Objects for uploaded files [8] http://lists.koha-community.org/pipermail/koha-devel/2016-February/042316.h…

1 0

942 versus 952
by Karen Myers 02 Dec '16

02 Dec '16

Hi all I am wanting to clarify the usage of the 942$c field versus the 952$y field as I am setting up a new bib framework. I am wondering if it is necessary to have both the 942$c field and the 952$y field in the framework as they seem to record the same information i.e Koha item type. Is there an advantage to recording the same information in both fields and if not which is the preferred? We are using Koha 3.22 thanks! Karen

3 3

Improvements to framework plugins (cataloguing)
by Marcel de Rooy 02 Dec '16

02 Dec '16

Hi all, Around two years ago I wrote Koha::FrameworkPlugin now. As an ongoing project I wanted to convert existing plugins to its new style (while it also supports the old style). Unfortunately, this project did not get much further the last six months of 16.11. Two reports https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13438 and https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16203 are just waiting for a signoff already over 6 months, while they still apply. Since one report deals with normarc plugins, I hoped for Magnus, but unfortunately.. I am still hoping for some attention. Further development in this project depends on it. Testing them should not be that hard. Thanks, Marcel

1 0