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

Possible issues with 942$0 (totalissues) values?
by Theodoros Theodoropoulos 10 Oct '18

10 Oct '18

Hello everyone, There might be some issues in Koha involving 942$0, update_totalissues script and sorting by popularity. If I understand correctly, the update_totalissues script updates biblioitems.totalissues and updates the 942$0 too (see C4::UpdateTotalIssues). Also I believe that sorting by popularity is based on the indexed 942$0 values and not on the values in biblioitems.totalissues So, I think there are a couple of cases where this number can be inaccurate leading to a false sorting-by-polularity. 1. If the value is prefilled by the script, regardless of the 942$0 subfield being hidden in the Marc framework, a librarian with cataloguing permissions may go into the marc editor and change it directly. That number will be indexed by zebra and used in sorting by popularity. The only way of 942$0 being 'fixed' by the system is after a checkout of an item of this biblio is made. Then, the update_totalissues script will requery the DB tables to count the total number of checkouts and update 942$0 2. Likewise, when a librarian with cataloguing permissions duplicates a biblio record with a value in 942$0, this value will be copied to the cloned record as well. As you imagine, this is wrong because it's a NEW biblio record (and probably has no items yet, so no checkouts), so 942$0 should be initially 0. Again this 'cloned' value will be taken by the system as the 'official' number of total checkouts for this biblio (at least for sorting purposes) and will remain there until a checkout of an item of this biblio is made (so the script will recalculate the proper number and hopefully update it) The 1st cannot be solved by simply 'hiding' 942$0 in the Default framework. The script will have the value filled, so the subfield will be visible and editable. Is there a way to hide (or make readonly) certain fields from the cataloguer (even in the advanced editor?). Maybe a new syspref could be incorporated to restrict viewing/editing of certain MARC field/subfields? The 2nd issue seems equally (if not more) important because it's more likely to happen. I vaguely remember a discussion from the past where it was mentioned that by selecting 'flagged' in "Edit Framework Subfields > Advanced constraint values > Visibility", the value of that subfield would not be cloned in a new biblio, but I couldn't reproduce it in my tests. Maybe we could use this for differentiating the case when all checkboxes are unchecked and where flagged is selected? (I believe that right now the behavior of these two is identical). I'm only thinking aloud, so any ideas/comments would be more than welcome! Kind regards, Theodoros Theodoropoulos

1 0

Translation too long
by BOUIS Sonia 09 Oct '18

09 Oct '18

Hello, I've noticed that there's a translation too long in french in catalogue/moredetail.pl so it's unreadable. Cf image. Is there's something to change in the code to allow a longer but clearer translation : Accession date -> Date d'entrée dans les collections Or should we just change the translation for a shorter one ? Thanks in advance [cid:image001.png@01D45D60.7B76E4E0] Sonia BOUIS ------------------------------------------------------ Responsable du Service des applications documentaires Bibliothèques universitaires Université Jean Moulin Lyon 3 ADRESSE GÉOGRAPHIQUE > Manufacture des Tabacs | 6 cours Albert Thomas | LYON 8e ADRESSE POSTALE > Bibliothèque de la Manufacture | 1C avenue des Frères Lumière | CS 78242 - 69372 LYON CEDEX 08 Ligne directe : 33 (0)4 78 78 79 03 http://bu.univ-lyon3.fr<http://bu.univ-lyon3.fr/>| Suivez-nous > Facebook<https://www.facebook.com/bulyon3/> | Twitter<https://twitter.com/bulyon3>| Instagram<https://www.instagram.com/bu.lyon3/?hl=fr> --------------------------------------------------- L'Université Jean Moulin est membre de l'Université de Lyon

4 4

koha-testing-docker - a couple of questions
by David Nind 08 Oct '18

08 Oct '18

I've been getting to grips with using koha-testing-docker ( https://gitlab.com/koha-community/koha-testing-docker) since KohaCon 18. Thanks Kyle and Tomás for having a session on it at the HackFest! A couple of questions - apologies if the answers to these are obvious, I've not really used docker until now... I'm using docker on a Ubuntu 18.04 desktop. env/defaults.env and .env ==================== Is the copy you make of defaults.env only required because docker requires it (as instructed under Setup in the README.md file)? Anything I've updated in .env seems to be ignored in favour of what is in the env/defaults.env file, for example your Git user name and email. However, if you don't have the .env file you get this error when running docker-compose -p koha up : > WARNING: The KOHA_INTRANET_PREFIX variable is not set. Defaulting to a blank string. > WARNING: The KOHA_INSTANCE variable is not set. Defaulting to a blank string. > WARNING: The KOHA_INTRANET_SUFFIX variable is not set. Defaulting to a blank string. > WARNING: The KOHA_DOMAIN variable is not set. Defaulting to a blank string. > WARNING: The KOHA_OPAC_PREFIX variable is not set. Defaulting to a blank string. > WARNING: The KOHA_OPAC_SUFFIX variable is not set. Defaulting to a blank string. > WARNING: The RUN_TESTS_AND_EXIT variable is not set. Defaulting to a blank string. > WARNING: The COVERAGE variable is not set. Defaulting to a blank string. > ERROR: The Compose file './docker-compose.yml' is invalid because: > services.koha.networks.kohanet contains non-unique items, please remove duplicates from [u'', u''] For the moment I just make changes in env/defaults.env and copy this to .env UNIMARC support ============== Does koha-testing-docker support UNIMARC at this stage? Adding either UNIMARC or unimarc to the env/defaults.env file didn't seem to make any difference. Normally I would use MARC21, but I was trying to test a UNIMARC patch - the UNIMARC specific script said it only works on UNIMARC (surprisingly enough!). If I try reset_all_unimarc in the container it hangs at the last line: > Inserting /kohadevbox/koha/installer/data/mysql/en/marcflavour/unimarc/mandatory/authorities_normal_unimarc.sql... > Inserting /kohadevbox/koha/installer/data/mysql/en/marcflavour/unimarc/mandatory/unimarc_framework_DEFAULT.sql... > Setting the MARC flavour on the sysprefs... > Setting Koha version to 18.0600035... > Running [sudo koha-shell kohadev -p -c 'PERL5LIB=/kohadevbox/koha:/kohadevbox/qa-test-tools perl /kohadevbox/misc4dev/create_superlibrarian.pl --userid koha --password koha ']... > Running [sudo koha-shell kohadev -c 'PERL5LIB=/kohadevbox/koha:/kohadevbox/qa-test-tools perl /kohadevbox/misc4dev/insert_data.pl --marcflavour UNIMARC']... > There is no records data for UNIMARC yet at /kohadevbox/misc4dev/ insert_data.pl line 50. Also, is there an easy way to tell if Koha is using UNIMARC? I assume you can tell by looking at the default cataloguing framework (if you know what you are looking for, which I don't). Rebuilding search indexes ===================== After docker is running you don't get any search reults when searching the catalogue. Is having to rebuild the search index manually once docker has started the normal behaviour? Is it possible to have the indexes created as part of docker starting up? Or is there a reason why this isn't done? (Depending on whether you want to use Zebra or Elastic.) Getting my head around docker ========================= I found this quick guide useful to get the concepts of docker https://vsupalov.com/6-docker-basics/ As well, the docker documentation is helpful after that https://docs.docker.com/get-started/ Are there any other useful guides or tutorials that you would recommend to people new to docker? Thanks for everyone's work that has made koha-testing-docker possible! David Nind | david.nind(a)gmail.com PO Box 12367, Thorndon, Wellington, New Zealand 6144 m. +64 21 0537 847

2 2

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