Hi to all,
in fact POST is the only not idempotent method, so:
POST /biblios/123/merge/456
options a json with inside a full MARCXML, the result of the merge, not rules
The user does the merge on FE, as is done today.
If there isn't a full MARCXML the record with the id 456 is deleted now,
and the
Yes this is important, and how the merging should be actually done is
something the GUI needs to deal with.
When the PUT/POST -request is done, we already need to know how the
merger is performed.
When you POST to /biblios/123/merges, you would semantically be creating
a new instance of a bi
El vie, 6 oct 2023 a las 11:03, Olli-Antti Hypernova (<
olli-antti.kivila...@hypernova.fi>) escribió:
> 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
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 prevent
