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

Zebra: the 'elements zebra::snippet' doesn't work
by Tajoli Zeno 11 Jan '17

11 Jan '17

Hi all, I trying to check my indexes in Zebra. My setup: OS: Debian jessie Koha: 3.20.7 [manual install] Zebra: 2.0.61 [install from IndexData repo] Format: UNIMARC Probably the fact that I use unimarc is relevant but I don't understand where. I do the debug described here: http://wiki.koha-community.org/wiki/Troubleshooting_Zebra#Why_does_a_search… The result of a working search is: Diagnostic message(s) from database: [25] Specified element set name not valid for specified database -- v2 addinfo 'zebra::snippet' but my ../etc/zebradb/retrieval-info-bib-dom.xml is correct: <?xml version="1.0" encoding="UTF-8"?> <retrievalinfo xmlns="http://indexdata.com/yaz"> <retrieval syntax="unimarc" name="F"> <backend syntax="xml" name="marc"> <marc inputformat="xml" outputformat="marc" inputcharset="utf-8" outputcharset="utf-8"/> </backend> </retrieval> <retrieval syntax="unimarc" name="B"> <backend syntax="xml" name="marc"> <marc inputformat="xml" outputformat="marc" inputcharset="utf-8" outputcharset="utf-8"/> </backend> </retrieval> <retrieval syntax="xml" /> <retrieval syntax="xml" name="index"/> <retrieval syntax="xml" name="marc" identifier="info:srw/schema/1/marcxml-v1.1"/> <retrieval syntax="xml" name="marcxml" identifier="info:srw/schema/1/marcxml-v1.1"/> <retrieval syntax="xml" name="zebra::*"/> </retrievalinfo> Do I need to check in other places for the setup of ' zebra::snippet' ? Bye Zeno Tajoli -- Zeno Tajoli / SVILUPPO PRODOTTI/ - Automazione Biblioteche Email: z.tajoli(a)cineca.it Fax: 051/6132198 *CINECA* Consorzio Interuniversitario - Sede operativa di Segrate (MI)

5 13

INSTALL.debian is outdated
by Jonathan Druart 27 Nov '16

27 Nov '16

2015-11-11 22:37 GMT+00:00 Robin Sheat <robin(a)catalyst.net.nz>: > Aparrish schreef op wo 11-11-2015 om 08:13 [-0700]: >> I followed the official instructions: >> http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=INSTALL.debian;hb… > > We need to delete those, they're from 2012 and are super out of date. Shall we 1) delete them, 2)replace them with the content of the wiki page or 3) just put a link to the wiki page?

12 23

Introduce the use of Grunt or Gulp?
by Owen Leonard 13 Oct '16

13 Oct '16

I would very much like to start using some kind of build tool for front-end assets in Koha. The ones I've encountered are Grunt and Gulp: Grunt: http://gruntjs.com/ Gulp: http://gulpjs.com/ I have some experience with Grunt, and have heard good things about Gulp. Has anyone else used either in their non-Koha projects? Adopting them would introduce a little more complexity to the process of making client-side changes to Koha, and to be honest I'm not sure of the right way to incorporate the tools into our workflow. What I see as the advantages: - Automatic linting, minification, and concatenation of CSS and JS - Potentially, automatic compression of images and contruction of image sprites - Overall performance improvements from the above Disadvantages: A new process to learn for those wanting to contribute front-end modifications. A new set of dependencies for front-end developers (Node.js etc). If there is interest I'd be happy to submit a patch introducing the process to the OPAC as a demonstration. -- Owen -- Web Developer Athens County Public Libraries http://www.myacpl.org

10 22

Who all are purposing Koha as an Union Catalog?
by Indranil Das Gupta 18 Apr '16

18 Apr '16

Hi all, At a recent conference here, there was discussions about utilizing Koha as an Union catalog. I would like to know how many / if anyone here is using Koha in that manner. And what is the experience so far, the extent of custom development etc thanks -- 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

2 3

Interface consistency: The buttons edition
by Owen Leonard 18 Apr '16

18 Apr '16

Sorry for being the guy who thinks way too much about buttons. I have added a section to the interface guidelines in the wiki all about buttons: https://wiki.koha-community.org/wiki/Interface_patterns#Buttons I think it's an accurate description of how we're doing things now. Please let me know if you have comments, disagree, or have a proposal for updating any of the de-facto standards we are working with. -- Owen -- Web Developer Athens County Public Libraries http://www.myacpl.org

2 1

How is relevance weighted in zebra search?
by Barton Chittenden 18 Apr '16

18 Apr '16

Hi, We just upgraded a library from Koha 3.0 to 3.22. After the upgrade, the library complained that the title "Golden Age" was at the bottom of their OPAC search results. I checked the obvious first: OPACdefaultSortField had been set to 'relevance' with OPACdefaultSortOrder set to 'ascending', which would definitely be backwards (least relevant first)... I changed to to 'ascending', and got exactly the same results. Restarting memcache didn't help. When I searched using yaz-client, I found that the results that were coming first in the list had the phrase "golden age" in 520$a. Here's the version of zebra: $ idzebra-config --version 2.0.59 At this point, I have two major questions: 1) Where do I check which fields are ranked more highly in a relevance search? (I would think that title should be ranked higher than 520$a -- summary). 2) Why didn't the sort order change when I changed OPACdefaultSortOrder from ascending to descending?

3 2

Improving Zebra logging
by David Cook 15 Apr '16

15 Apr '16

Hi all: As if you weren't all sick of me going on and on about Zebra. So you may or may not know that the Zebra logs are fairly useless in a package install of Koha. At Prosentient, we don't use package installs much, so I haven't noticed this until now, but here's a tip: If you want to see what requests are being made to Zebra, you can do the following: 1) vi /usr/sbin/koha-start-zebra 2) Under start_zebra_instance, you can change "-v none,fatal,warn" to "-v none,fatal,warn,request" (note that "request" is an undocumented log level but it should work. alternately remove none and requests should appear in the log) 3) sudo koha-zebra-stop 4) sudo koha-zebra-start 5) profit (or at least see the PQF which is sent to the server and whether you're getting errors or OK query responses) This is the kind of additional output you should expect to see: 14:15:00-17/11 zebrasrv(2) [request] Auth idPass kohauser - 14:15:00-17/11 zebrasrv(2) [request] Init OK - ID:81 Name:ZOOM-C/YAZ Version:4.2.30 98864b44c654645bc16b2c54f822dc2e45a93031 14:15:00-17/11 zebrasrv(2) [request] Search biblios OK 0 1 1+0 RPN @attrset Bib-1 @attr 1=1016 @attr 4=6 @attr 5=1 test Anyway, I wouldn't *actually* recommend changing /usr/sbin/koha-start-zebra since that's part of the koha-common package. but maybe someone would be interested in making change to the Zebra commands to allow for different logging levels. Other things to note: koha-zebra-restart isn't the same thing as koha-zebra-stop && koha-zebra-start. If you restart Zebra after changing the flags for daemon or zebrasrv, the changes won't be brought across.it's necessary to stop and start it again. even though the process is actually restarted. it seems to be restarted using the original configuration used when launching daemon in the first place. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St, Ultimo, NSW 2007

3 3

Plan for upgrading jQuery in the staff client
by Owen Leonard 08 Apr '16

08 Apr '16

I have filed a new bug with a plan for how to move forward on an upgrade of jQuery in the staff client. https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15883 I would love to hear other developers' comments about it. Thanks, Owen -- Web Developer Athens County Public Libraries http://www.myacpl.org

3 6

Exporting fine
by yash verma 31 Mar '16

31 Mar '16

is there anyway to export the fine data along with some user info in an xls format?

2 1

Freeze/Release dates coming up for 16.05
by Brendan Gallagher 31 Mar '16

31 Mar '16

Hi All - I will be setting a feature freeze of April 28th (End of Day) and a release date of May 26, 2016. All those patches that are not PQA by the end of day 28th April will not have a chance to be in the 16.05 release. Thanks, Brendan

1 0