IQSS / IQSS/dataverse

In OpenAIRE/oai_datacite export, use `dateType` "Updated" for date of latest published version only after user has published more than one version

Open
#12,294 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

GREI 2 GREI 3 GREI 4 Size: 3
Dominant language
Java
Stars
1.1k
Forks
564
Avg merge
2d 2h
Merged PRs (30d)
29

Description

Overview of the Feature Request

To match what the DataCite/Datacite export does, the OpenAIRE/oai_datacite export should use the dateType "Updated" only when the user has published more than one version and to indicate when the user published the dataset's latest published version.

Currently, the OpenAIRE/oai_datacite export uses "Updated" to indicate when the latest version was published, even when the user published only one version.

This issue is part of a larger effort to align both metadata exports, described in https://github.com/IQSS/dataverse/issues/11916 and https://github.com/IQSS/dataverse/issues/12281.

What kind of user is the feature intended for?

API User, Superuser, and Sysadmin

What inspired the request?

This is part of a larger effort to align the OpenAIRE/oai_datacite and DataCite/Datacite metadata exports. There is more context at https://github.com/IQSS/dataverse/issues/11916 and https://github.com/IQSS/dataverse/issues/12281.

What existing behavior do you want changed?

Currently, the OpenAIRE/oai_datacite export uses "Updated" to indicate when the latest version was published, even when the user published only one version.

<date
    dateType="Updated">2025-12-07
</date>

The DataCite/Datacite export uses the "Updated" dateType only when the user has published more than one version of the dataset, to indicate when the user published the dataset's latest published version.

The OpenAIRE/oai_datacite export should be changed to use the "Updated" dateType and the "Available" dateTypein the same ways that the DataCite/Datacite export does.

Any open or closed issues related to this feature request?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Compare the OpenAIRE/oai_datacite export with the DataCite/Datacite export, focusing on their dateType handling. Verify the XML for datasets with one published version and with multiple published versions; done means Updated and Available dates match the requested behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
api, backend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
56/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.