You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
a) if the record is indeed invalid:
aa) shall we make the encode-marc21 make more forgiving?
ab) or is it enough to bail out (as it is atm) resp. to expect the user to use catch-stream-exception resp. fix the invalid MARC ?
b) if the record is valid: fix encode-marc21
The text was updated successfully, but these errors were encountered:
Came up in #527 :
If we parse (assumingly) crude binary
MARC
the encoding fails.(first broken
MRC
seems to be02589nas a2200601 c 4500
in https://raw.githubusercontent.com/gbv/Catmandu-Tutorial/master/data/marc.mrc (should be double checked with another MARC-validator other than MF:Because MARCs binary
directory
of field787
points toIso646Constants.INFORMATION_SEPARATOR_2 = 0x1e
the encoding breaks))If an encoding breaks not only the field is dumped or the whole record but the whole stream. The dumping of the record and - more important- the whole stream can be avoided by piping
decode-marc21
tocatch-stream-exception
before piping toencode-marc21
.a) if the record is indeed invalid:
aa) shall we make the
encode-marc21
make more forgiving?ab) or is it enough to bail out (as it is atm) resp. to expect the user to use
catch-stream-exception
resp. fix the invalid MARC ?b) if the record is valid: fix
encode-marc21
The text was updated successfully, but these errors were encountered: