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

Tags features
by Tomas Cohen Arazi 05 Mar '19

05 Mar '19

Hi all, while fixing issues with emojis in Tags (solved already in 21846, waiting from someone to stamp their QA signoff) I was told about 22420: tag cloud broken. Reverting the change from bug 14385 would 'fix it', meaning we restore the ability to properly scale tags based on their weight. I'm sending this email to clarify what is the expected behaviour that pretended to be introduced in 14385. It looks like it is trying to filter out those biblios that should be hidden in OPAC: cool. I can achieve this by decrementing the weights instead of what is done now. But then I noticed that the behaviour for logged in users is to display own tags only, and for anonymous users it displays all the tags? Can someone explain the desired behaviour so I don't make it worse while fixing the other problem? Thanks! -- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F

2 2

Koha Community Newsletter: February 2019
by Koha Newsletter 03 Mar '19

03 Mar '19

Sorry for the delays on the news! Ran into some technical difficulties with Wordpress. Special thanks to Liz for the technical help! The Koha Community Newsletter for February 2019 is here: https://koha-community.org/koha-community-newsletter-february-2019/ 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. Chad Roseburg Koha Community Newsletter Editor

1 0

Koha community site Wordpress issue
by kohanews 03 Mar '19

03 Mar '19

The Wordpress site koha-community.org will not save my edits and I'm unable to publish. Anyone know who manages that? Thank you! -- Chad Roseburg Editor, Koha Community Newsletter

3 2

Re: [Koha-devel] [Koha] Barcode Troubles
by Mark Alexander 01 Mar '19

01 Mar '19

Excerpts from abrazier's message of 2019-02-28 15:50:51 -0700: > While editing items that are being > added to our collection, when we click in the field (p - Piece > designation (barcode)) which we have always had set to (autoBarcode: > generated in the form 1, 2, 3) we are no longer getting the barcode we > expect to see. > > We suspect it is now going back to barcodes that once belonged to items > that are now deleted (because, that earlier barcode is now available). I took a look at the Koha source code, and it seems that for some barcode types, it is using this SQL to determine where to start generating new barcodes: select max(abs(barcode)) from items; It then increments the value that it obtains this way to use as the new barcode. So I suspect that you could fix your problem by creating a dummy item that has the first barcode you want to use, minus one. Note that I am not an expert and have not tried this myself.

1 0

SSL problem with lists.koha-community.org
by David Cook 01 Mar '19

01 Mar '19

Hi all, It looks like BibLibre might be in charge of lists.koha-community.org? https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel seems to be sending an expired self-signed certificate with BibLibre information. Someone might want to take a look at that. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595

2 1

Problems with "LOC" authorized values and tokenization
by David Cook 27 Feb '19

27 Feb '19

Hi all, I have a library with lots of problematic data in their "LOC" authorized value codes, and it's led me to a few issues. 1. LOC authorized values can contain "*", "(", and ")" but all of these characters will cause the ZOOM library to fail to compile the CCL2RPN query. 2. mc-loc (from the "Shelving location" tab on /cgi-bin/koha/catalogue/search.pl) seems to be doing an incomplete search. That means if you have two locations like "Big Box" and "Big Box - Drawer", "Big Box" will return items for both locations. The reason for #2 is actually kind of interesting. While the RPN/PQF query is "@attr 1=8013 @attr 4=1 apple_street" and @attr 4=1 represents a "phrase" search, Zebra is actually using the "w" register and not the "p" register. It's because of the "Completeness Attributes (type = 6)": "Incomplete subfield (1) is the default, and makes Zebra use register type="w", whereas Complete field (3) triggers search and scan in index type="p"." (https://software.indexdata.com/zebra/doc/querymodel-rpn.html) If we wanted to actually just get the exact location, we'd want to use "mc-loc,complete-field", but then we'd get Zebra errors because mc-loc doesn't use the "p" type register currently, although that would be easy enough to add. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595

3 4

zebraidx with 1 large MARC file rather than many small MARC files
by David Cook 27 Feb '19

27 Feb '19

Hi all, I haven't looked into it too deeply, but I was curious if Zebra would have better performance indexing with 1 large MARC file versus many small MARC files. At the moment, we generate 1 huge MARC file and then pass that to zebraidx as an argument. Is that something we've always done or was it done as a performance enhancement? I haven't looked at the Zebra internals to see whether it reads the entire file into memory and then processes it or if it parses the XML using a stream reader. Zebraidx can also take a list of files from stdin*, but if you had tonnes of small files that could be troublesome. I suppose it doesn't matter too much as we march on to ElasticSearch, but I figure lots of people are using Zebra still and probably will for a long time, so perhaps worth thinking about. https://software.indexdata.com/zebra/doc/zebraidx.html David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595

2 3

search result list is void of information
by giuseppe 26 Feb '19

26 Feb '19

Hello all, (already posted on koha-general, but maybe here a better place -- sorry for possible cross postings -- I will file a bug report if nothing happens here too) I've replaced an old Koha 17.11 by a fresh install of Koha 18.11 (on a fresh install of Debian 9.7 64bit). After install, as superlibrarian I successfully populated the DB with sample records including a couple of items, for test purposes. <http://koha.1045719.n5.nabble.com/file/t341209/Screenshot_2019-02-17_17-55-…> Afterwards, as normal user I tried a search for a keyword matching more than one record, and thus I got a list of search results. <http://koha.1045719.n5.nabble.com/file/t341209/Screenshot_2019-02-18_12-38-…> The list is correct, but, as you can see, each entry is void of textual information -- no title/author/etc. . If I click on the "image preview" of one single entry (not visible in the screenshot) I get access to the full info of that entry, which shows correct. But the search results void of textual information is uninformative for a user. This misbehaviour is also present in Koha 18.05 but not in Koha 17.11. Is this just a matter of misconfiguration? What should I do to restore the original behaviour? Thank you. -- Sent from: http://koha.1045719.n5.nabble.com/Koha-devel-f3063671.html

2 1

Limits cannot contain parentheses
by David Cook 26 Feb '19

26 Feb '19

Hi all, I noticed that the CCL2RPN parser throws fatal errors when limits have parentheses in them. I have a fix for it (described at https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22344) but it makes for an escaped $limit_cgi and an ugly $limit_desc. It doesn't break anything, but it's not aesthetically pleasing. Would people prefer an ugly fix that is easy to implement, or a more beautiful but difficult to implement fix? David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595

2 1

Re: [Koha-devel] FW: [Koha] Koha 18 support
by Fridolin SOMERS 26 Feb '19

26 Feb '19

Hi, Looks like your Zebra configuration is still in GRS-1 which is strongly deprecated. Try switch to DOM : https://wiki.koha-community.org/wiki/Switching_to_dom_indexing Which is you OS and how did you install Koha please ? Best regards, Le 23/01/2019 à 06:03, faiz(a)umt.edu.pk a écrit : > Dear Fridolin and Koha friends > > Our koha is not searching and when we rebuild Koha zebra it gives zebraidx error which is attached, our installation package is on ubuntu 16.04, when we rebuild Zebra from root login it works in the begning but as the indexing finishes after 20 min it starts generating errors, please share resolution. > > > Kind Regards > > > Muhammad Faiz Chishti > Team Lead Systems > Office of Technology Support (OTS) > University of Management and Technology > C 2 Johar Town > Tell: +42 111300200 Ext: 3640 Cell: +923054440632 > Website: www.umt.edu.pk Email: faiz(a)umt.edu.pk > > Please consider the environment before printing this email. > > > -----Original Message----- > From: faiz(a)umt.edu.pk <faiz(a)umt.edu.pk> > Sent: Tuesday, January 22, 2019 8:30 PM > To: 'Fridolin SOMERS' <fridolin.somers(a)biblibre.com>; 'koha(a)lists.katipo.co.nz' <koha(a)lists.katipo.co.nz>; 'koha-devel' <koha-devel(a)lists.koha-community.org> > Subject: RE: [Koha] Koha 18 support > > Dear brother > > We are using a pre compiled version by total library solution, We are facing error with zebra, it fails and the stops Koha search, we than rebuild Koha index and restart the server 2 or three times, this in return brings the service up. Now when we rebuild zebra it gives zebraidx error and does not rebuild. > > > The error is attached > > Kind Regards > > > Muhammad Faiz Chishti > Team Lead Systems > Office of Technology Support (OTS) > University of Management and Technology > C 2 Johar Town > Tell: +42 111300200 Ext: 3640 Cell: +923054440632 > Website: www.umt.edu.pk Email: faiz(a)umt.edu.pk > > Please consider the environment before printing this email. > > > -----Original Message----- > From: Koha <koha-bounces(a)lists.katipo.co.nz> On Behalf Of Fridolin SOMERS > Sent: Tuesday, January 22, 2019 8:20 PM > To: koha(a)lists.katipo.co.nz; 'koha-devel' <koha-devel(a)lists.koha-community.org> > Subject: Re: [Koha] Koha 18 support > > Hi > > What is your zebraidx error ? > > How did you install ? Debian Package ? > > Regards, > > Le 22/01/2019 à 11:31, faiz(a)umt.edu.pk a écrit : >> >> We are facing error with our daily Cron jobs, it fails and the stops Koha search, we than rebuild Koha index and restart the server 2 or three times, this in return brings the service up. Now when we rebuild zebra it gives zebraidx error and does not rebuild. >> >> We require support and maintenance of our locally installed instance. >> >> >> - Current system >> * Koha 18.05 >> >> - Number of bibliographic records >> * 127K >> >> - Average annual circulation >> * 35K approx. >> >> >> >> Kind Regards >> >> >> Muhammad Faiz Chishti >> Team Lead Systems >> Office of Technology Support (OTS) >> University of Management and Technology C 2 Johar Town >> Tell: +42 111300200 Ext: 3640 Cell: +923054440632 >> Website: www.umt.edu.pk Email: faiz(a)umt.edu.pk >> >> Please consider the environment before printing this email. >> >> > > -- > Fridolin SOMERS <fridolin.somers(a)biblibre.com> BibLibre, France - software and system maintainer _______________________________________________ > Koha mailing list http://koha-community.org Koha(a)lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha > -- Fridolin SOMERS <fridolin.somers(a)biblibre.com> BibLibre, France - software and system maintainer

1 0