Good idea. Anything to disband the "SmartUI"-antipattern is good for me. We should add a new endpoint following established nomenclature. eg. PUT /biblios/123/merge/456 (PUT as it is modifying existing records) regarding b) We should separate Mojololicious from Plack, because Plack prevents the use of websockets and more advanced Mojolicious features. It is not such a biggie to implement. We can control two processes from the same koha-plack -script, so the CLI management API doesnt need to change either. On 6.10.2023 13.00, koha-devel-request@lists.koha-community.org wrote:
Message: 1 Date: Fri, 6 Oct 2023 10:01:18 +0200 From: Zeno Tajoli<ztajoli@gmail.com> To: koha-devel<koha-devel@lists.koha-community.org> Subject: [Koha-devel] REST API and new defaults Message-ID: <CACwhcG0R2BUPM+X0NSkiA4d7em2vzgyb0yuWrR-gGpx=rPOEdw@mail.gmail.com> Content-Type: text/plain; charset="UTF-8"
Hi to all, thinking about BZ 33036, the basic idea is to change a part of ../cataloguing/merge.pl to create a 'merge' verb inside Koha/REST/V1/Biblios.pm then use this new verb in a new version of ./cataloguing/merge.pl
But if we use REST inside standard scripts, I think we need to change those defaults: a)RESTBasicAuth: from 'Not enabled' to 'Enabled' b)Plack as mandatory
As I see also ERM needs those defaults
So is it a direction to take?
In .. ../cataloguing/merge.pl I insert a check on the environment.
Cheers Zeno Tajoli