DOIs that return a "Warning" status in your submission logs have been deposited, but may need extra attention. A "Failure" status means that either a particular DOI has not been deposited or the entire deposit file was unable to be processed due to some error.
Warnings
| Warning | Meaning | Solution |
|---|---|---|
| Added with conflict | The DOI was deposited; however, there was already another DOI in our system with identical metadata. This often occurs when an article is published ahead of print and deposited with no page numbers. | Review DOIs with warnings and resolve all conflicts. |
Errors: System Checks
When processing a metadata deposit, we do a number of checks to prevent the introduction of bad data to our system.
| Error | Meaning | Solution |
|---|---|---|
| Record not processed because submitted version: xxxxxxx is less or equal to previously submitted version (DOI match) | The timestamp in this deposit file is numerically smaller than the timestamp in a previous deposit for this same DOI. | Review and edit the timestamp included in the deposit. Timestamps can be found by reviewing past deposits, in the depositor report, or by retrieving the DOI's metadata record. |
| User with ID: {0} cant submit into handle, please contact the Crossref admin | The handle system username and password assigned to this prefix is incorrect in the Crossref system. | This is usually a clerical error. Contact support - include submission ID in your email |
User not allowed to add records for prefix: {0} |
The username that was used to submit this deposit does not have permissions to deposit DOIs beginning with this prefix. | Confirm that you are using the appropriate account and prefix. Contact support and include submission ID in your email. |
| All prefixes in a submission must match (DOI[{0}]) |
All DOIs included in a single deposit submission must have the same prefix, regardless of ownership. | Revise submission and split file into multiple deposits, each with a single prefix. Then resubmit new deposit files. |
| title "{title}" was previously deleted by a Crossref admin | The title record being deposited or updated was deleted from our system, usually at the publisher's request. |
Review your title and compare to previous deposits for that type of content. Contact support and include submission ID in your email. |
|
user not allowed to add or update records for the title "{title}" |
The Crossref account/username that was used to submit this deposit does not have permissions to deposit for this title. | Review title to confirm that you are using the appropriate account and prefix. Contact support and include submission ID in your email. |
|
ISSN "12345678" has already been assigned to a different title/publisher/content type |
The ISSN, title, or ownership of your deposit does not match the title information we have on record. | Review your ISSN and compare to previous deposits for that title. Refer to the ISSN error help document. Contact support and include submission ID in your email. |
|
http://doi.org/submitted-doi is not a valid URL |
The DOI link has been incorrectly used as the resolution URL and therefore the submission is invalid. The resolution URL registered should be the online location of the content. | Update the resolution URL registered so that it is the online location of the content. Then the submission will be processed successfully and the DOI link (http://doi.org/submitted-doi in this example) will resolve to the online location (URL) registered. |
Errors: Some Common Validation and Processing Errors
| Error | Meaning | Solution |
|---|---|---|
| [error] :286:24:Invalid content starting with element {element name}'. The content must match '(("http://www.crossref.org/schema/4.3.0": item_number) {0-3}, ("http://www.crossref.org/schema/4.3.0": identifier) {0-10}) | This is an example of a parsing error being reported in the log file. Since this output comes directly from the Xerces parser the actual message will vary depending on the error. | Review file at line / column indicated (in this example line 286 col. 24) edit and re-submit. Contact support for help if needed. |
| org.jdom.input.JDOMParseException: Error on line 312 of document file:///export/home/resin/journals/crossref/inprocess/395032106: The content of elements must consist of well-formed character data or markup. | Unacceptable markup in file | Review the file as indicated, correct, and re-submit. |
[fatal error] :1:1: Content is not allowed in prolog. |
Characters precede the XML declaration. This is almost always a Byte Order Mark (BOM) which most often occurs when word processing programs are used to edit XML files. | Open file in a text / XML editor and remove characters (usually ). If the encoding is shown as "UTF-8 With BOM" change this to "UTF-8" or "UTF-8 Without BOM." Then resubmit the deposit. |
| java.io.UTFDataFormatException: invalid byte 1 of 1-byte > UTF-8 sequence (0x92) | There is a badly encoded character. | Locate and correct the bad character encoding. Refer to Using Special Characters for more details. |
| java.sql.SQLException: ORA-00001: unique constraint (ATYPON.NDX1_CIT_RELS) violated | Two files containing the same DOIs have been submitted simultaneously. The system attempts to process both deposits, but only one deposit will be successful. The unsuccessful deposit will generate this error. | Review DOI metadata to be sure it was updated correctly. |
| java.lang.NullPointerException | Most often this means a citation-only deposit or multiple resolution resource-only deposit has been uploaded as a metadata deposit (or vice-versa) | Resubmit deposit as 'DOI Resources' or doDOICitUpload. If this does not apply to your deposit, contact support@crossref.org with details, including submission ID. |
| Submission version NULL is invalid | Schema declaration is incorrect. | Resubmit with correct schema declaration |
| Invalid namespace/version | Wrong operation type, or submitted file is not XML | submit with correct operation type |
Comments
0 comments
Please sign in to leave a comment.