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

Re: [Koha-devel] Jenkins (we want to move the server)
by Laurent Ducos 02 Mar '16

02 Mar '16

Hello. Jenkins Server is prodution for several weeks. Do you know if Jenkins server is backup and if so how? If the server breaks , I have no backup to rebuild it. Thanks.

2 2

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

Koha Community Newsletter: February 2016
by kohanews 01 Mar '16

01 Mar '16

Fellow Koha users: The Koha Community Newsletter for February 2016 is here: https://koha-community.org/koha-community-newsletter-february-2016/ Many thanks to the folks who submitted articles and news to this month's newsletter. Please feel free to email me with any corrections or suggestions. Thanks! -- Chad Roseburg Editor, Koha Community Newsletter

1 0

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

Repeated MARC field in Staff normal view
by akafortes 19 Feb '16

19 Feb '16

In the staff client normal view of a record, if you have a repeated MARC field then you'd get the all of the repeated entries in the same line separated by a coma. So for a example for a repeated 701 field you'd get something like this: 701_tag:701_value,701_value_of_repeated What I'd like to do is have each repeated field to be displayed in its own line 701_tag:701_value 701_tag:701_value_of_repeated If you see my previous post <http://koha.1045719.n5.nabble.com/Staff-Client-Normal-View-details-td587228…> you'll see why I want to do that. What I've tried is this: <xsl:call-template name="tag_7xx"> <xsl:for-each select="marc:datafield[@tag=701]"> <xsl:with-param name="label" select="marc:subfield[@code='4']" /> </xsl:for-each> </xsl:call-template> I've tried a few variations of this as well, but always with no success. Instead it removes the entire normal view from the staff client. Any help is greatly appreciated -- View this message in context: http://koha.1045719.n5.nabble.com/Repeated-MARC-field-in-Staff-normal-view-… Sent from the Koha-devel mailing list archive at Nabble.com.

2 3

Call for news: February 2016 Newsletter
by kohanews 17 Feb '16

17 Feb '16

Fellow Koha users ~ I'm collecting news for the February 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 Editor, Koha Community Newsletter

1 0

Bug 15809
by Marcel de Rooy 17 Feb '16

17 Feb '16

Hi all (especially members of QA team), I changed the status of bug 15809. But want to invite you to add your arguments too in favor or disfavor of the solution proposed. Thanks, Marcel

1 0