Skip to content

Handle.net PIDs - exception creating new dataset in Dataverse 6.5-6.6 after update from 6.4 #11592

@vkush

Description

@vkush

Dear Dataverse team,
There is a problem creating a new dataset using Handles (Handle.net PID) since update to versions 6.5 and 6.6 - there is an exception about "UnmanagedHandleProvider" and dataset is not created, showing also an error page in GUI "Page Not Found - The page you are looking for was not found.":

[edu.harvard.iq.dataverse.DatasetPage] [tid: _ThreadID=102 _ThreadName=http-thread-pool::jk-connector(1)] [timeMillis: 1749748666538] [levelValue: 1000] [[
  CommandException, when attempting to update the dataset: PID Provider UnmanagedHandleProvider is not configured.
edu.harvard.iq.dataverse.engine.command.exception.IllegalCommandException: PID Provider UnmanagedHandleProvider is not configured.
        at edu.harvard.iq.dataverse.engine.command.impl.CreateNewDatasetCommand.handlePid(CreateNewDatasetCommand.java:100)
        at edu.harvard.iq.dataverse.engine.command.impl.AbstractCreateDatasetCommand.execute(AbstractCreateDatasetCommand.java:134)
        at edu.harvard.iq.dataverse.engine.command.impl.AbstractCreateDatasetCommand.execute(AbstractCreateDatasetCommand.java:26)
        at edu.harvard.iq.dataverse.EjbDataverseEngineInner.submit(EjbDataverseEngineInner.java:36)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
        at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.base/java.lang.reflect.Method.invoke(Method.java:569)

I see in the history, that some changes for PIDs were done for 6.5 (before Dec 2024), but the most of them were done for other PID providers, not for Handles: https://github.com/IQSS/dataverse/commits/develop/src/main/java/edu/harvard/iq/dataverse/pidproviders?after=0177e5d9d4965dd97bfc361d8dace7872be49d78+34
Maybe some needed changes for Handles were skipped, because in version 6.4 the same Handle-config works as expected well.

**To whom does it occur (all users, curators, superusers)?
all users

Which version of Dataverse are you using?
The problem is in 6.5, 6.6. Versions 6.4 and below are correct.

Any related open or closed issues to this bug report?

There is a list of Dataverse instances which are using Handle.Net PIDs: #8881. The latest version of Dataverse there is 6.4.

Communication in the user group: see here.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions