CoinDOI fails silently but id_number still set with DOI

[drn05r]

On occasion, I have noted that the CoinDOI event queue tasks will fail silently as DataCite will return an HTTP error code to one of the requests made but this will not trigger to mark the task as failed and instead it will say it has succeeded and update the id_number field with the expected DOI but when the user tries to follow this DOI it is reported as not being registered.

One scenario where this happens is if the DataCite account being used has got at allowed domains set incorrectly to not include the repository's hostname or an appropriate wildcard representation (e.g. *.example.org). When I send this XML to DataCite's API I get back the following response:

201: OK (10.18765/EPRINTS.DATA.00000123)

The subsequent URL registration fails with the error message:

422: URL is not allowed by repository domain settings.

[wfyson]

Am I right in thinking that in these cases the DOIs exist in a draft status in DataCite and that when the issue is fixed (i.e. the domain has been updated to use a wildcard format) they can then progress to being properly registered DOIs?

If so then the DOI being set in the eprint's id_number field is still valid it's just not active yet. Whilst this is not ideal, I guess it's also not preferable to leave it unset and try re-coining at a later date which might then confuse DataCite because the DOI already exists (either in draft, or possibly now registered form). But then maybe a quick check to see if the DOI already exists and then grab that to use in id_number might fix that issue?