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

Koha 17.05.14 release
by Fridolin SOMERS 05 Oct '18

05 Oct '18

The Koha community is proud to announce the release of Koha 17.05.14. This is a maintenance release. Packages will be available in a few days. The full release notes are available at https://koha-community.org/koha-17-05-14-release/ Important /!\ This should be the last 17.05.x release. Please consider upgrading to 17.11.x, it will be maintained for at least the next 6 months. I have proposed to continue managing 17.11.x during next release cycle. Regards, -- Fridolin SOMERS <fridolin.somers(a)biblibre.com> BibLibre, France - software and system maintainer

1 0

The libre Android application "Web Opac" is planning to integrate Koha
by Victor Grousset/tuxayo 04 Oct '18

04 Oct '18

Hi :) https://opac.app/en/ https://github.com/opacapp/opacclient https://f-droid.org/packages/de.geeksfactory.opacclient/ https://github.com/opacapp/opacclient/issues/101#issuecomment-425421264 > Status update: As Koha is becoming more popular in Germany (through LMSCloud, who offer Koha hosting), we are now starting to work on implementing full support for Koha OPACs, including account features. As the new Koha API will probably still use SRU for catalogue search, it will only work for Koha libraries that have SRU enabled. Is their analysis correct? (about SRU stuff) And could there be advice that would help them? -- Victor Grousset, dev support/maintenance BibLibre, Services en logiciels libres pour les bibliothèques BibLibre, Libre/Open Source software and services for libraries

2 1

Can't create new Jessie Kohadevbox
by David Cook 04 Oct '18

04 Oct '18

Hi all, I created a Jessie Kohadevbox at the Kohacon18 hackfest and it was all good, but when I've tried making one back at work, it's been failing. Josef pointed me to this issue opened by Owen: https://gitlab.com/koha-community/kohadevbox/issues/273, and I think that I've worked out what's going on. It looks like there was a recent update to the python-reportbug package and it triggers the download of python-openssl version 0.14-1, which seems to create fatal errors in pip and Ansible. The workaround is to remove python-openssl and then re-provision the kohadevbox. Obviously, that's not a great solution for a kohadevbox which should work "out of the box", but it's a solution for now. I haven't tried Stretch with the kohadevbox, but I have a feeling that it might be OK. Hopefully this info is helpful! David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595

2 4

KohaDevBox | Debian Stretch
by Tomas Cohen Arazi 03 Oct '18

03 Oct '18

We've shifted the default OS version in KohaDevBox to Debian Stretch. We will try to keep following stable. You can still run Debian Jessie by explicitly asking for it: $ vagrant up jessie $ vagrant ssh jessie and so on. If you already have a Jessie-based box running and update the kohadevbox code, please remember to add the trailing 'jessie' word to the commands you usually ask vagrant to run. Thanks! -- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F

1 0

Implementation of Koha in the Library of the University of Cádiz
by Aurora Marquez Pérez 03 Oct '18

03 Oct '18

Dear colleagues, after the first year in production, from the Library of the University of Cádiz we decided to share our experience on migration from Millennium ILS to Koha by publishing a paper in the Spanish professional journal El profesional de la Información. Implementing Koha at the University of Cádiz Libray. Fernández-Alfaro, Leonor; Márquez-Pérez, Aurora; Chamorro-Rodríguez, Ricardo (2018). "Implementation of Koha in the Library of the University of Cádiz". The professional of the information, v. 27, n. 4, pp. 928-936. https://doi.org/10.3145/epi.2018.jul.21 As our situation is similar to that of many other libraries that are currently in analogous processes, we encourage you to read them as we describe the different phases of the Project: the choice of software, migration, parameterization and a final consideration as a conclusion. We hope our experience will be useful to you and, of course, we are at your disposal for any question you want to ask us. Kind regards. UCA Aurora Márquez Pérez Coordinadora Sección Proceso Técnico y Gestión Tecnológica Área de Biblioteca y Archivo Universidad de Cádiz C/ Doctor Marañón, 3 Edificio Andrés Segovia 11002 - Cádiz Tel 956 015273 aurora.marquez(a)uca.es

1 0

QA script is now able to catch missing filters!
by Jonathan Druart 02 Oct '18

02 Oct '18

Hi devs, A new check to catch missing filters is not in the QA script. Please update, and report bugs! ;) Cheers, Jonathan https://gitlab.com/koha-community/qa-test-tools/issues/3

2 2

Re: [Koha-devel] [Koha] Inventory lists incorrectly sorted
by David Cook 02 Oct '18

02 Oct '18

I think Koha should be taking care of normalizing the call number into something like “AL_333_910000000000000_WHY_1986” (admittedly a Dewey-ish example) for sorting purposes. If Koha isn’t sorting the call number correctly, I think it’s worth raising an issue. It seems to me that the on-screen inventory list and the CSV/spreadsheet export inventory list should be identical in how they’re sorted. That way you can print off a shelf list, do your inventory, and then scroll through your screen marking items as seen in the order that they were seen for real. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 From: Sebastian Hierl [mailto:s.hierl@aarome.org] Sent: Friday, 28 September 2018 7:11 PM To: dcook(a)prosentient.com.au Cc: Koha Devel <koha-devel(a)lists.koha-community.org>; koha <koha(a)lists.katipo.co.nz> Subject: Re: [Koha] Inventory lists incorrectly sorted Thank you for raising this issue, David. We sort the reports we generate from Koha in Excel with the following formula by Lee Ann Nolan and Jameson Conley: https://scholarsphere.psu.edu/concern/generic_works/qv33rw719 The formula is a big help, but it doesn't work for call numbers starting three letters, such as in the K class <https://www.loc.gov/aba/publications/FreeLCC/freelcc.html> , where there are numerous call numbers starting with KJA, KKH, KZA, etc. I would love to hear whether anyone has devised a better script or formula to sort LC call numbers in either LibreOffice / OpenOffice or Excel. Thank you, Sebastian -- Sebastian Hierl, Ph.D. Drue Heinz Librarian, Arthur & Janet C. Ross Library American Academy in Rome Via Angelo Masina 5 00153 Rome Italy T: +39 06 5846 417 F: +39 06 5810 788 On Fri, Sep 28, 2018 at 8:33 AM David Cook <dcook(a)prosentient.com.au <mailto:dcook@prosentient.com.au> > wrote: Hi all, Has anyone had a problem where the lists generated by the inventory tool don't seem to be sorted correctly? I received reports of this and during my investigation I found https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19021 but that didn't seem to solve the root problem, which actually appears to be with the item data stored in the database - rather than Koha code per se. I've opened https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21447 to look into this. I've solved it in my case using touch_all_items.pl <http://touch_all_items.pl> , but it might not be feasible for everyone to run this. Keen to hear ideas about how people think we should resolve this issue for all people. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 _______________________________________________ Koha mailing list http://koha-community.org Koha(a)lists.katipo.co.nz <mailto:Koha@lists.katipo.co.nz> https://lists.katipo.co.nz/mailman/listinfo/koha

1 0

Problem of OpacHiddenItems
by DevinimKoha 01 Oct '18

01 Oct '18

Hello everyone, We faced a quite big problem in Opac search for a while and we were not able to find a workaround for that. When we use OpacHiddenItems system preference value for a specific items, let's say withdrawn items, in the Opac search result, related item become hidden and the numbering is being closed automatically. However if all items in the second page were also hidden then it says "0 results found". Is there anybody hit this problem and any workaround for that? We created the bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19688 and we think that the change in the bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10584 may be the result of this bug. Thanks. Devinim Koha team.

3 3

Koha Community Newsletter: September 2018
by kohanews 29 Sep '18

29 Sep '18

The Koha Community Newsletter for September 2018 is here: https://koha-community.org/koha-community-newsletter-september-2018/ 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

git trailers: should we use more of them ?
by Julian Maurice 28 Sep '18

28 Sep '18

Hi all, AFAIK in our commit messages we are using two different trailers: - Signed-off-by tells who tested/reviewed the patch - Sponsored-by tells who sponsored the patch I recently stumbled upon the contribution guidelines for git [1] which suggests to use Reported-by, Acked-by, Reviewed-by, Tested-by and others (Thanks-to, Mentored-by, ...) I think it can be good to credit people who reported bugs or helped in a way other than signing off or writing patches (testers that find bug are helpful but they're not always the signoffers). Also, the distinction between Tested-By and Reviewed-By could help in situations where we don't know for sure if a signoff is only a test or a full QA review. This guide (and the git-commit manpage [2]) also states that we're not really using the Signed-off-by trailer as intended. In short, a "signoff" means (for git developers) that the patch author agrees to https://developercertificate.org/ I'd like to know what you think about this. Should we use Reported-By ? Should we replace Signed-off-by by Tested-By (for testers) and Reviewed-By (for QA) ? Should we use Signed-off-by as suggested in the git-commit manpage ? Do you think it is not worth the effort or that a change would be bad in some way ? Thanks [1] https://github.com/git/git/blob/master/Documentation/SubmittingPatches [2] https://git-scm.com/docs/git-commit#git-commit--s -- Julian Maurice <julian.maurice(a)biblibre.com> BibLibre

6 7