Register DOI button on submission page returning errors in Dspace9.1
Romy Forrer
We seem to be experiencing a similar bug to https://github.com/DSpace/DSpace/issues/8732 which was fixed by https://github.com/DSpace/DSpace/pull/8752 again in 9.1. with identifiers.submission.register = true. The Register DOI button in showing in item status page and brings up the metadata check page but clicking the confirm button on the check page does not work first time it is pressed (no DOI is created/saved). Second time it is pressed 2 error modals pop up on screen but a DOI is actually created for the item. The items we were trying to mint DOIs for are not included in our item-filter for auto-minting of dois (hence why we have to use this option).
The error stack trace from dspace log is a bit different to the example in 8752 (full error stack attached) e.g. first few lines:
2026-02-26 17:46:57,695 ERROR ec44c601-409f-408d-a55b-71e8e4527381 8c020bb6-4914-485a-9429-58028d993a0b org.dspace.event.BasicDispatcher @ Consumer("doi").consume threw: org.dspace.identifier.doi.DOIIdentifierNotApplicableException: Item 10092/109409 was evaluated as 'false' by the item filter, not minting
org.dspace.identifier.doi.DOIIdentifierNotApplicableException: Item 10092/109409 was evaluated as 'false' by the item filter, not minting
at org.dspace.identifier.DOIIdentifierProvider.checkMintable(DOIIdentifierProvider.java:1141) ~[dspace-api-9.1.jar:9.1]
at org.dspace.identifier.DOIIdentifierProvider.loadOrCreateDOI(DOIIdentifierProvider.java:1007) ~[dspace-api-9.1.jar:9.1]
at org.dspace.identifier.DOIIdentifierProvider.mint(DOIIdentifierProvider.java:622) ~[dspace-api-9.1.jar:9.1]
I've been checking our identifier configurations against what we had when this was working in 7.6 which we upgraded from. Thus far it all looks correct (not identical to 7.6 as we had workarounds for bugs subsequently fixed).
There are also errors related to versions. We have item versioning disabled and just using DOIIdentifierProvider rather than the versioned option in identifiers-service.xml. In 7.6 there were bugs with this and we had to comment out versioning.enabled = false in local.cfg as well as use the class (org.dspace.identifier.VersionedDOIIdentifierProvider) in the DOIIdentifierProvider bean. I had thought all bugs related to this were fixed now so reverted our 9.1 configuration for the bean back to the example. Looking closer at PR 8752 the fix for it only adjusted the code for dspace-api/src/main/java/org/dspace/identifier/VersionedDOIIdentifierProvider.java. Now we are using the DOIIdentifierProvider class in identifier-service.xml again so I guess that could explain why we now have the issue occurring?
Curious if anyone else not using versioning and with identifiers.submission.register = true is also experiencing this. Not sure if it is still wise to change the class back to
VersionedDOIIdentifierProvider to get around this issue given the amount of code change in dspace between 7.6 and 9.1.
Kind Regards,
Romy
Romy Forrer
Library Systems Coordinator
University of Canterbury