-
Notifications
You must be signed in to change notification settings - Fork 3
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
DOI Service does not accurately parse <author_list> and <editor_list> in XML labels #377
Comments
Current information model doesn't appear to allow for the possibility of organisation/mononym authors. @jordanpadams, that seems like an oversight worth fixing. Provided value Will fix, such that mononym values are written to the author last-name field, with a blank first-name field (if that doesn't cause validation problems - need to check). Suggest that authors like |
Ah, I see now - names like I've done the best I can untangling the name parsing logic, but to go any further with it I'll need a comprehensive list of name strings which the parser is expected to support. My tests support:
but the first/middle-name ordering is broken for (for example)
because detection of first/middle-name ordering isn't well-defined, currently. |
@jordanpadams existing tests suggest a need to support format |
@jordanpadams I found these cases
|
Final list of supported formats:
|
🐛 Describe the bug
When parsing the <author_list> and <editor_list> in PDS4 XML labels, a wobbly is thrown if the value doesn't follow the formation rules for using commas and semicolons. For instance, this series of values will fail:
<author_list>smith, john; jones, tom, NASA; Google, Inc.</author_list>
(1) NASA will throw a wobbly because there is no comma
(2) Google will be parsed inaccurately as <last_name>, <first_name>
📜 To Reproduce
See example above
🕵️ Expected behavior
(1) Allow a value (within the set of values) to not require a comma.
(2) A more difficult fix will be to "interpret" the Google example.
📚 Version of Software Used
N/A
🩺 Test Data / Additional context
🏞Screenshots
🖥 System Info
🦄 Related requirements
⚙️ Engineering Details
Per @jordanpadams let's try to better handle case (1), but I don't think we will ever be able to handle case (2) until the PDS4 Information Model is improved.
The text was updated successfully, but these errors were encountered: