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

API use in intranet and OPAC
by Agustin Moyano 15 Oct '19

15 Oct '19

Hello everyone, I'll introduce myself for those of you who didn't "git blame" me... I'm the one who introduced that huge, nasty, blocking bug, that didn't ley you place a simple hold on intranet. I'm glad to announce that patch is on the way, and passed QA. This was one of the first steps (if not the first) of using the API in intranet. A really clumpsy step, I give you that, but as they saying says.. "That's one small step for [a] man, one giant leap for the API", but in my case, if I've been Neil Armstrong, I've probably tripped as soon as I got out of the module, get my helmet all scratched and filled with moon dust, and instead of a nice clean footprint, there would have been a fuzzy figure resembling a space suit trying to get up. Marcel de Rooy, the generous soul who passedQA the solution patch, complained (and he was absolutely right) about a couple of things: 1. That there was no comunication about this in dev channel before implementing. It's too late for discusing before implementing, but I would really like to know your opinion post implementation. 2. OPAC and Intranet now use diferent methods to place holds.. one uses the API, the other uses a POST to a .pl file. I think it best to move OPAC to use the API, but this time I'm going to hear you first. Regards

10 15

Duplicated holds notices
by Nick Clemens 14 Oct '19

14 Oct '19

Hi All, We have been getting several reports of duplicated holds notices on a few systems. We cannot find any issues in the code that would duplciate this, there are not duplicated transports or anything in the data we can find. We have noticed that some of the modals have a submit button, and then js to submit the form, however, Kyle attempted to add 'preventDoubleFormSubmit()' to the page and that has not helped $(document).ready(function() { if (window.location.href.indexOf("circ/ returns.pl") > -1) { $('form').preventDoubleFormSubmit(); } }); Has anyone else experienced this? -Nick -- Nick Clemens ByWater Solutions bywatersolutions.com Phone: (888) 900-8944 Pronouns: (he/him/his) Timezone: Eastern

2 3

Removing data from hea.koha-community.org
by dcook＠prosentient.com.au 14 Oct '19

14 Oct '19

Hi all, Do we have any process for removing data from hea.koha-community.org? For instance, say that a library permanently closes, or just no longer wants to be listed? David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595

2 1

Turn on DEBUG for Koha Plack instance
by dcook＠prosentient.com.au 08 Oct '19

08 Oct '19

Hi all, How do you (temporarily) turn on DEBUG mode for Koha Plack? I looked inside and out and nothing I tried seemed to work? David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595

1 0

Mini roadmap for the API
by Tomas Cohen Arazi 08 Oct '19

08 Oct '19

Hi, with the HAL introduction in mind I plan to (at least) provide a sample implementation of the following: - Add a 'to_api' method to Koha::Object and Koha::Objects that can be overloaded if needed (trivial, WIP 23770) - Pick a sample endpoint (probably /cities) and make sure the implementation keeps the current behaviour (trivial, besides the boring tests) - Move the existing controllers into using this (trivial) - Implement in some sample class, to be determined, ->to_api_hal. And make the endpoint that uses it, Accept: application/hal+json and return this new data structure. So if JSON is requested, the current behaviour is kept. Otherwise, the HAL representation will be returned. Things to think about and which we will be able to play with: - How to determine the depth of the embedding? (HAL has that ability) - Should we specify which FK to follow and embed on the query? how would that query look like? Thanks for your time :-D -- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F

2 1

Koha, centOS, Apache, starman => random timeout !
by Paul Poulain 07 Oct '19

07 Oct '19

Hello, We have a library running Koha (17.11) on his own centOS (virtual) server, with Apache as webserver. Everything is working smoothly, except that, from time to time (about once a day), it's not working anymore, any page returns: "Proxy error, Error reading from remote server" The logs shows nothing except a strange: [Wed Jul 10 17:17:35.732798 2019] [proxy_http:error] [pid 322] (70007)The timeout specified has expired: [client 1.2.3.4:32988] AH01102: error reading status line from remote server localhost:5000, referer: https://xxx.xxx.xxx.fr/cgi-bin/koha/catalogue/detail.pl?biblionumber=78504&… [Wed Jul 10 17:17:35.732861 2019] [proxy:error] [pid 322] [client 1.2.3.4:32988] AH00898: Error reading from remote server returned by /cgi-bin/koha/catalogue/search.pl, referer: https://xxx.xxx.xxx.fr/cgi-bin/koha/catalogue/detail.pl?biblionumber=78504&… <https://admin.panam.culture.fr/cgi-bin/koha/catalogue/detail.pl?biblionumbe…> What is stranger : after a few minutes, without any action on the server, everything is back, and working well. did anyone face such a problem ? any idea welcomed ! -- 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 1

Hackfest meeting about Mana-kb
by Paul Poulain 04 Oct '19

04 Oct '19

Hello all, We had a quite productive meeting regarding mana-kb during the hackfest. We had many ideas regarding improvements / new features that could be added, I've created a bugzilla entry for each idea. Below is a summary of our work reminder : and "object" is something that is shared through mana. For now, subscription patterns and reports can be shared. * there's a web interface (ui.mana-kb) to look at data, and delete old/outdated. The idea is to curate data regularly. Anyone can apply to become a curator of the data in mana-kb. New features idea : o add a button "apply as curator" https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23738 o prepare some SQL queries that could show librarians contributing a lot, and proposing them to join the list of curators https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23739 o Let curators flag a content (3 values : non-flagged / hide this object, to be discussed for deletion / 'star' this object, it has a high quality/value) https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23740 * Sharing reports guidelines https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23741 o When you share a report, Koha could check if there's a runtime value to set (<<xxxx|yyyy>>). If there's none, add a confirmation checkbox, most useful reports need a runtime parameter. o Add a hint : "do not share a report with hardcoded value related to your own data" that is displayed when the librarian want to share a report * Languages checks are made on the full language code (fr_FR). We need only the first 2. Thus, reports with language fr_FR are displayed also for our canadian-Quebec friends (same thing for en_EN, en_US, en_NZ, of course) https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23742 * In the admin/share_content.pl page => show if a token has not been validated yet https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23743 * In the result lists (for object (reports, ...) searching, add a column with the language of submission, that can be filtered/sorted https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23744 * in ui.mana-kb : https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23745 o hide the token column, a curator does not need to know the token of a librarian o add a feature 'resend token' => resend the validation email to the librarian * In Koha : check that the associated email is an email, to avoid unvalidable tokens https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23746 * replace a local Koha object by a mana-kb one: currently, it's not possible to modify a local object with one coming from Mana-kb. Add this feature, 2 sub-features: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23747 o if the local object comes from Mana, have a message "hey, the mana object has been updated, clic here to update your local one" o if the local object is 'home-made', add a button "update from mana-kb" that let the librarian search in mana, and update his local data. * "golden mana-kb contributor": we expect to have some librarians contributing very efficiently and frequently. Those librarians should be able to update existing mana objects. The golden mana-kb contributor is given by curators, coopt/consensus. The golden contributor status can be given for reports and for subscriptions, separately. -- 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

A case against some uses of C4::Context->userenv
by Tomas Cohen Arazi 30 Sep '19

30 Sep '19

Hi all, I've been looking at the 'Claims returned' work (awesome!) [1] and I've noticed a pattern we should, in my opinion, start avoiding and reverting. It is quite common to find uses of C4::Context->userenv in the Koha::* namespace, either as a plain requirement (if the borrowernumber is not set we bail out) or just as a fallback. I think it is wrong to expect such environment status in our logic. It complicates things in various ways. [2] It is done this way because: - We come from the CGI era, in which it made perfect sense - Cookie auth is well established on the UI - When migrating from C4:* into Koha:* it is easier to just keep the current behavior and then evolve. I propose we leave them out, and add as a parameter whatever we are expecting to find in the userenv hashref. That way we could use this new libs in the API (which is not cookie-only). Looking forward to hear your opinions [1] https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14697 [2] CLI scripts are using Koha::* libraries, and we then need to 'emulate' that userenv or even add code to detect we don't have a userenv. -- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F

5 4

kohastructure.sql : columns with COLLATE
by Fridolin SOMERS 30 Sep '19

30 Sep '19

Hi I'm working on DB structure compare. I note that in installer/data/mysql/kohastructure.sql, a few columns define CHARACTER SET and/or COLLATE, with same values as table. Is this usefull or should we remove it ? $ grep 'COLLATE' installer/data/mysql/kohastructure.sql | grep -v ENGIN | grep 'utf8mb4_unicode_ci' `category_name` varchar(32) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `font` char(10) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT 'TR', `text_justify` char(1) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT 'L', `auto_renew_error` varchar(32) COLLATE utf8mb4_unicode_ci DEFAULT NULL, -- automatic renewal error `auto_renew_error` varchar(32) COLLATE utf8mb4_unicode_ci DEFAULT NULL, -- automatic renewal error `suppliers_report` MEDIUMTEXT COLLATE utf8mb4_unicode_ci, -- reports received from suppliers entity varchar(16) COLLATE utf8mb4_unicode_ci NOT NULL, code varchar(64) COLLATE utf8mb4_unicode_ci NOT NULL, lang varchar(25) COLLATE utf8mb4_unicode_ci NOT NULL, -- could be a foreign key translation MEDIUMTEXT COLLATE utf8mb4_unicode_ci, `branchcode` varchar(10) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci DEFAULT NULL, -- Fridolin SOMERS <fridolin.somers(a)biblibre.com> BibLibre, France - software and system maintainer

5 4

Koha Newsletter: September 2019
by Koha Newsletter 29 Sep '19

29 Sep '19

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