Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Leader indicator length and MARCXML #19

Open
distobj opened this issue Feb 3, 2017 · 2 comments
Open

Leader indicator length and MARCXML #19

distobj opened this issue Feb 3, 2017 · 2 comments

Comments

@distobj
Copy link

distobj commented Feb 3, 2017

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.

@distobj
Copy link
Author

distobj commented Feb 3, 2017

Sorry, forgot the attachment...

leader10-4.zip

@adamdickmeiss
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants