in the schema, titles is not a required element in pending_publication, but Pending Publication deposits fail if titles is not included
Background
The pending publication section of the schema shows that publication, acceptance_date, and doi are the only required elements.
Observed behavior
Elife reported deposit failures for Pending Pub, in which the deposit only included those three required elements, e.g.
https://doi.crossref.org/servlet/submissionAdmin?sf=detail&submissionID=1510336895
The error message is unusual, and I found other examples of that error in Zendesk which pointed to a mismatch between the schema's requirements and the deposit processing system's requirements.
<record_diagnostic status="Failure">
<doi>10.7554/eLife.63720</doi>
<msg>No exception localized message</msg>
</record_diagnostic>
<record_diagnostic status="Failure">
<doi>10.7554/eLife.63720</doi>
<msg>A system error has occured</msg>
</record_diagnostic>
I tested with similar metadata and was able to replicate the same error
https://doi.crossref.org/servlet/submissionAdmin?sf=detail&submissionID=1510361424
When I added the <titles>
element to that same test metadata, the deposit was successful.
https://doi.crossref.org/servlet/submissionAdmin?sf=detail&submissionID=1510390045
Based on what I recall from early discussions of Pending Publication, I thought that <intent_statement>
might be required as well. But the deposit worked both with and without it.
https://doi.crossref.org/servlet/submissionAdmin?sf=detail&submissionID=1510384700
Expected behavior
Can we confirm whether <titles>
is supposed to be required for Pending Publication deposits?
If so, we should update the schema and schema documentation.
If not, we should update the deposit system such deposits without <titles>
are successfully processed.
How urgent
Definition of ready
-
Product owner: -
Tech lead: -
Service:: or C:: label applied -
Definition of done updated -
Acceptance testing plan: -
Weight applied
Definition of done
-
Unit tests identified, implemented, and passing -
Code reviewed -
Available for acceptance testing via a staging URL, or otherwise -
Consider any impacts to current or future architecture/infrastructure, and update specifications and documentation as needed -
Knowledge base reviewed and updated -
Public documentation reviewed and updated -
Acceptance criteria met -
AC 1 -
AC 2
-
-
Acceptance testing passed -
Deployed to production