Our system has flagged DOIs 10.38124/https://doi.org/10.38124/ijisrt/IJISRT24MAR129and 10.38124/ijisrt/IJISRT24MAR129 because the bibliographic metadata registered for these two DOIs is identical. We have automatically flagged this in our system and put the DOIs into conflict ID 7235049 because we think there is a chance that the DOIs have been duplicated for the same content. But, since we don’t know your content like you do, we need your help to review the conflict.
In this case, it looks like DOI 10.38124/https://doi.org/10.38124/ijisrt/IJISRT24MAR129 might have been registered in error and really DOI 10.38124/ijisrt/IJISRT24MAR129 is the DOI that should have been registered and will be maintained for the journal article titled ‘Development of Composite Index in Block Level: A Case Study of Nirmal District, Telangana’ going forward. But, again, this is your content so we need you to confirm that.
If DOI 10.38124/ijisrt/IJISRT24MAR129 is the DOI that will be maintained for this journal article, then you should alias the incorrect DOI to that correct one (more on this below in scenario 2). This will effectively hide the incorrect DOI from our APIs and then we’ll be able to make the correct DOI the primary, which will aid in citation matching going forward.
For reference, I am including all of the possible conflict scenarios below.
There are basically three different scenarios that can cause this to occur:
You assigned two DOIs to distinct content items, but accidentally submitted the same metadata for both of them. In this case, one of the DOIs has incorrect metadata. If you resubmit an updated metadata deposit to correct that DOI’s metadata, the conflict will be resolved.
You inadvertently assigned two DOIs to the same content item. In this case, you can resolve the conflict by assigning one of the DOIs (the one you intent to use for that content item in perpetuity) as ‘primary’ and the other as its ‘alias’. The alias will automatically redirect to the primary, and you’ll only need to maintain the primary going forward. There are two methods to assign primary and alias status, and both are described in detail here: Conflict report - Crossref
The two DOIs refer to different content items, but their metadata is so similar that a conflict was flagged falsely. This often happens for items that have very minimal metadata included. In this case, you can accept the conflict as is, using one of the methods described here:
You’ll need to evaluate each of the conflicts that appears on your conflict reports and determine which of the above scenarios applies.
DOIs are designed to be persistent, so they can’t be deleted. That’s why we have this alias process in place.
I have aliased incorrect DOI 10.38124/https://doi.org/10.38124/ijisrt/IJISRT24MAR129 to the correct DOI 10.38124/ijisrt/IJISRT24MAR129 that you will maintain going forward. I have done this using the conflict management tab in our admin tool at doi.crossref.org as described here: Conflict report - Crossref
There is nothing more that you need to do for this specific conflict, albeit you do have other conflicts on your account that need attention. I did not resolved those other conflicts. You should be able to follow this example in order to resolve the remaining conflicts. You have several additional conflicts on your report here: https://0-data-crossref-org.library.alliant.edu/reports/conflictreport/10.38124_conflicts.xml. You’ll notice that the one I resolved yesterday during my afternoon has not yet been removed from the report at https://0-data-crossref-org.library.alliant.edu/reports/conflictreport/10.38124_conflicts.xml. That’s because we update that report at the start of the day on Tuesdays, so my changes are not yet reflect at that link.