https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16581
--- Comment #9 from David Cook <[email protected]> --- Overall, I'm in favour of using Indexdata's repository. As Mark pointed out, 2.0.62 appears to be the latest version: http://www.indexdata.com/zebra/doc/NEWS You'll notice that 2.0.60 is where the tokenization bug was fixed: Fix ICU phrase searches for terms split by ICU ZEB-664 You'll probably notice a big gap between 2.0.59 and 2.0.60. My emails to Indexdata prompted the fix for 2.0.60. You may also notice "Allow @attr 2=102 for numeric index" in 2.0.62. I had noticed that relevance ranking didn't work with a query containing a numeric index, so Indexdata fixed it. I don't think it really affects the ranking much per se, but it prevents the Zebra error. Note also that you an now browse Zebra's code on Github: https://github.com/indexdata/idzebra I don't know if they accept pull requests, but I wouldn't be surprised if they did. Of course, I don't know if Indexdata will be doing much work on Zebra going forward. I don't think they're answering the Zebra-list anymore: http://lists.indexdata.dk/pipermail/zebralist/2016-May/002645.html I think they're focusing their efforts on the FOLIO project these days. Tomas mentioned some time ago that Indexdata considered Zebra a legacy project, and that seems to be the case. All the more reason to move to Elastic, I suppose, although I see the utility of keeping Zebra around if only as a Z39.50 server. Makes you wonder if we should be thinking about turning Zebra into an optional component once Elastic takes over fully... -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
