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

incremental backup of the DB
by Indranil Das Gupta 17 Nov '15

17 Nov '15

Hi all, I'm facing a situation that between full backups, I would like to take incremental backups. Anyone have played with mysql incremental backup and Koha? any known issues? 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

Working around annoying OpacSuppression 114 error in Zebra using special attribute 14
by David Cook 17 Nov '15

17 Nov '15

Hey all: I just opened Bug 15198 (http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15198) which contains some instructions for how to make it so that you can turn on OpacSuppression and still retrieve search results, even if you don't have any suppressed records (942$n = 1) in Zebra. I ramble about it below but everything you actually need to know is in the bug report. I would supply a patch myself, but I'm having issues building Perl dependencies for Master, so I won't be contributing any patches until I get that sorted. Cheers, -David -- So I was reading the Zebra docs again (as you do), and I noticed a special attribute type of 14 which could help out with our OpacSuppression issue (whereby you get 0 results - well actually a 114 error - if you don't have any records suppressed but are sending queries checking for suppression). Observe: Z> find @attr 14=1 @not @attr 1=4 test @attr 1=9011 1 Sent searchRequest. Received SearchResponse. Search was a success. Number of hits: 8, setno 20 SearchResult-1: term=test cnt=8, term=1 cnt=0 records returned: 0 Elapsed: 0.000678 Z> find @not @attr 1=4 test @attr 1=9011 1 Sent searchRequest. Received SearchResponse. Search was a bloomin' failure. Number of hits: 0, setno 21 Result Set Status: none records returned: 0 Diagnostic message(s) from database: [114] Unsupported Use attribute -- v2 addinfo '9011' Elapsed: 0.000650 Here's the info about attribute type 14 from the Zebra docs (http://www.indexdata.com/zebra/doc/querymodel-zebra.html) Specifies whether un-indexed fields should be ignored. A zero value (default) throws a diagnostic when an un-indexed field is specified. A non-zero value makes it return 0 hits. Cheers to Jesse Weaver for realizing the syntax was @attr 14=1. For those of you who don't read PQF, I'll do it in CCL too: Z> find ignore-empty=(kw=test not Suppress=1) Sent searchRequest. Received SearchResponse. Search was a success. Number of hits: 97, setno 2 SearchResult-1: term=test cnt=97, term=1 cnt=0 records returned: 0 Elapsed: 0.000969 Z> find kw=test not Suppress=1 Sent searchRequest. Received SearchResponse. Search was a bloomin' failure. Number of hits: 0, setno 3 Result Set Status: none records returned: 0 Diagnostic message(s) from database: [114] Unsupported Use attribute -- v2 addinfo '9011' Elapsed: 0.000841 *Note that I just added "ignore-empty 14=1" to my ccl.properties to get that ignore-empty=() to work. Actually, the lightest touch for this issue would be to change: Suppress 1=9011 To Suppress 1=9011 14=1 Check that out: Z> find kw=test not Suppress=1 Sent searchRequest. Received SearchResponse. Search was a success. Number of hits: 97, setno 1 SearchResult-1: term=test cnt=97, term=1 cnt=0 records returned: 0 Elapsed: 0.005849 David Cook Systems Librarian Prosentient Systems 72/330 Wattle St, Ultimo, NSW 2007

2 2

Call for Development News: November Newsletter
by kohanews 14 Nov '15

14 Nov '15

Let the community hear what cool things you're working on! Send me some bugs that need testing, sign-offs and user feedback. k o h a news AT gmail dot com Thank you! -- Chad Roseburg Editor, Koha Newsletter

1 0

Call for News: November Newsletter
by kohanews 14 Nov '15

14 Nov '15

Fellow Koha users ~ I'm collecting news for the November 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

1 0

People's names on the Release Notes 3.22
by Tomas Cohen Arazi 13 Nov '15

13 Nov '15

Hi everyone, if you look at the relesae notes for the beta, you might notice some glitches on the names/addresses/companies/library names. Those are extracted from the commits, so not my fault :-D But most of them can be fixed manually. Just let me know and I'll do it. -- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B76C 6E7C 2D80 551A C765 E225 0A27 2EA1 B2F3 C15F

2 1

Searching numeric ranges
by Barton Chittenden 13 Nov '15

13 Nov '15

I am working on searching lexile number ranges. ccl.properties shows lex 1=9903 r=r The 'r=r' bit means that I should be able to search using a numeric range separated by a dash, e.g. 500-600 Should return any numeric results from 500 to 600. The following query works: cgi-bin/koha/catalogue/search.pl?q=ccl%3Dlex%2Cst-numeric%3D500-600 However, when I try adding that as an item in the search menu, as follows: $(document).ready(function(){ //add lexile to search pull downs $("select[name='idx']").append("<option value='lex,st-numeric'>Lexile (e.g. 600 or 550-650 )</option>"); }); That gets munged... the url reads cgi-bin/koha/catalogue/search.pl?idx=lex%2Cst-numeric&q=500-600 And I get the following message: No results found No results match your search for 'lex,st-numeric: 500-600'. --Barton

2 4

Trying to contact Zeno Tajoli at Cineca...
by David Cook 12 Nov '15

12 Nov '15

Hi Zeno: I CCed you into my koha list response, but I'm getting unrecoverable errors trying to send to you. Here's the relevant line: <-- 554 5.7.1 <z.tajoli(a)cineca.it <mailto:z.tajoli@cineca.it> >: Recipient address rejected: Failed SPF check; prosentient.com.au, Unknown mechanism type 'ip' in 'v=spf1' record I'm guessing that your v=spf1 record might contain "ip" instead of "ip4"? I don't know much about SPF, but that's my best guess. Thought I'd try to send you a head's up about it via the listserv in any case. Maybe it's a problem on my end but it's not happening when I send email to anyone else. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St, Ultimo, NSW 2007

1 0

Koha 3.22 beta released
by Tomas Cohen Arazi 12 Nov '15

12 Nov '15

A beta release of Koha 3.22 is now available for download. We encourage all users of Koha to consider downloading and testing the beta prior to its release later this month. Debian packages for this beta will be available soon on the unstable repository. Koha 3.22 is a major release, that comes with many new features. This beta preview is released for testing purposes. Its use on production sites is discouraged. Draft release notes and download links can be found below. Share and enjoy (and test)! Download: http://koha-community.org/download-koha/ Draft release notes: http://koha-community.org/koha-3-22-beta-released/ <http://koha-community.org/koha-3-20-beta-released/> Note: if you want to try the new Plack integration, read the instructions here: http://wiki.koha-community.org/wiki/Plack Thanks everyone! -- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B76C 6E7C 2D80 551A C765 E225 0A27 2EA1 B2F3 C15F

1 0

Re: [Koha-devel] Benchmarks - prior to the 3.22 release
by Paul A 09 Nov '15

09 Nov '15

At 06:26 PM 11/9/2015 +0000, Jonathan Druart wrote: >2015-11-09 17:56 GMT+00:00 Paul A <paul.a(a)navalmarinearchive.com>: > > At 04:30 PM 11/9/2015 +0000, Jonathan Druart wrote: > >> > >> Hi devs, > >> > >> Please have a look at the these benchmarks: > >> > >> http://wiki.koha-community.org/wiki/Benchmark_for_3.22 > >> > >> I let you draw the appropriate conclusions. > > > > > > Jonathan, > > > > Is there a write up (perhaps specific code examples) on how these > benchmarks > > are obtained? How fast are the machines (server and client)? allow any > > caching? if from a work station, what browser, and how is latency > > compensated for? > > > > For example, using one of our cataloguers' workstations -- not exactly > > modern, cache disabled, and using a 10/100 ethernet card on our Gigabit LAN > > -- with Firebug "Net", I can "add item" in 1.66s (onload: 1.68s) -- the > > actual POST additem.pl is 698ms, and nearly all the remainder is > GETting the > > various *.js (utilities.js slowest at 156ms) and *.css (skin.css slowest at > > 125ms) > > > > But -- I'm maybe comparing "apples and pears" to the benchmarks on the > Wiki. > >Yes you are, see first lines on the wiki page. Thanks for the pointer. Next week I can probably mirror our prod. machine back to a sandbox. Is your script specific to 3.16|18 or should it run on 3.8.24 on Ubuntu 14.04? If there's a chance of success, I can certainly give it a try... Best -- Paul

1 0

Re: [Koha-devel] Benchmarks - prior to the 3.22 release
by Paul A 09 Nov '15

09 Nov '15

At 04:30 PM 11/9/2015 +0000, Jonathan Druart wrote: >Hi devs, > >Please have a look at the these benchmarks: > >http://wiki.koha-community.org/wiki/Benchmark_for_3.22 > >I let you draw the appropriate conclusions. Jonathan, Is there a write up (perhaps specific code examples) on how these benchmarks are obtained? How fast are the machines (server and client)? allow any caching? if from a work station, what browser, and how is latency compensated for? For example, using one of our cataloguers' workstations -- not exactly modern, cache disabled, and using a 10/100 ethernet card on our Gigabit LAN -- with Firebug "Net", I can "add item" in 1.66s (onload: 1.68s) -- the actual POST additem.pl is 698ms, and nearly all the remainder is GETting the various *.js (utilities.js slowest at 156ms) and *.css (skin.css slowest at 125ms) But -- I'm maybe comparing "apples and pears" to the benchmarks on the Wiki. Best -- Paul

2 1