February 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

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

Re: [Koha-devel] [Koha] Koha Search Indexes
by David Cook 01 Mar '16

01 Mar '16

Hi Nicole, I keep meaning to look over and revise the search documentation, but I always seem preoccupied with other work. I'm not sure whether or not the list at http://manual.koha-community.org/3.24/en/kohasearchindexes.html is complete at a glance. To be honest, while I think it's a valuable list, I think it would be more valuable for end users to have a list of CCL qualifiers (and their corresponding registers). While an index may exist in Zebra, it's the CCL qualifier that the user needs to know in order to access it, and sometimes the qualifier is difference than the index name. There are 3 vital files for Zebra indexing and Koha searching: bib1.att biblio-zebra-indexdefs.xsl ccl.properties bib1.att defines which indexes may exist. Biblio-zebra-indexdefs.xsl decides what MARC data goes into which indexes. ccl.properties provides a query language for accessing those indexes through search queries. Paul asked about the suffixes :n, :p, :w, :u, and :s. These are called "registers". :n is numeric, :p is phrase, :w is word, :u is URL, and :s is sorting. Different types of CCL qualifiers allow us to access different types of registers. "st-numeric" provides access to the :n register. "st-phrase" and "phr" access :p. "st-word", "st-word-list", and "wrdl" access ":w", "st-urx" accesses :u, and generally we don't need to access :s when searching as that's a behind-the-scenes thing for Koha to worry about. Different registers have different normalization rules. If we look at biblio-zebra-indexdefs.xsl, we can see that MARC 245 is indexed into Title:w and Title:p. That means "Harry Potter and the Philosopher's Stone" would be indexed something like so: <title:w>Harry</title:w> <title:w>Potter</title:w> <title:w>Phllosopher's</title:w> <title:w>Stone</title:w> <title:p>Harry Potter and the Philosopher's Stone</title:p> So if we did a search like... "title,wrdl=Harry", we'd get a hit for that MARC record. If we did a search like 'title,phr="Harry Potter and the Philosopher's Stone"', we'd get a hit for that MARC record. I'll draw your attention now to 952$u. It's indexed as uri:u (although it would also show up in the Any:w and Any:p keyword indexes). In order to access uri:u, we'd need to search for 'uri,st-urx="http://koha-community.org"'. The "st-urx" maps to the ":u", and we see "uri" in "ccl.properties" which maps to "uri" in bib1.att. If we tried to do a search for 'uri,wrdl="http://koha-community.org"', it would fail, because nothing is indexed in the "uri:w" index:register combo. I have to run to an appointment, but hopefully that helps a bit. One day, I'd like to write a program which parses ccl.properties to provide a list of qualifies that cross-references with biblio-zebra-indexdefs.xsl to see which registers are available for which qualifier/index pair. The register system is a bit complicated but it can be useful. I've recently started doing more with the ":u" register... David Cook Systems Librarian Prosentient Systems 72/330 Wattle St, Ultimo, NSW 2007 > -----Original Message----- > Date: Mon, 1 Feb 2016 11:21:01 -0600 > From: Nicole Engard <nengard(a)gmail.com> > To: Paul A <paul.a(a)navalmarinearchive.com> > Cc: Koha <Koha(a)lists.katipo.co.nz>, koha-docs(a)lists.koha-community.org > Subject: Re: [Koha] Koha Search Indexes > Message-ID: > <CAC0K6VHYbER_h2B8pXmVRu8Q9=3rLVaqzOJb=SKiHPTMsYagfg@ > mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > I'd love if someone could help me there. > > Nicole > > On Mon, Feb 1, 2016 at 10:35 AM, Paul A <paul.a(a)navalmarinearchive.com> > wrote: > > > At 08:42 AM 2/1/2016 -0600, Nicole Engard wrote: > > > >> Hello all, > >> > >> I updated this page in the manual > >> http://manual.koha-community.org/3.24/en/kohasearchindexes.html > because > >> there were many indexes not listed in there. Would index experts please > >> take a look to make sure I caught all of the indexes? > >> > > > > Many thanks. Could you possible add an explanation of the suffixes :n, :p, > > :w, :u (URL?) and :s? > > > > Tnx and br -- Paul > > > > --- > > Maritime heritage and history, preservation and conservation, > > research and education through the written word and the arts. > > <http://NavalMarineArchive.com> and <http://UltraMarine.ca> > > > > _______________________________________________ > > Koha mailing list http://koha-community.org > > Koha(a)lists.katipo.co.nz > > https://lists.katipo.co.nz/mailman/listinfo/koha

3 2

Reminder: Developer IRC meeting 1 March 2016, 15 UTC
by Jonathan Druart 29 Feb '16

29 Feb '16

Hi developers, There is a developer IRC meeting tomorrow, 1 March 2016, at 15 UTC. Find the local time here: http://www.timeanddate.com/worldclock/fixedtime.html?msg=Koha+Developers+IR… And the agenda: https://wiki.koha-community.org/wiki/Development_IRC_meeting_1_March_2016 Cheers, Jonathan

1 0

Editing help files
by Paul A 26 Feb '16

26 Feb '16

I have looked at Bug 10232 - Permission check for editing help files is broken -- but it does not appear to address my problem: even as "superlibrarian" I cannot edit help files, getting the following: Online Help WARNING: You will not be able save, because your webserver cannot write to '/usr/share/koha/intranet/htdocs/intranet-tmpl/prog/en/modules/help/mainpage.tt'. Contact your admin about help file permissions. chmod 666 on the *.tt files (they are/were 644) seems to cure the problem, but I am not certain if this introduces any unforeseen consequences -- not paranoid, but to make files writable by anyone without permission is perhaps a tad dubious. Can anyone reassure me, please? Thanks -- Paul

1 0

KohaCon16 - Registrations & Call for proposals Open
by Γιάννης Κουρμούλης 23 Feb '16

23 Feb '16

Dear koha lists members We are pleased to announce that Registration <http://kohacon2016.lib.auth.gr/?page_id=24> and Call <http://kohaCall/> for Proposals <http://kohacon2016.lib.auth.gr/?page_id=29> are now open for Kohacon16! Registration is free. Developers, technical support staff, librarians are invited to share their experience by contributing with a presentation proposal based on their knowledge, ideas, best practices and even mistakes! (Please note that all presentations will be in English). KohaCon16 will be organized by the Library & Information Centre and will be held at the Aristostle University of Thessaloniki on 30 May – 4 June 2016. For detailed information and updates, please visit the *KohaCon16 site* <http://kohacon2016.lib.auth.gr/>. “Let's make it Ko-ha-ppen!” KohaCon16 Library & Information Center Aristotle University of Thessaloniki GR-54124 Thessaloniki Greece tel: +30 2310 99 5368 <+302310995368> email: <kohacon16(a)lib.auth.gr>kohacon16(a)lib.auth.gr url: kohacon2016.lib.auth.gr

3 2

Disabling multiple submission on search form
by SUZUKI Arthur 22 Feb '16

22 Feb '16

Hello, We are facing the following problem on our installation of Koha. Some impatient users tends to click several times on the "Go" button of the search form on OPAC. Probably in a desperate hope that this will speed up the whole process. However the result is quite opposite, as Zebra is then queried multiple times which increases the server cpu load, until it reach 100% and cause Denial of Service (boooh...) We had the idea of disabling the "searchsubmit" button upon first click. This is done by adding onclick="this.disabled=true;" after "id=searchsubmit" in masthead.inc. Here is a SED command to make it easier. sed -i -e 's/id="searchsubmit"/id="searchsubmit" onclick="this.disabled=true; this.form.submit(); return true;"/' src/koha-tmpl/opac-tmpl/bootstrap/en/includes/masthead.inc Did any of you already faced similar problems? Any other ideas or implementation are welcome! Arthur SUZUKI Service informatique des bibliothèques bIBLIOTHÈQUES UNIVERSITAIRES Université Jean Moulin Lyon 3 6 Cours Albert Thomas - B.P. 8242 - 69355 Lyon Cedex 08 ligne directe : +33 (0)4 78 78 79 16 | http://bu.univ-lyon3.fr L'Université Jean Moulin est membre fondateur de l'Université de Lyon

3 3