Curate Task 'Register DOI' not actually registering DOI, error in logs.

[Carolyn Sullivan]

Hello friends,

On Thursday, January 9th, our Scholarly Communications Librarian ran a Curate task to register a couple DOIs.  Despite this process running without incident many times before, for some reason, the process ran to completion, stated it was successful, and returned the DOIs.  However, the DOIs themselves did not resolve, and when we checked in DataCite Fabrica, it looked like they were never registered.

Examination of the logs shows these errors:

dspace.log-2025-01-09:2025-01-09 15:12:30,519 INFO  unknown unknown org.dspace.app.rest.scripts.handler.impl.RestDSpaceRunnableHandler @ Process id: 134, script name: curate, message: Curation task: registerdoi performed on: 10393/ [redacted]  with status: 0. Result: 'DOI registration task performed on 10393/[redacted]. DOI: (doi:10.20381/[redacted])'
dspace.log-2025-01-09:2025-01-09 20:00:29,032 ERROR unknown unknown org.dspace.identifier.doi.DataCiteConnector @ While reserving a DOI, the crosswalk to generate the metadata used another DOI than the DOI we're reserving. Cannot reserve DOI doi:10.20381/ [redacted]   for ITEM  [redacted]  .
dspace.log-2025-01-10:2025-01-10 04:00:29,315 ERROR unknown unknown org.dspace.identifier.doi.DataCiteConnector @ While reserving a DOI, the crosswalk to generate the metadata used another DOI than the DOI we're reserving. Cannot reserve DOI doi:10.20381/ [redacted]   for ITEM  [redacted] .
dspace.log-2025-01-10:2025-01-10 12:02:00,970 ERROR unknown unknown org.dspace.identifier.doi.DataCiteConnector @ While reserving a DOI, the crosswalk to generate the metadata used another DOI than the DOI we're reserving. Cannot reserve DOI doi:10.20381/ [redacted]  for ITEM  [redacted]  .
dspace.log-2025-01-10:2025-01-10 20:00:26,906 ERROR unknown unknown org.dspace.identifier.doi.DataCiteConnector @ While reserving a DOI, the crosswalk to generate the metadata used another DOI than the DOI we're reserving. Cannot reserve DOI doi:10.20381/ [redacted]   for ITEM  [redacted]  .
dspace.log-2025-01-11:2025-01-11 04:00:28,589 ERROR unknown unknown org.dspace.identifier.doi.DataCiteConnector @ While reserving a DOI, the crosswalk to generate the metadata used another DOI than the DOI we're reserving. Cannot reserve DOI doi:10.20381/[redacted] for ITEM  [redacted]  .

dspace.log-2025-01-11:2025-01-11 12:00:28,286 ERROR unknown unknown org.dspace.identifier.doi.DataCiteConnector @ While reserving a DOI, the crosswalk to generate the metadata used another DOI than the DOI we're reserving. Cannot reserve DOI doi:10.20381/ [redacted]  for ITEM  [redacted] .
dspace.log-2025-01-11:2025-01-11 20:00:29,240 ERROR unknown unknown org.dspace.identifier.doi.DataCiteConnector @ While reserving a DOI, the crosswalk to generate the metadata used another DOI than the DOI we're reserving. Cannot reserve DOI doi:10.20381/ [redacted]   for ITEM  [redacted] .
dspace.log-2025-01-12:2025-01-12 04:01:05,086 ERROR unknown unknown org.dspace.identifier.doi.DataCiteConnector @ While reserving a DOI, the crosswalk to generate the metadata used another DOI than the DOI we're reserving. Cannot reserve DOI doi:10.20381/ [redacted]   for ITEM  [redacted]  .
dspace.log-2025-01-12:2025-01-12 12:01:03,406 ERROR unknown unknown org.dspace.identifier.doi.DataCiteConnector @ While reserving a DOI, the crosswalk to generate the metadata used another DOI than the DOI we're reserving. Cannot reserve DOI doi:10.20381/ [redacted]   for ITEM  [redacted]  .
dspace.log-2025-01-12:2025-01-12 20:00:28,290 ERROR unknown unknown org.dspace.identifier.doi.DataCiteConnector @ While reserving a DOI, the crosswalk to generate the metadata used another DOI than the DOI we're reserving. Cannot reserve DOI doi:10.20381/ [redacted]   for ITEM  [redacted]  .

Any idea why this is happening?  The only issue I found that looked similar on Github was this: https://github.com/DSpace/DSpace/issues/9641

Thanks,

Carolyn.

[Carolyn Sullivan]

 In case anyone else has this issue: It was in fact the issue identified in the Github issues for DSpace.  We confirmed as much by editing the metadata for the affected resource and removing the DOI from the citation.  The DOI registered the next time that cronjob ran.  We haven't applied the patch yet that's supposed to prevent it from happening in the future or confirmed that it does in fact work, but here it is:

https://github.com/DSpace/DSpace/pull/9671/commits/9e11e1f9ae69f19e506618d1d0b1fec0059ba165