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

"Get desktop application" link
by dcook＠prosentient.com.au 16 Jan '20

16 Jan '20

Hi all, I'm just poking around on 19.11 and I notice the "Get desktop application" link on /cgi-bin/koha/circ/circulation-home.pl points to ByWater's Github. Is that an optimal link or should it be pointing to a Koha Community resource? David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595

3 4

String Freeze
by Joy Nelson 15 Jan '20

15 Jan '20

Greetings! Just a quick note that string freeze is effect today 01/15/2020 for the maintenance branches. Maintenance releases scheduled for the 22rd. Let the translations begin! Thanks! joy -- Joy Nelson President, Koha Division ByWater Solutions <http://bywatersolutions.com> Support and Consulting for Open Source Software Phone/Fax (888)900-8944 What is Koha? <http://bywatersolutions.com/what-is-koha/>

1 0

Out of sort memory, consider increasing server sort buffer size
by Philippe Blouin 15 Jan '20

15 Jan '20

Good morning Koha, Newbie question: why do we have 16 fields in GROUP BYs ? Are they really all necessary to eliminate duplicate lines in budgets? Genuine question. When in acqui-home.pl, clicking certain entries linking to spent.pl just crashes with the error listed in the mail's object: Out of memory. Although I hate that solution, I went with it, increased sort_buffer_size 64x fold (I'm a generous guy). Still not enough. Removing most lines in GROUP BY of spent.pl solves it all, of course. -- Philippe Blouin, Directeur de la technologie Tél. : (833) 465-4276, poste 230 philippe.blouin(a)inLibro.com <mailto:philippe.blouin@inLibro.com> inLibro | pour esprit libre | www.inLibro.com <http://www.inLibro.com>

3 7

Call for news: January 2020 Koha Newsletter
by kohanews 15 Jan '20

15 Jan '20

I'm collecting news for the January 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. Thank you! -- Chad Roseburg Editor, Koha Community Newsletter

1 0

Question about correct hold availability checking in the OPAC
by Owen Leonard 07 Jan '20

07 Jan '20

Bug 19298, "allow_onshelf_holds is not calculated correctly in opac-shelves" added a check of circulation rules to control whether the "Place hold" button should appear on the OPAC list contents page. I'm trying to restart my work on Bug 13121, "Move search results "action" links ("Place hold," "Add tag," etc) into include file" and so I'm interested in having unified template logic. Does anyone know if there was a reason the change made in Bug 19298 wasn't made to the OPAC search results page? Thanks, -- Owen -- Web Developer Athens County Public Libraries (740) 737-6006 https://www.myacpl.org

2 2

Urungi for building dashboards on Koha database
by Paul Poulain 06 Jan '20

06 Jan '20

Hello koha-devel, First of all, happy new year ! This new year comes with a finalized version of Urungi and availability of some dashboards & layers for building your own dashboards & reports. I'm happy to share all our work with the Koha community, and would be even happier with some feedback, suggestions, and contributions ! Urungi Urungi can be downloaded here : https://github.com/biblibre/urungi/releases Some new features since v1: * export reports and dashboards in PDF or PNG * theme management. Urungi 2.1.0 is provided with 2 themes for theming your dashboards in a few clicks. More themes can be added easily, it's just a CSS * a reports or dashboard can now be made public, ie available through an URL, without any login * Minor improvements: o you can rename a field when building a report, to have a more meaningful legend o crossed reports are based on HTML table, more consistency with other reports Urungi-data Urungi is pretty an empty box without the proper layers and some dashboards for Koha. That's why we've created another repo, where we store & publish them. You can find them on a specific repository, available at : https://github.com/biblibre/urungi-data You'll find there what we made for french UNIMARC libraries. I'm looking for some volunteers who would like to translated them to English. It's pretty easy even if you don't speak french for the French>English translation, a little bit more tricky for the MARC21 specific things. If you want to work on that, just drop me an email, I'll give your some directions on how to do that. Note that someone is already working on a translation to Spanish Contributing How to contribute ? As usual you can submit issues on github if you face any problem or would like a feature to be added. Urungi is currently available only in English and French. If you want to translate (Urungi, not Koha layers/reports/dashboards), welcome https://github.com/biblibre/urungi/tree/master/language Demo platform our demo, based on our koha demo, is available at: https://intranet-demo.biblibre.com/urungi/ login bibliotheque password 9sDDn3o11T It contains layers, reports and dashboards that are available on urungi-data Feedback welcomed ! I would be more than happy to have feedback on Urungi, urungi-data, features, bugs, dashboards. Feel free to share any work you do. Note that in march we will replace the static page urungi.org by a brand new website (based on WordPress) -- Paul Poulain, Associé-gérant / co-owner BibLibre, Services en logiciels libres pour les bibliothèques BibLibre, Open Source software and services for libraries

1 0

Koha, jump
by Jonathan Druart 30 Dec '19

30 Dec '19

Hi devs, I have been spending some hours on a plugin lately. The plan was to understand a bit the new capabilities that were added recently. Also I wanted to quickly implement an idea I had few weeks ago. So far everything is dirty, but I wanted to share it as soon as I had something that was more or less working. The plugin is named "koha-plugin-jump" and is available on my gitlab repository. >From the README: """ It started with a simple idea then it got complex, as always. So far the UI, the design and the code are ugly. The first idea was to add a simple method to jump from one page to another, then came the idea to generate data on demand, then data that matches given conditions, then etc. What's possible so far: * Jump to the following entities: biblio, item, itemtype, libraries, list (shelves) * Create one of those entities, with or without attributes of your choices Example: * jump biblio The art of will display the list of bibliographic records matching "The art of" in their title, when selected you will be redirected to the selected record * create item will create a new item * create 10 item biblionumber=20 will create 10 items attached to the bibliographic record with the biblionnumber=20 """ I cannot continue to develop alone this plugin so I would love to get some help on it, if you think it could be helpful to you as well. To install it you will have to generate the kpz file (not released using the gitlab workflow yet): % git clone https://gitlab.com/joubu/koha-plugin-jump % cd koha-plugin-jump % zip -r koha-plugin-jump.kpz Koha Then install the kpz using the Koha plugin tool page. Also if you want pretty data to be generated you should use patches from bug 24310 (do not forget to install libtext-lorem-perl) If you are lazy to try it, you can have a look at this screencast: https://drive.google.com/open?id=1G01pr8IZH2m5W7_bxEibfi3MyzXAZF-5 (I have no idea why this stuff rendered so dark!) Enjoy end 2019 ;) Cheers, Jonathan https://gitlab.com/joubu/koha-plugin-jump https://gitlab.com/joubu/koha-plugin-jump/blob/master/README.md https://gitlab.com/joubu/koha-plugin-jump/blob/master/TODO

3 2

Koha Community Newsletter: December 2019
by kohanews 28 Dec '19

28 Dec '19

The Koha Community Newsletter for December 2019 is here: https://koha-community.org/koha-community-newsletter-december-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 Editor, Koha Community Newsletter

1 0

Koha 19.11.01 release
by Joy Nelson 24 Dec '19

24 Dec '19

The Koha community is proud to announce the release of Koha 19.11.01. This is a maintenance release containing 30 bugfixes The full release notes are available at https://koha-community.org/koha-19-11-01-release/ Debian packages will be updated within a few days That just leaves me to wish everyone Happy Holidays and express my thanks to everyone involved in this release. Particularly Nick Clemens, Lucas Gass, and Martin Renvoize for stepping me through the various hoops in getting this done. Joy Nelson -- Joy Nelson President, Koha Division ByWater Solutions <http://bywatersolutions.com> Support and Consulting for Open Source Software Phone/Fax (888)900-8944 What is Koha? <http://bywatersolutions.com/what-is-koha/>

4 3

Upgrade db to v19.11
by Paul A 17 Dec '19

17 Dec '19

I have the possibility over the next month or two of examining the upgrading Koha from 3.8.24 to 19.11 (latest stable release.) We have the hardware available, but have a couple of questions before I plan the workflow: a) database migration? I have looked at the schemas, and am worried that there are substantial changes. Our production servers contain some 250,000 items. We are not a lending library, so have no concerns with that side of library management -- only with pure cataloguing, for which we use over 100 custom reports, 900 "sources", ten customized biblio frameworks, etc -- how best to proceed? Is there a script (or multiple scripts) that would do it? b) server software? does "pure" Debian (which we have never used in production) have advantages over Ubuntu LTS (with which we are extremely comfortable)? c) We normally build from tarballs, but have received some criticism in the past. The reason is that once we have a server locked into production, we never (major security excepted) touch it; our 3.8.24 has now been running for 1,467 days without rebooting, and "if it ain't broken, leave it alone." Is the final installation package/tarball identical using the different methods? Thanks in advance for your advice. Season's greetings, Paul

4 3