IQSS / IQSS/dataverse

To OpenAIRE/oai_datacite export, add file DOI related identifiers

Open
#12,308 0 comments 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

The OpenAIRE/oai_datacite export should include related identifiers for files that Dataverse registers DOIs for, as the DataCite/Datacite export already does. Currently, the OpenAIRE/oai_datacite export does not include this information.

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 DataCite/Datacite export includes related identifiers for files that Dataverse registers DOIs for. For example:

<relatedIdentifier
    relationType="HasPart"
    relatedIdentifierType="DOI">10.7910/DVN/YKAMUT/QCHYCL
</relatedIdentifier>

The OpenAIRE/oai_datacite export does not include this information.

The OpenAIRE/oai_datacite export should be changed to include related identifiers for files that Dataverse registers DOIs for, matching the behavior of the DataCite/Datacite export.

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

Start by comparing the OpenAIRE/oai_datacite export with the DataCite/Datacite export, then read issues #11916 and #12281 for the alignment context. The work is done when OpenAIRE/oai_datacite includes the same related identifiers for files with registered DOIs, including the shown HasPart/DOI example.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.