Ho Thomas,
thanks for your answer.
In the meantime, I'm waiting for a response from the Plesk research and
development team: they are verifying that "javascript-commom" package is
indeed still in conflict with Plesk itself (it was like this in the past,
but if it was no longer the case, the Plesk
Hi Jonathan
Thanks for your message! You wrote:
> Line 157 on this version is about authorised values. My guess is that
> you have a value in marc_subfield_structure.authorised_value that does
> not have an entry in the authorised_values table (column category).
>
> It can be considered as a bug
Hi all,
I just wanted to bring your attention to Bug 34587 which is another
enhancement to the ERM module to introduce Data Providers, COUNTER and
SUSHI to Koha.
There is no formal test plan to this (as it is a big feature) but you can
watch my video at KohaCon 23 this year which shows how all of t
Hi Jonathan
In file "search_for_data_inconsistencies.pl" I found the line
push @decoding_errors, $@ if $@;
which I changed to
push @decoding_errors, sprintf("ID=%s - %s", $biblio->biblionumber, $@);
After running "search_for_data_inconsistencies.pl" again, I found three
ID numbers saying:
hi Alessandro
El lun, 2 oct 2023 10:18, Alessandro Tedesco mailto:alessandro.tedesco...@gmail.com>> escribió:
Hi Mason,
thanks for the reply.
If I may, I would ask a further question.
If I install Koha 21.11 (which requires libmojolicious-perl 8.x) and then
upgrade to Koh
Safe in what sense?
Koha won't work correctly with those records if there is no entry in
biblio_metadata for them, but maybe you should try and recover them, or at
least understand how it happened.
Le mar. 3 oct. 2023 à 17:13, Michael Kuhn a écrit :
> Hi Jonathan
>
> In file "search_for_data_in
6 matches
Mail list logo