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

RFC for overdue notice enhancements
by Francois Charbonnier 27 Aug '14

27 Aug '14

Hello all, Halland County Library in Sweden is going to sponsor new features. Their goals are to : * manage a reminder fee when a reminder is sent * manage different reminder delays depending on whether the item is reserved or not, and is free of charge or has a rental fee. We will start from a development inLibro did to manage invoices and fixed costs that goes along (http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11092) Since, it hasn't been upstreamed yet, we will close this report and re-work it for a better integration with the new features. The requirements were thought to comply Halland County Library needs but also to be flexible and fulfill different settings. We also paid attention to keep Koha's behaviour, so libraries can keep their original set up if they doesn't need these new features. Here, you will find the RFCs : http://wiki.koha-community.org/wiki/Overdue_Notice_Enhancement Any comments, thoughts, suggestions are very welcome! Thanks François -- François Charbonnier, Bibl. prof. / Chef de produits Tél. : (888) 604-2627 francois.charbonnier(a)inLibro.com <mailto:francois.charbonnier@inLibro.com> inLibro | pour esprit libre | www.inLibro.com <http://www.inLibro.com>

7 10

PROG/CCSR deprecation
by Chris Cormack 27 Aug '14

27 Aug '14

Hi All I have been working on the prog/ccsr removal, I have all the patches that have been signed off pushed to a branch so we can test them all together. However I need 3 bugs to be signed off 12655 12539 12657 If someone could take a look at that and please sign them off, we can push them to the MM_OPAC/theme_dep to get them integration tested and then merge to master Thanks Chris

1 0

Call for development IRC meeting
by Tomas Cohen Arazi 27 Aug '14

27 Aug '14

I forgot to announce last week's dev meeting so we missed it. Sorry for that. I propose doing it next tuesday: - 2 September 2014, 15UTC - 2 September 2014, 22UTC I encourage everyone interested on the UTF-8 cleanup effort to be on IRC, we need your opinions. We definitely need ideas for writing regression tests for this, and volunteers to work on that. The guys have worked a lot on this patches, and are rebasing them periodically. We have reached half of the 3.18 release cycle, and this stuff needs to get in so we have enough time to test and fix any possible regression before release on november. I remind you the wiki page where we are sumarizing what's left to be done so you make up your mind by tuesday: http://wiki.koha-community.org/wiki/Handling_UTF8_in_development I hope you can all join us. Thanks in advance -- Tomás Cohen Arazi Prosecretaría de Informática Universidad Nacional de Córdoba ✆ +54 351 5353750 ext 13168 GPG: B76C 6E7C 2D80 551A C765 E225 0A27 2EA1 B2F3 C15F

1 0

Stemming and zebra
by Francois Charbonnier 27 Aug '14

27 Aug '14

Hello, I have tested the QueryStemming system preference on Koha 3.14 (my local installation) and I'm wondering, does zebra just right truncate the words or is there an algorithm to find the stems? I use ICU and I have enabled "QueryWeightFields". I don't have automatic truncation or fuzzy search on. I use these words for my tests: * ski, skiing, skills * fish, fished, fishing, fisher, fishxsdfe Each time, with QueryStemming on, skills and fishxsdfe come out in the search results. Is it what I should expect? "Skills", maybe but "fishxsdfe"? Do you know how it works? or have a good example that would help me to understand? Thanks! -- François Charbonnier, Bibl. prof. / Chef de produits Tél. : (888) 604-2627 francois.charbonnier(a)inLibro.com <mailto:francois.charbonnier@inLibro.com> inLibro | pour esprit libre | www.inLibro.com <http://www.inLibro.com>

3 5

Koha::Acquisition::Order?
by Jonathan Druart 27 Aug '14

27 Aug '14

Hi developers, I've just sent a patch to put the order-related code into a new module. I would like to get some feedback on it. Please have a look at bug 12830 Note that the changes are not trivial and rebase the patch for a long time is dangerous. The sooner this first patch is integrated (adapted to your needs/requests), the faster I will provide a patch to fix the TODOs. Cheers, Jonathan http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12830

1 0

Proposed patch to add in-browser support of Indian/non-Latin language typing in Koha
by Indranil Das Gupta 26 Aug '14

26 Aug '14

Hi all, [apologies for X-Posting] Browser based on-the-fly transliterated input on the OPAC was a long-standing requirement particularly in the Indian Koha user community. Indian government recognises 22 official languages for the purpose of official correspondance. The earlier attempts to add GoogleIndicTransliteration was a step in this direction. But that attempt did not finally clear QA. Google Transliteration API was deprecated in June 2011 and it's general Terms of Service (ToS) are not FOSS friendly. In contrast, jQuery.IME is dual-licensed under GPLv2+ and MIT. It is a key component of Wikimedia's (the organisation behind Wikipedia.org) global language engineering stack. At present, this represents robust, well tested support for over 135 input methods spanning over 67 languages. I've uploaded a patch (http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=31152) against the bug number http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12815. The patch is against the current Koha master. I would like to request interested users to have a look and preferably test it. The patch work both in the OPAC as well as in Koha's staff client interface. Screenshots of the patch in action: http://imgur.com/a/2gB7H#0 and http://imgur.com/a/2gB7H#2 cheers, -indra -- Indranil Das Gupta Phone : +91-98300-20971 Blog : http://indradg.randomink.org/blog IRC : indradg on irc://irc.freenode.net Twitter : indradg -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=- Please exchange editable Office documents only in ODF Format. No other format is acceptable. Support Open Standards. For a free editor supporting ODF, please visit LibreOffice - http://www.documentfoundation.org

1 0

C4/Items.pm experts invited
by Marcel de Rooy 24 Aug '14

24 Aug '14

Hi, Bug 7817 offers two approaches on resolving an issue with unmapped (internal) item fields. Your feedback is welcome. Thanks, Marcel

2 1

Re: [Koha-devel] RFC: proposing change to Koha's plugins system
by Paul A 22 Aug '14

22 Aug '14

At 10:16 PM 8/21/2014 +0000, Indranil Das Gupta wrote: >Hi all, > >I've been trying to use the KPZ structure in some of my projects. In >general, I've found it rather useful, with a few modifications. > >I would like to propose the following changes as >http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12805 > >lets have your feedback on this. With a view of maintaining core stability for Koha, all 'enhancements' (e.g. plug-ins) should be optional and not affect speed, size and cpu cycles of basic functionality. I think that this is what you are proposing... if I'm mistaken, please advise. I've been relatively quiet for some time about my intrinsic belief that a two year cycle of updating Koha (along the same 2-year lines of most OS's) should be the norm. "If it ain't broke, don't fix it." Enhancements (not security updates) should be for the end-user to decide upon, and most libraries do not have the personnel | time | budget to get involved every couple of months. I recognize that the paid consultants may have an interest -- and I have absolutely nothing against that; without them a huge amount of "Koha devel" would not take place. However, we are getting ready to upgrade our servers from 2012 to 2014 standards, and I've been looking at Koha 3.14 and 3.16. We are *not* a lending library -- just a big research centre -- and quite frankly I can find no totally compelling reason to upgrade from 3.8 (handheld browsers might be the exception.) Again, if I'm mistaken, please advise. Please don't misunderstand me. I'm all in favour of "improvments", but when a quick analysis of one of my OPAC pages come up with: Combine external CSS (6) Combine external JavaScript (11) Leverage browser caching (23) Leverage proxy caching (5) Minimize cookie size Serve static content from a cookieless domain (11) Specify image dimensions (1) Optimize the order of styles and scripts (2) Remove unused CSS rules (1335) Use normal CSS property names instead of vendor-prefixed ones (3) it's probably better to look at the 1,335 "unused CSS rules"... (bootstrap? doesn't do away with yahoo? does zebra depend on yahoo?) End rant. I promote Koha wherever I can, but in my job I've got to stay practical. Over the last four years we've put in place a marvelous OPAC meeting our users requirements. Please keep up the good work, but please also maintain core stability. Compare with Debian (lenny, squeeze, wheezy, 2 year cycle); Ubuntu (lynx, pangolin, tahr, 2 year cycle); Apache (2.2 ==> 2.4, eight/ten? year cycle); MySQL (fairly minor in the 5. series, no urgency); Perl (ditto); etc... Best -- Paul

4 3

RFC: proposing change to Koha's plugins system
by Indranil Das Gupta 21 Aug '14

21 Aug '14

Hi all, I've been trying to use the KPZ structure in some of my projects. In general, I've found it rather useful, with a few modifications. I would like to propose the following changes as http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12805 lets have your feedback on this. cheers -indra -- Indranil Das Gupta Phone : +91-98300-20971 Blog : http://indradg.randomink.org/blog IRC : indradg on irc://irc.freenode.net Twitter : indradg -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=- Please exchange editable Office documents only in ODF Format. No other format is acceptable. Support Open Standards. For a free editor supporting ODF, please visit LibreOffice - http://www.documentfoundation.org

1 0

Divergent handling (?) of Koha's <pluginsdir>
by Indranil Das Gupta 21 Aug '14

21 Aug '14

Hi, I'm wondering why Koha's <pluginsdir> is handled differently between git / tarball and .deb packages. I'm seeing certain divergence (i think?) as follows: 1) Installed master from git (3.17.00.014) - found /var/lib/koha/plugins to exist under /home/<user>/koha-dev, created off /home/<user>kohaclone/skel/var/lib/plugins. It is even defined in koha-conf.xml. 2) Downloaded and unzipped koha-latest.tar.gz - same thing, I see the folder "/var/lib/koha/plugins" under skel. 3) However in koha-common_3.16.02_all.deb, the same folder is not present. Instead, the directory has to be created as described in http://manual.koha-community.org/3.16/en/pluginsystem.html why is this so? thanks in advance. -- Indranil Das Gupta Phone : +91-98300-20971 Blog : http://indradg.randomink.org/blog IRC : indradg on irc://irc.freenode.net Twitter : indradg -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=- Please exchange editable Office documents only in ODF Format. No other format is acceptable. Support Open Standards. For a free editor supporting ODF, please visit LibreOffice - http://www.documentfoundation.org

1 0