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

removing some projects from git.koha-community.org
by Paul Poulain 14 Nov '18

14 Nov '18

Hello, on git.k-c.org, there are some project that have not been updated for years, and I'm wondering whether we should/could hide or delete them: This question is for the following repos: * koha-translations.git Translations files (.po) for... Translation Manager 3 years ago * mm/jcamins.git MM repo for authorities Jared Camins-Esakov 4 years ago * mm/chrisc.git MM repo for testing Chris Cormack 4 years ago * wip/koha-equinox.git Equinox work in progress Galen Charlton 5 years ago * koha-small.git main Koha release repository Koha Project 6 years ago * wip/koha-catalyst.git Catalyst work in progress Chris Cormack 6 years ago * wip/koha-chris_n.git Personal work in progress Chris Nighswonger 7 years ago * wip/koha-biblibre.git BibLibre work in progress Henri-Damien Laurent 7 years ago * wip/koha-fbc.git Foundations Bible College... Chris Nighswonger 7 years ago * wip/koha-ptfs.git PTFS work in progress J. David Bavousett 8 years ago the koha-biblibre.git, for sure, BibLibre don't use it at all, it can be discarded. I haven't listed: * website.git Koha website repository Koha Project 5 years ago * koha-archive.git Old Koha topic branches Koha Project 5 years ago but maybe they can be included as well. good idea or not ? -- Paul Poulain, Associé-gérant / co-owner BibLibre, Services en logiciels libres pour les bibliothèques BibLibre, Open Source software and services for libraries

3 2

Filtering inventory results by cn_sort vs. callnumber
by Nick Clemens 14 Nov '18

14 Nov '18

Hello All! I put together a bug a while back for switching the sorting on inventory results filter from using 'callnumber' to the hidden/constructed column 'cn_sort' i.e. When inventorying a section by callnumber you would enter the range GT90 to GT100, Koha would then interpret this to (roughly) GT090 and GT100 as we do when constructing the cn_sort column. 'cn_sort' is the column we use to pad callnumbers with '0' and spaces to ensure that a callnumber of GT90 is sorted before GT100 (if sorted as normal strings 1 comes before 9) During review if the bug there was concern that some callnumber schemes may not work under this change, or some libraries might not have the cn_sort columns correctly filled and that we should add a system preference to control which column was used. On bug 21629 ( https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21629) we made sorting lists by callnumber use cn_sort by default. I am just writing to see if any libraries out there have concerns about the change, or if we think that always using cn_sort to filter the results would work. We want to be consistent throughtout the code (ideally) Let me know what thoughts you have and if you think we can simply assume cn_sort is the definitive column for sorting and defining ranges. -Nick -- Nick Clemens Sonic Screwdriver (Development Support) ByWater Solutions IRC: kidclamp

1 0

Replacing koha-plack, koha-start-zebra, etc with systemd services?
by David Cook 14 Nov '18

14 Nov '18

Hi all, I'm about to start working on a systemd service for running Plack (for a non-package Koha install), and I was wondering if anyone else has thought about or is using systemd services for Plack, Zebra, etc. Mason did a great job with a systemd service https://github.com/KohaAloha/koha-mysql-init/blob/master/koha-mysql-init.ser vice for getting around the autoincrement issue (fixed in MySQL 8.0 https://dev.mysql.com/doc/refman/8.0/en/innodb-auto-increment-handling.html and MariaDB 10.2.4 https://mariadb.com/kb/en/library/auto_increment/) Anyway, once I've got something working, I'm happy to share it. Curious if anyone has any systemd unit files they'd like to share. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595

3 4

Call for News: November 2018 Newsletter
by kohanews 14 Nov '18

14 Nov '18

I'm collecting news for the November 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

Freeze and release notes
by Nick Clemens 14 Nov '18

14 Nov '18

Hi All, I went through the queue today and pushed what I could, I think we got a few nice things in today :-) There are some outstanding bugs still, please keep up the great work and help us sort these before release, especially majors/criticals and of course, blockers The release notes are generated rolling now, so first, very rough, draft is already generated: https://gitlab.com/koha-community/koha-release-notes/blob/master/release_no… There are two outstanding enhancements I am considering, 18983 and 20244 for ES - they shouldn't affect Zebra code so I think they are safe and will help uskeep ES momentum Thanks for all your hard work, and your patience. Let me know your feedback and where I can help. -Nick -- Nick Clemens Sonic Screwdriver (Development Support) ByWater Solutions IRC: kidclamp

2 1

Candidate for 18.05 Maintainer
by Nick Clemens 13 Nov '18

13 Nov '18

Hello all! Last week during the Koha developers meeting we voted on roles for the 19.05 release. I will be continuing as the Release Manager, and we have many hands helping along the way ( https://wiki.koha-community.org/wiki/Roles_for_19.05) There is one role left unfilled: 18.05 Release Maintainer (old stable) The release maintainers are responsible for watching the bugs queue from the upcoming release and backporting bugs that affect the version they watch, helping to make sure version in use are kept as stable as possible. It is a good way to learn more about different areas of Koha, to practice your rebasing skills, and to get more involved in the community. There will be many people in the community around to help you out, and we are always looking for new faces to take on these roles. If you are interested please add your name to the wiki page above and we will be voting tomorrow to accept candidates if we have one in place. If you have any questions you can ask the list or message me here or in IRC. Thanks! -Nick -- Nick Clemens Sonic Screwdriver (Development Support) ByWater Solutions IRC: kidclamp

1 0

Freeze/Notes draft
by Nick Clemens 08 Nov '18

08 Nov '18

Hello all, I have hit a multitude of issues today with my VMs and testing and did not realize I was traveling tomorrow when I first set dates for release. I plan to extend the freeze through Monday so that things in the queue (and things I commented today) have some time to get fixed. I will test everything I can today to provide feedback and do the final push on Monday. Thank you for your patience. -Nick -- Nick Clemens Sonic Screwdriver (Development Support) ByWater Solutions IRC: kidclamp

2 2

Documentation for KohaTable() javascript function
by David Cook 01 Nov '18

01 Nov '18

Hi all, Does anyone know where there is any documentation for using the KohaTable() javascript function? I'm muddling through, but it would be great if there was something in at least https://wiki.koha-community.org/wiki/Coding_Guidelines. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595

2 2

Handling for items lost in transit
by Renvoize, Martin 01 Nov '18

01 Nov '18

Hi all, I'm seeking some thoughts regarding 'Bug 21732 - If an item is marked as lost, any outstanding transfers should be cancelled <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21732>'. Currently, there is no thought given to transfers when an item is marked as lost, an as such you may have lost items in the transfers queue. This bug aims to solve this by triggering a cancellation of the transfer at the point an item is marked as lost. We have a few questions: 1) Should this be treated as an enhancement or a bug (If it's an enhancement then we would enable/disable it's functionality based upon a system preference. If it's a bug (as I advocate), then it would be always enabled and no system preference would be added) 2) If the items is 'in transit' where should the items holding library be set to when it is marked as lost (the from or to library). 3) If we consider this a bug, should we add handling for cleaning up the transfers table at upgrade time for any lost items. Many thanks for your help, *Martin Renvoize* <https://www.ptfs-europe.com> Development Team Manager *Phone:* +44 (0) 1483 378728 *Mobile:* +44 (0) 7725 985 636 *Email:* martin.renvoize(a)ptfs-europe.com *Fax:* +44 (0) 800 756 6384 www.ptfs-europe.com Registered in the United Kingdom No. 06416372 VAT Reg No. 925 7211 30 The information contained in this email message may be privileged, confidential and protected from disclosure. If you are not the intended recipient, any dissemination, distribution or copying is strictly prohibited. If you think that you have received this email message in error, please email the sender at info(a)ptfs-europe.com

1 0

Koha Community Newsletter: October 2018
by kohanews 31 Oct '18

31 Oct '18

The Koha Community Newsletter for October 2018 is here: https://koha-community.org/koha-community-newsletter-september-2018/ Many thanks to the folks ( and poultry <http://avengingchicken.online/kohacon2018/> ) 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

2 2