DataCite updates and Dataverse

[Courtney Mumma]

Hi all,

Not sure if this should be a github issue, so I'm mentioning here on the list and perhaps we can touch on it in the next Community Call? DataCite has informed its communities about some updates, and I'm curious about how they will impact Dataverse instances.

The following is some of the text from their update.

....

New release: DataCite Metadata Schema 4.5

We are pleased to announce the release of DataCite Metadata Schema 4.5. Please see the following links for more information: 

· Announcement: Introducing DataCite Metadata Schema 4.5 (https://lists.datacite.org/t/t-l-vkiyhjl-sojiluii-y/)

· All DataCite Metadata Schema documentation is accessible from https://schema.datacite.org/(https://lists.datacite.org/t/t-l-vkiyhjl-sojiluii-j/) .

Upcoming Deprecation of DataCite Metadata Schema 3

As announced last month, DataCite Metadata Schema 3 will be deprecated on January 1, 2025. Please see the following links for more information:

· Announcement: Deprecating Schema 3 (https://lists.datacite.org/t/t-l-vkiyhjl-sojiluii-t/)

· Support documentation: Updating from Schema 3 to Schema 4 (https://lists.datacite.org/t/t-l-vkiyhjl-sojiluii-i/)

Repositories using Schema 3 should begin the transition to Schema 4 as soon as possible. Please contact us at sup...@datacite.org for assistance.

To learn more about the schema changes, please also consider joining the upcoming webinar “Updating the DataCite Metadata Schema: Introducing Schema 4.5 and deprecating Schema 3 (https://lists.datacite.org/t/t-l-vkiyhjl-sojiluii-d/) ” on March 13, 2024, 3pm (UTC).

...

Best to you all, and see you February 6th on the call,

Courtney

[Julian Gautier]

Hi Courtney,

I agree, discussing during a community call would be helpful.

Specifically I've been wondering if the deprecation of DataCite Metadata Schema 3 affects any Dataverse repositories, especially any repositories that are sending DataCite more metadata than Dataverse sends "out of the box". I imagine that this won't be an issue since those repositories have always based their changes on one of the schema 4 versions.

So far, I can't recall any changes in schema 4.5 that would affect our plans to have repositories using Dataverse send more dataset metadata to DataCite when publishing datasets. But the community call would be a great chance to hear from others.

[Philip Durbin]

Thanks Courtney and Julian.

It looks like Jim upgraded Dataverse from DataCite schema version 3 to 4 back in Dataverse 4.10: https://github.com/IQSS/dataverse/pull/5047

So yes, perhaps installations running Dataverse 4.9 or older should consider upgrading to keep up with DataCite's changes.

--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-commu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/b4901edd-72a2-4505-b285-bf2b5450fa46n%40googlegroups.com.

--

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

[Philipp Conzett]

We're currently figuring out whether we need to do anything to prepare our Dataverse installation for January 1, 2025, when DataCite won't support DataCite Metadata Schema 3 anymore; see discussion above.

We've currently almost 600 DOI records in DataCite using DataCite Metadata Schema 3 (kernel-3). Most of these records are file-level DOI records. I've done some testing:

1. All metadata records I've exported from our Dataverse installation, refer to kernel-4.
2. After upgrading dataset metadata and publishing a new version of a dataset with a kernel-3 record in DataCite, the dataset DOI record in DataCite changes from kernel-3 to kernel-4.
3. After upgrading file metadata (= adding a file tag) and publishing a new version of a dataset with a kernel-3 file-level DOI record in DataCite, the file-level DOI record in DataCite still refers to kernel-3.
4. After deleting an existing file and adding a new version of the file and then publishing a new version of a dataset with a kernel-3 file-level DOI record in DataCite, the file-level DOI record in DataCite changes from kernel-3 to kernel-4.

Behaviour 1, 2, and 4 above seem to indicate we won't run into DataCite trouble once kernel-3 is deprecated. But what about behaviour 3? Any thoughts on this? Do other installations have similar experiences?

Best,
Philipp

[James Myers]

Philipp,

There’s an API call to update the metadata at the PID provider: https://guides.dataverse.org/en/latest/admin/dataverses-datasets.html#update-metadata-for-a-published-dataset-at-the-pid-provider – without having to make any changes to the dataset.  I’m not sure when it was introduced but it’s been around for a while. In v6.4, we recommending using this, or the bulk version (which wasn’t documented previously and used GET instead of POST) to update the DataCite metadata to the 4.5 schema with many additional fields added (see #10632 for details).

 

-- Jim

To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/6af98927-d125-466d-b97a-fbe33e00cb4an%40googlegroups.com.

[Philipp Conzett]

Thanks Jim! We've updated all the affected DataCite dataset-level DOI records using the API call you pointed to. This worked well, except for 35 file-level DOI records, which still display "kernel-3" in their DataCite metadata record. These files are found in the following 6 datasets:

https://doi.org/10.18710/DG75YC
https://doi.org/10.1870/LI8A7X
https://doi.org/10.18710/LHCGYQ
https://doi.org/10.18710/LI8A7X
https://doi.org/10.18710/LOWPDQ
https://doi.org/10.18710/TWALRY

I haven't been able to find out why we haven't managed to update the metadata records of the files in these datasets from kernel-3 to kernel-4.

Do others have similar issues?

Best,
Philipp

[James Myers]

I’m not sure. If an error occurred, there should hopefully be info in the server log. Another possibility (that I guess should be considered a bug) is that it looks like file PIDs aren’t updated by the modify api call (and most commands related to PIDs) unless file PIDs are enabled in the collection. So if file PIDs were on at one point and aren’t now, I don’t think they’d get updated. In that case, a work-around would be to enable file PIDs temporarily and run the modify command again.

To view this discussion visit https://groups.google.com/d/msgid/dataverse-community/ac681824-c742-4416-9e56-7d0f7e559f2an%40googlegroups.com.

[Benedikt]

Do you want to talk to us (UiT: IT Department), Philipp Conzett?