March 2019 - 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