Metadata Manager deposits failing when deposit includes issue-level contributors - alt-name field not being populated correctly in the XML

User 'nyun' has discovered that when including issue-level contributor metadata that submissions via MDT are failing because MDT is not populating the alternative name field correctly in the XML.

Screen_Shot_2019-12-17_at_2.22.56_PM

See submission https://doi.crossref.org/servlet/submissionAdmin?sf=rerun&submissionID=1460090743 as an example. Although the user has left the alternative name field blank, the admin tool and MDT is throwing the following error:

<?xml version="1.0" encoding="UTF-8"?>
<doi_batch_diagnostic status="completed" sp="ds5">
   <submission_id>1460090743</submission_id>
   <batch_id>153a5c08-fa14-491f-81d9-86827dee228e</batch_id>
   <record_diagnostic status="Failure">
      <doi />
      <msg>Error: cvc-complex-type.2.4.b: The content of element 'alt-name' is not complete. One of '{"http://www.crossref.org/schema/4.4.0":name, "http://www.crossref.org/schema/4.4.0":string-name}' is expected.
Error: cvc-complex-type.2.4.b: The content of element 'alt-name' is not complete. One of '{"http://www.crossref.org/schema/4.4.0":name, "http://www.crossref.org/schema/4.4.0":string-name}' is expected.
Error: cvc-complex-type.2.4.b: The content of element 'alt-name' is not complete. One of '{"http://www.crossref.org/schema/4.4.0":name, "http://www.crossref.org/schema/4.4.0":string-name}' is expected.
</msg>
   </record_diagnostic>
   <batch_data>
      <record_count>1</record_count>
      <success_count>0</success_count>
      <warning_count>0</warning_count>
      <failure_count>1</failure_count>
   </batch_data>
</doi_batch_diagnostic>

The XML being generated by MDT looks like this:

<full_title>Journal on Education in Emergencies</full_title>
<abbrev_title>JEIE</abbrev_title>
<issn media_type="print">2518-6833</issn>
<doi_data>
<doi>10.33682/nsvs-wq51</doi>
<resource>https://inee.org/evidence/journal</resource>
</doi_data>
</journal_metadata>
<journal_issue>
<contributors>
<person_name sequence="additional" contributor_role="editor">
<given_name>Sarah</given_name>
<surname>Dryden-Peterson</surname>
<affiliation>Harvard University</affiliation>
<ORCID>https://orcid.org/0000-0002-0849-9489</ORCID>
<alt-name/>
</person_name>
<person_name sequence="additional" contributor_role="editor">
<given_name>Jo</given_name>
<surname>Kelcey</surname>
<affiliation>New York University</affiliation>
<alt-name/>
</person_name>
<person_name sequence="additional" contributor_role="editor">
<given_name>S. Garnett</given_name>
<surname>Russell</surname>
<affiliation>Columbia University Teachers College</affiliation>
<ORCID>https://orcid.org/0000-0002-2814-4714</ORCID>
<alt-name/>
</person_name>
</contributors>
<titles>

Definition of ready

  • Product owner: @SaraBowman
  • Tech lead: @myalter
  • Service:: label applied
  • Definition of done updated
  • Acceptance testing plan:
  • Weight applied

Definition of done

  • Unit tests identified, implemented, and passing
  • Code reviewed
  • Knowledge base reviewed and updated
  • Consider any impacts to current or future architecture/infrastructure, and update specifications and documentation as needed
  • Public documentation reviewed and updated
  • Available for acceptance testing via a staging URL, or otherwise
  • Acceptance criteria met
    • AC 1
    • AC 2

Related Zendesk tickets for internal reference: 153302, 165531, 164201, 163372, 161642, 155089, 151983, 154116, 160246

Edited by Patrick Polischuk