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

Working on Koha interface guidelines
by Owen Leonard 08 Mar '16

08 Mar '16

A while ago I started a page on the wiki for describing common interface patterns in Koha. I've made some additions to it over the last couple of weeks, and I hope to continue to expand it. https://wiki.koha-community.org/wiki/Interface_patterns As you can see it has been long enough since I started that the first screenshots look out of date. Updating them is on my to-do list. However I think the guidelines are still accurate. To a certain extent, this document is both a catalog of how we generally do things in the staff client template and an explanation of my understanding of /why/ we do some things the way we do. If anyone has any questions or suggestions I would love to hear them. -- Owen -- Web Developer Athens County Public Libraries http://www.myacpl.org

2 2

New "renew" shortcut conflicts with previous use of the accesskey attribute
by Owen Leonard 06 Mar '16

06 Mar '16

The staff client uses (albeit inconsistently) the "accesskey" attribute in some dialogs where a Yes/No choice is offered: Yes, delete (Y) / No, don't delete (N) I've just seen that the addition of the renew tab in the header search form assigned "Alt-y" to the renew form. These two shortcuts can't coexist. I personally use the accesskey option when it is available (and when it works), but I imagine not many people do. Is it not worth keeping? -- Owen -- Web Developer Athens County Public Libraries http://www.myacpl.org

2 1

Wiki - Delete/disable user Xdbmsx
by David Nind 04 Mar '16

04 Mar '16

Hi. I accidentally approved a new wiki user last night (I thought I had rejected it, but must have approved it :-( ). Could someone who has permission disable/block the user Xdbmsx as I don't have permissions to do this. The user has also created several pages that need to be deleted. Apologies for this.... David Nind | david.nind(a)gmail.com PO Box 12367, Thorndon, Wellington, New Zealand 6144 m. +64 21 0537 847 | w. +64 4 8906 098

3 3

Patron searching change 'start_wtih' / 'contain' Bug 15252 / 15930
by Nick Clemens 04 Mar '16

04 Mar '16

Hello all, In bug 15252 a change was introduced to fix the problem of too many / irrelevant results when searching for patrons with multi-part names e.g. 'jean paul' 'mac beth' 'le guelec' This change now defaults many searches to 'start_with' and does not split terms for a 'start_with' search. This does not affect members-home.pl, but many other patrons searches request.pl, common/patron_search.tt ... A side effect of this change is that searching for a patrons full name i.e. 'Henry Acevedo' or 'Edna Acosta' returns no results as it is searching for [firstname like 'edna acosta%'] it also prevents searches like 'Ed aco' from finding results. The searches above returned results through 3.18, but 15252 is in 3.20.8 and 3.22.2 and master As we are seeing libraries upgrade to the newer versions we are hearing complaints as this is a big behaviour change from their viewpoint. Jonathan and I have been discussing on Bug 15930 and the options we have so far are: 1/ add a special case to search on firstname and surname (if start_with) 2/ add a pref to default on contains or start_with 3/ let the libraries who want a different behavior modify the default with some JS code 4/ add phrase searching with quotes and split terms otherwise Ideally we want to allow for ease in finding multi part names, but not introduce a change for single part names Thoughts?

2 1

Jenkins status
by Tomas Cohen Arazi 03 Mar '16

03 Mar '16

Hi everyone, on a recent plugin upgrade it seems jenkins configuration lost track of the git repositories each task must follow. I'm fixing it. Sorry for the inconvenience, and thanks Jonathan for reporting it. -- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F

1 0

RM update - May 2nd
by Brendan Gallagher 03 Mar '16

03 Mar '16

Hi All - It's been a little bit of time since I've posted. Sorry it's ended up being a long email. ( Easier to say most of this here instead of posting all this into an IRC meeting) ;) Currently the PQA is very low. I encourage all of you to review the needs sign-off page and test some of the wonderful code that many of us have written. Just to remind - the dashboard is a great place to start (everyone should have that one bookmarked - I hope I didn't date myself with that term). http://dashboard.koha-community.org/ - Also here is a link to the Bugzilla page that has the Needs Signoff queue - http://tinyurl.com/h3zdxec . Remember that Bugzilla is only the name of the tracker that we are using - it's not only bugs but also features and other coding needs for Koha. ;) Also a reminder for those that are newer to testing - try out the sandboxes - https://wiki.koha-community.org/wiki/Sandboxes (please remember that you can also ask any of us for help). I know that there are a few things that I need to follow up on for some recent patches that have been pushed. I'm on them and tracking them. Thankfully no one is using Master in production :) As always if I have missed something or I have made a mistake - please let me know and I thank you all for the times you have pointed out a spot I missed (those curly brackets if you know what I mean) Somethings I'd like to concentrate on going forward. 1. Speed. two bugs in general - https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15350 https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15341 Any and all help is welcome here. Jonathan has been presenting thoughts and comments about this for awhile now - let's all help there. There are some others too and we should all think about this. I feel like we are loading too much with each page. Also dbix::class should be examined. 2. Elastic Search - https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12478 Is the main bug where there are comments, code and thoughts. I think we need a sign-off on this and get this into QA with larger discussions happening. The Main goal for now is that it doesn't break anything with Zebra and we can push this in experimental. There are some good comments and questions on the bug. 3. Staying on top of PQA queue so our developers do not have to spend time rebasing code. I will hopefully maintain that. (sorry for those that have had to rebase so far) 4. Continue to encourage new signoff champions! This is on all of us to encourage and help those that want to do this and have time to do it. We can do it. 5. EDIfact code - needs a signoff. https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7736 and https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15630 great work by PTFS-europe and nice job by Kyle Hall on making it plugable so that it works around the standards. (Also I encourage PTFS-europe on submitting more of their code - they are sitting on a few gems right now that will be great for Koha - so if you see their code come it - let's test it). 6. Jenkins - I would like to see Jenkins pass as stable for Master in the near future. I will be spending sometime working on that. I know this turned into a long email. But let's do it! Cheers, Brendan -- --------------------------------------------------------------------------------------------------------------- Brendan A. Gallagher ByWater Solutions CEO Support and Consulting for Open Source Software Installation, Data Migration, Training, Customization, Hosting and Complete Support Packages Headquarters: Santa Barbara, CA - Office: Redding, CT Phone # (888) 900-8944 http://bywatersolutions.com info(a)bywatersolutions.com

1 0

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