Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upMARCXML import breaks when a subfield is empty #1722
Comments
adam3smith
self-assigned this
Aug 24, 2018
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
yup, thanks, I have a fix for this, coming shortly |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
closed via e234d96 |
adam3smith
closed this
Aug 25, 2018
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
adam3smith
Aug 25, 2018
Collaborator
FWIW, I do think this is an error by Code4Lib -- their MAiRCXML isn't all that good overall -- but I don't see any reason to not just skip empty subfields.
FWIW, I do think this is an error by Code4Lib -- their MAiRCXML isn't all that good overall -- but I don't see any reason to not just skip empty subfields. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
bencomp commentedAug 23, 2018
I see this error in the console when I look at a Code4Lib Journal article:
Using the debug log I found that the Code4Lib Journal translator was broken (see #1721) and that Zotero tries to use the MARCXML translator on the unAPI MARCXML output. This output contains an empty (string in a) subfield:
<marc:subfield code="a"></marc:subfield>
, which I guess is the reasonsf is null
in:translators/MARCXML.js
Lines 64 to 67 in 2d3e4bd
All other subfields contain text.
I don't know for sure if this is an error on the Code4Lib Journal side – empty tags don't add value, but I don't know if they are forbidden. Perhaps the translator should be aware of and resistent to empty subfield elements?