Submission version NULL is invalid (?)

Any idea what could be wrong here? Below is the diagnostic email I’m getting when posting XML for a journal issue with articles to the Crossref test registration system. I searched the forum for “submission version” and didn’t find anything useful. The same XML file seems to pass the online metadata quality checker tool, but my understanding is that it isn’t quite as strict.

<?xml version="1.0" encoding="UTF-8"?>

<doi_batch_diagnostic status=“completed” sp=“a-cs1”>
<record_diagnostic status=“Failure” msg_id=“1”>

Submission version NULL is invalid

NMG-DOI.xml (5.7 KB)

Hi Adam,

Thanks for your post.

Invalid xml is only one of several reason why a metadata deposit might not work. There are a number of additional requirements imposed by our system during the deposit processing.

In this case, we require a “version” be included among the namespace/schema declarations in <doi_batch>.

Currently, you’re missing that version value.

<doi_batch xmlns="" xmlns:jats="" xmlns:xsi="" xsi:schemaLocation="">

If you add version=“5.3.0” in there, that should take care of the problem.
It shouldn’t really matter where it goes within the <doi_batch> declarations.

<doi_batch version="5.3.0" xmlns="" xmlns:jats="" xmlns:xsi="" xsi:schemaLocation="">

Please let us know if you run into any other issues testing the deposits.


1 Like