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

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

Update on RM
by Brendan Gallagher 17 Apr '16

17 Apr '16

Hi All - I had a really busy week last week and was not able to dedicate time towards testing and pushing code. I have a busy Monday morning, but then after that I will get that PQA low again. We have about 2 weeks until the freeze, just a reminder, not a rallying call yet. Hoping the final month after the freeze we can get Master wicked stable. :). Cheers, Brendan -- Sent from Gmail Mobile

1 0

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

Call for News: April 2016 Newsletter
by kohanews 14 Apr '16

14 Apr '16

Fellow Koha users ~ I'm collecting news for the April 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

Biblio level visibility
by Mark Tompsett 14 Apr '16

14 Apr '16

Greetings, Thanks to those who helped get bug 15870 into master. What I was hoping was to get biblio level filtering for MARC working better in the OPAC, particularly bug 11592. This will let me turn my attention back to OpacHiddenItems as a filter, so that the expected visibility of things will be correct across the board, and make overrides (bug 10589) easier. GPML, Mark Tompsett

1 0

koha ldap for AD (ref)
by long_sam.tw 13 Apr '16

13 Apr '16

Dear all, koha ldap for AD (config & test) ref https://koha.wikispaces.com/koha_ldap_en

1 0

Reminder: Development IRC meeting 13 April 2016
by Katrin Fischer 12 Apr '16

12 Apr '16

Hi all, just the usual quick reminder that there is a developer meeting scheduled in a bit less than 24 hours: https://wiki.koha-community.org/wiki/Development_IRC_meeting_13_April_2016 Hope to see you there, Katrin

1 0

International ES sign-off testing day (next Tuesday/Wednesday)
by Brendan Gallagher 12 Apr '16

12 Apr '16

Hello All - I am hoping that we could have a day next week where we are in irc channel #koha and do some testing of Elastic. Ideally target that to be Wednesday for NZ UTC +12 (iirc) and Tuesday morning for me. The idea is that we'll have Chris (rangi) in channel to look at problems and fix problems that day as we bring them up to him. Nick (kidclamp) from ByWater will also be present as he has done the most testing on our side. Ideally we'll have some ES installs setup - hopefully (we bywater will have 2 identical datasets - 1 running ES and 1 running zebra (but with the ES code installed))... More setups are welcome. We could hopefully get everything set well so that we could get a sign-off that day and get this into QA. Also another thought is that we edit a wiki-page so that we can list things that ES is doing already - what system preferences effect it etc. Thanks, Brendan -- --------------------------------------------------------------------------------------------------------------- Brendan A. Gallagher ByWater Solutions CEO

5 6

NEKLS Job opportunity for NExpress Coordinator and ILS Systems Manager
by Heather Braum (NEKLS) 11 Apr '16

11 Apr '16

Last call for applicants. NEKLS will begin reviewing applications after April 15. The Northeast Kansas Library System <http://www.nekls.org/> (NEKLS) in Lawrence, KS <http://explorelawrence.com/>, has an opening and we’re looking for a diplomatic applicant with lots of energy, enthusiasm, and excellent custom service skills to come work with us! *NExpress Coordinator and ILS Systems Manager*: Opportunity for a creative librarian who will enjoy the challenge of managing a large regional shared consortia catalog, with 42 public libraries and 1 school district (public catalog <https://catalog.nexpresslibrary.org/>). The system runs on the Koha ILS <http://www.koha-community.org/>, an open source ILS used all over the world. Responsibilities include: - Providing overall management, support, and coordination of the NExpress ILS and consortia, including balancing needs of consortia with local library needs - Coordinating operations of NExpress team - Maintaining data quality of NExpress records and database - Coordinating with participating libraries and ILS support vendor regarding system features and bugs, migrations, upgrades, and software developments - Providing NExpress training to participating libraries, including planning & leading quarterly NExpress users group meetings - Participating in the international Koha community Qualified candidates will meet the following: - MLS degree preferred and 3 or more years of prior library experience is required. - Experience with integrated library automation system software is required. - Knowledge of cataloging best practices, database management (MySQL), web languages (HTML, CSS, JQuery), web CMS platforms (WordPress and LibGuides) is highly preferred. See the full job description, including qualification list <http://nekls.org/wp-content/uploads/2016/03/NExpress-Coordinator-Job-Descri…>, for more information ( http://nekls.org/wp-content/uploads/2016/03/NExpress-Coordinator-Job-Descri… ). Excellent salary ($50,000-$53,000) and benefits package, including complete health, dental, and vision coverage (single and family), short-term and long-term disability insurance, and retirement options. Position is open until filled. Evaluation of applications will begin on April 15, 2016 and will continue until position is filled. Estimated start date is on or around July 1, 2016. For questions, please contact Laura DeBaun, NEKLS Director, at ldebaun(a)nekls.org. Apply with cover letter, resume and references list by emailing Carolyn Little, Courier Coordinator, at clittle(a)nekls.org. Please use the subject line NExpress Coordinator Job Application. NEKLS is an equal opportunity employer. Heather Braum NExpress Coordinator Resource Sharing Librarian Northeast Kansas Library System hbraum(a)nekls.org "The illiterate of the 21st century will not be those who cannot read and write, but those who cannot learn, unlearn, and relearn." ~Alvin Toffler, *Rethinking the Future*

1 0

*smirk* Funny but bad, bug 16233
by Mark Tompsett 11 Apr '16

11 Apr '16

Greetings, My sign off of 16233 with <strong> in the title has triggered a strong open tag in effect on the dashboard. GPML, Mark Tompsett

1 0