https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15399 --- Comment #7 from Barton Chittenden <barton@bywatersolutions.com> --- (In reply to Fridolin SOMERS from comment #6)
Yep I noticed this bug.
There seem to by a limit of YAZ. See yaz-client man, option -k. But I did not find how to use it in ZOOM perl lib.
In fact many bibs still use iso2709 for export/import. So its best to have records with size < 100 Ko.
Using GRS-1 is fully deprecated in Koha, which is the last place that I think that the 100 Kb limit touches zebra. Koha's item data, stored in 952, can *easily* go over 100 Kb, so this is not a realistic limit, and libraries with long running serials cataloged as items can go over 1MB. Looking at http://www.indexdata.com/yaz/doc/zoom.html, it seems that the default values of maximumRecordSize and preferredMessageSize are both set to 1MB, and void ZOOM_connection_option_setl(ZOOM_connection c, const char *key, const char *val, int len); and const char *ZOOM_connection_option_getl(ZOOM_connection c, const char *key, int *lenp); take length options. connection_option_setl() is called at line 470 of /usr/lib/x86_64-linux-gnu/perl5/5.20/ZOOM.pm, but I'm not sure if Koha's execution path ever calls option_binary(), which is the subroutine where connection_option_setl() is called, nor am I sure that this will actually override the default value of 1MB. -- You are receiving this mail because: You are watching all bug changes.