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
Both indicator length and identifier length is incorrect. The latter explains your subfield of "aEu". If we force those to be normal values it would break some records which actually have indicator length of 3. Admitted those with indicator length of 3 would have to be MarcXchange in order to be valid. As for the identifier. That has always been 2 so far. If your leader is bogus, you can also just remove it entirely.. YAZ will make one, then.
We ran across a MARCXML record that used "4" in leader position 10, and when converted to JSON, resulted in garbage output such as this;
{ "245": { "subfields": [ { "aEu":"noia" } ], "ind1":"1", "ind2":"0", "ind3":" ", "ind4":" " } }
AFAICT, leader position 10 shouldn't be consulted in a MARCXML to JSON conversion as it seems specific to the MARC serialization.
The text was updated successfully, but these errors were encountered: