I submitted an XML deposit to test new changes for pending publication updates as per your pending publication page.
This is the error:
{“batch_id”:“apsxref:d17fc912-9629-4c64-820e-ddb576ed167b”,“doi”:“10.1103/y7sy-3by1”,“msg”:“Article is is not a pending publication!”,“submission_id”:“1705516759”}
This is an accepted paper that has not been published yet, but was submitted perviously on July 16 (batch id: apsxref:5bfaffac-8453-4090-bbf7-6793079bc6e1).
Wondering if this error was because the first deposit of the accepted paper was not in a pending state.
Wondering if this error was because the first deposit of the accepted paper was not in a pending state.
Yes, that’s correct. You can only apply the pending publication record type to new DOIs, with the expectation that they’ll later be updated as a full record type (journal article, book chapter, conference paper, etc.) when the content is fully published.
You can’t go backwards from a journal article (or any other record type) record to a pending publication record. The workflow only goes in one direction.
When checking this submission, I also noticed that you have “Anonymous” submitted as the author surname. That’s not quite correct. Starting with schema 5.3.0, we have a <anonymous> option within <contributors> that should be used for anonymous authors.
Using schema versions prior 5.3.0, the best option is just omit the <contributors> section entirely if all authors are anonymous. That’s not ideal, and not necessary in your situation, since your xml uses version 5.3.1. But that’s just to say, best not to mischaracterize “Anonymous” as if it’s an actual name.
Please let me know if you have any further questions.
I posted this in another topic, but it should here
We submitted XML for an accepted paper with new XML format with the first element under the body element is pending_publication with intent_statement based on your pending publications document. We received this error:
A valid publication was not found.
The batch id is: apsxref:de4e9978-0e80-41fa-94b6-8f0913a9c43c
DOI is 10.1103/7q6l-d4qh
Can you provide insight if this is just an error or am I missing something from your documentation. I can rollback my code to avoid an onslaught of these errors if needed.