config bug in 6.2 fixed, was preventing creation of datasets when dataverse.pid.default-provider is not set

[Philip Durbin]

Hello Dataverse enthusiasts!

A configuration bug slipped into Dataverse 6.2 that could affect you if you are:

- installing Dataverse for the first time, using 6.2

- using the Python installer (dvinstall.zip rather than Docker)

Out of the box, Dataverse is configured to use the "FAKE" DOI provider, but before the bug was fixed (thanks, Jim!), when you try to create a dataset, it fails and the screen is greyed out (see attached). In server.log you'll see a NullPointerException*.

The fix was to make sure "dataverse.pid.default-provider" is set. I just uploaded a new version of dvinstall.zip that contains this fix (in as-setup.sh) to the 6.2 release: https://github.com/IQSS/dataverse/releases/tag/v6.2

I also updated the 6.2 release notes to mention both the bug ( https://github.com/IQSS/dataverse/issues/10557 ) and the fix ( https://github.com/IQSS/dataverse/pull/10563 ) where you can find additional details.

So! If you saw this problem, please try again! Or reconfigure your installation. If you're still testing with the FAKE provider, you can set it to "dataverse.pid.providers=fake". Or you can reconfigure to use (real) DOIs, Handles, or PermaLinks: https://guides.dataverse.org/en/6.2/installation/config.html#persistent-identifiers-and-publishing-datasets

Sorry for the inconvenience and thank you to the folks who reported this bug!

Thanks,

Phil

* Full error: NullPointerException: Cannot invoke "edu.harvard.iq.dataverse.pidproviders.PidProvider.generatePid(edu.harvard.iq.dataverse.DvObject)" because "pidProvider" is null

--

Philip Durbin
Software Developer for http://dataverse.org
http://www.iq.harvard.edu/people/philip-durbin