Hi all,
Any thoughts here about how we should handle updating fields in MARC which
have no specific corresponding database field.
I am thinking about e.g. a persistent identifier in MARC21 field 024 or an
OCLC number in field 035.
Could we add REST API entries for such changes as well? They will o
We could have a route to overlay the MARC representation of a biblio (if
acceptable). We could use
PATCH /biblios/:biblio_id
Content-Type: application/marc-in-json
{ ...
El vie., 22 ene. 2021 6:20, Marcel de Rooy escribió:
> Hi all,
>
> Any thoughts here about how we should handle updating f
Thanks. Overlaying the whole marc record is interesting too. Overwriting
specific fields might offer some more fine grained control however too.
Something like:
PUT /api/v1/biblios/123456/marc ?
POST, PUT /api/v1/biblios/123456/marc/field/789 ?
Marcel
X
X!
El vie., 22 ene. 2021 10:09, Marcel de Rooy
escribió:
> Thanks. Overlaying the whole marc record is interesting too. Overwriting
> specific fields might offer some more fine grained control however too.
>
> Something like:
>
> PUT /api/v1/biblios/123456/marc
>
The fact you're passing MARC is jus
Hello everyone 🤗
The Koha community is proud to announce the release of Koha 20.11.02.
It is a maintenance release including 10 enhancements, 50 bugfixes.
Contains 5 critical bugfixes especially :
Bug 27509 - cn_sort value is lost when editing an item without changing
cn_source or itemcallnumb
Hi folks!
The Koha community is proud to announce the release of Koha 20.05.08!
Koha 20.05.08 is a bugfix/maintenance release.
It includes 4 enhancements, 35 bugfixes.
The full release notes can be found here:
https://koha-community.org/koha-20-05-08-released/
--
Andrew Fuerste-Henry
Educator
