Genre Error on DOI Submission

Hi

This article in a conference proceedings sits in an OJS repository and we are using the OJS Crossref plugin to submit new DOIs via XML.

14 of our 15 Proceedings / Journals are wokring fine.

Just one gives the following “genre” error.

I have double checked the ISSN and Title.

Please can someone assist and let me know how to resolve??

~p6steve

-----Original Message-----
From: Crossref
Sent: 14 October 2022 16:00
Subject: CrossRef submission ID: 1544767535

<?xml version="1.0" encoding="UTF-8"?>
<doi_batch_diagnostic status="completed" sp="ds3.crossref.org">
<submission_id>1544767535</submission_id>
<batch_id>_1665758844</batch_id>
<record_diagnostic status="Failure" msg_id="22">
<doi>all doi's under the current journal element</doi>
<msg>ISSN "2049100X" has already been assigned, title/issn: European Conference on Games Based Learning/2049100X is assigned to another genre: CONFERENCE_PROCEEDING_SERIES</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>

Hi @p6steve ,

Thanks for your message, and welcome to the community forum!

The issue here is that ISSN 2049100X was previously registered as a conference series. I have removed that ISSN from the record associated with the conference series and have successfully reprocessed your submission.

DOI 10.34190/ecgbl.16.1.914 has now been registered, as you can see from the submission log:

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

<doi_batch_diagnostic status=“completed” sp=“ds5”>
<submission_id>1544767535</submission_id>
<batch_id>_1665758844</batch_id>
<record_diagnostic status=“Success”>
10.34190/ecgbl.16.1.914
Successfully added
</record_diagnostic>
<batch_data>
<record_count>1</record_count>
<success_count>1</success_count>
<warning_count>0</warning_count>
<failure_count>0</failure_count>
</batch_data>
</doi_batch_diagnostic>

Warm regards,
Isaac

Hi @ifarley - thank you for your rapid response and for solving the issue!

Please do close the ticket

1 Like