Okay, I have found the causes of both problems:
Problem 1: Status doesn't switch to "queued for registration" when accepted
Cause: In the context of Configuring pre-registration of Identifiers I
accidentally set "identifiers.submission.filter.install = doi-filter" in
config/modules/identifiers.cfg.
Solution: Set identifiers.submission.filter.install = always_true_filter
(default)
Problem 2: error "Database table DOI contains a DOI that is not valid" in
command ./dspace doi-organiser -r
Cause: The error message also states the following below: "Caused by:
java.lang.IllegalArgumentException: Handle is null" so no handle is
generated for the new item. DataCite needs to link the registered doi to an
item url which appears to be the metadata value
"{dspace.ui.url}/handle/123456789/x" (e.g. .../handle/123456789/7) in
dc.identifier.uri. Since no handle is created, no uri can be delivered to
datacite and the doi status of the item does not switch.
Solution: In config/spring/api/identifier-service the bean for the
HandleIdentifierProvider has to be uncommented:
<bean id="org.dspace.identifier.HandleIdentifierProvider"
class="org.dspace.identifier.VersionedHandleIdentifierProvider"
scope="singleton">
<property name="configurationService"
ref="org.dspace.services.ConfigurationService"/>
</bean>
Caution: If versioning is disabled, the class must be corrected to
org.dspace.identifier.HandleIdentifierProvider
The HandleIdentifierProvider creates a handle for the new item.
The handle doesn't need to be registered anywhere, it just has to be there
in dc.identifier.uri
Kind regards,
Matthias
Matthias Letsch schrieb am Montag, 6. November 2023 um 15:42:54 UTC+1:
> Thank you Manuele!
>
> Unfortunately, the typo only happened to me here in the problem
> description.
>
> The correct test prefix at DataCite is 10.82770 and also in the dspace.cfg
> is identifier.doi.prefix = 10.82770
>
> So the numbers match. The problem must lie elsewhere.
>
> Kind regards,
> Matthias
>
> Manuele Lorusso schrieb am Montag, 6. November 2023 um 15:09:36 UTC+1:
>
>> Hello Matthias,
>>
>> probably your config "identifier.doi.prefix" was overwritten through the
>> upgrade or a typo has happened
>>
>> Your registered DataCite DOI Prefix (10.87220) differs from the prefix in
>> the Exception Message (10.82770).
>>
>> Best,
>> Manuele
>>
>> Herr Manuele Lorusso
>> Softwareentwickler / Abt. IT-Dienste Forschung, Lehre, Infrastruktur
>> Kommunikations-, Informations-, Medienzentrum (KIM)
>> Universität Konstanz
>> 78457 Konstanz+49 (0)7531 / 88-5403 <+49%207531%20885403>
>> Raum B 707
>>
>> On 03.11.23 13:53, Matthias Letsch wrote:
>>
>> Hello together,
>>
>>
>>
>> we have a DataCite membership and doi registration to our fabrica test
>> environment just worked fine with the configurations set like described in
>> https://wiki.lyrasis.org/display/DSDOC7x/DOI+Digital+Object+Identifier.
>> We use the DataCite API directly.
>>
>>
>>
>> some weeks ago we updated up to version 7.6.1-SNAPSHOT (because of the
>> "browse by subject group" bugfix). I also updated all necessary
>> configuration files regarding the doi registration process:
>> - config/dspace.cfg (everything in "DOI registration agency credential"
>> as well as "crosswalk.dissemination.DataCite.publisher")
>>
>> - config/spring/api/identifier-service.xml (see attachment)
>>
>> - config/item-submission.xml (only for showing pending dois in the
>> submission form)
>>
>> - config/modules/identifiers.cfg (see attachment)
>>
>>
>>
>> By submission a doi is created in the following syntax: 10.87220/x (x =
>> serial number, e.g. 10.87220/7 etc.)
>>
>> Now our doi registration has some strange behaviors and I don’t
>> understand where they come from:
>>
>> 1. The status of the doi doesn't switch automatically from "pending"
>> to "Queued for registration" when a new submission is accepted by admin.
>> (Before the update to 7.6.1, this was the case).
>>
>> 2. So I enabled „registering doi from admin“ to manually set the
>> status "Queued for registration" in the status tab of the item via
>> "identifiers.item-status.register-doi = true" in
>> config/modules/identifiers.cfg.
>>
>> 3. Now, with some items with doi status "queued for registration"
>> (database: 1), I used the typical dspace commands „./dspace doi-organiser
>> -u/-s/-r/-d“, but in command –r (register) an error occured:
>>
>>
>>
>> It wasn't possible to register this identifier: doi:10.82770/7
>> Exception: Database table DOI contains a DOI that is not valid:
>> doi:10.82770/7!
>> java.lang.IllegalStateException: Database table DOI contains a DOI that
>> is not valid: doi:10.82770/7!
>> at (...)
>>
>>
>>
>> How is 10.82770/7 not valid? DSpace did register all dois with that
>> syntax just fine before the dspace version update.
>>
>>
>>
>> 4. So I concluded that the registration didn’t work. Yet here the
>> funny thing is: I looked up our datacite fabrica test environment at
>> https://doi.test.datacite.org/ and there a new item with doi 10.82770/7
>> actually found its way to the registered dois. So DSpace did send the doi
>> to DataCite. BUT in our dspace database at table doi, the doi 10.82770/7
>> STILL has status 1 instead of 3 (1 = queued for registration, 3 =
>> registered) and no doi was written into the metadata (dc.identifier).
>>
>>
>>
>> Does anyone know how this can happen and which configuration file I need
>> to change?
>>
>> Thank you very much!
>>
>> Kind regards,
>>
>> Matthias
>>
>> --
>> All messages to this mailing list should adhere to the Code of Conduct:
>> https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "DSpace Technical Support" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to dspace-tech...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/dspace-tech/9bc03cb4-0167-4891-9283-8d1f0a23585cn%40googlegroups.com
>>
>> <https://groups.google.com/d/msgid/dspace-tech/9bc03cb4-0167-4891-9283-8d1f0a23585cn%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>>
--
All messages to this mailing list should adhere to the Code of Conduct:
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
---
You received this message because you are subscribed to the Google Groups
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/dspace-tech/dde4bef0-ff95-491d-99e1-978ce98b6726n%40googlegroups.com.
