Conflict management submissions
Conflict management submissions are used to resolve conflicts in batch. They can
be used to automate the conflict management functions available through the
admin interface.
The format of Conflict management submissions is simple: The first line
is considered the submission header followed by line separated DOIs. The
format of the header is as follows:
<![CDATA[
H:email=<email>;op=<operation>
]]>
Where op is one of: primary,alias,unresolve or resolve
For example: The following submission instructs corssref to make the DOIs: 10.5555/test1 and 10.5555/test2
primary in all the conflicts it appears in:
<![CDATA[
H:email=hisham@atypon.com;op=primary
10.5555/test1
10.5555/test2
]]>
Note that op=alias should be used when the primary DOIs are not known. If there are more than 2 DOIs in the
conflict then the operation is rejected since the system can't decide automatically which DOI to prime.
The result of the submission conforms to the following DTD:
<!ELEMENT doi_batch_diagnostic (submission_id,record_diagnostic*) >
<!ELEMENT submission_id (#PCDATA) >
<!ELEMENT record_diagnostic (conflict*,msg?) >
<!ATTLIST record_diagnostic doi CDATA #REQUIRED >
<!ATTLIST record_diagnostic status (Error) #IMPLED >
<!ELEMENT conflict (msg,doi_list) >
<!ATTLIST status (Success | Warning) #REQUIRED >
<!ATTLIST ids CDATA #REQUIRED >
<!ELEMENT msg (#PCDATA) >
<!ELEMENT doi_list (doi*) >
<!ELEMENT doi (#PCDATA) >
For example: Here is the result of making 10.5555/prime a primary DOI for 2 other DOIs: 10.5555/a1 and 10.5555/a2
<![CDATA[
<?xml version="1.0" encoding="UTF-8"?>
<doi_batch_diagnostic>
<submission_id>1181263946</submission_id>
<record_diagnostic doi="10.5555/prime">
<conflict status="Success" ids="23135669,2311211">
<msg>Marked as alias</msg>
<doi_list>
<doi>10.5555/a1</doi>
<doi>10.5555/a2</doi>
</doi_list>
</conflict>
</record_diagnostic>
</doi_batch_diagnostic>
]]>
Forced aliasing
Publishers can also force a DOI to be an alias of another even if those 2 DOIs are not in conflict. The format
of the submission is the same. Supplying op=force_alias expects the submission to have a line separated pairs
of space separated DOIs as follows:
<primary DOI> <alias DOI>
Supplying op=unalias allows you to unalias
previously forced aliases. The submission payload in this case expects a list of line separated DOIs you wish
to unalias.
The result of such submission still conforms with the DTD as above. For example:
<![CDATA[
<?xml version="1.0" encoding="UTF-8"?>
<doi_batch_diagnostic>
<submission_id>219253106</submission_id>
<record_diagnostic doi="10.5555/test_forced_alias_doi2">
<msg>Sucessfully aliased to: 10.5555/test_forced_alias_doi1</msg>
</record_diagnostic>
</doi_batch_diagnostic>
]]>
