IQSS / IQSS/dataverse

In DataCite/Datacite export, when the user adds a DAI author identifier, include in creator nameIdentifier property

Open
#12,296 7 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

When the user adds a DAI author identifier type, the DataCite/Datacite export should include the DAI author identifier in the creator nameIdentifier property, like the OpenAIRE/oai_datacite export does. Currently, the DataCite/Datacite export omits the DAI identifier entirely.

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, when the user adds a DAI author identifier type and a DAI identifier, the DataCite/Datacite export does not include the identifier in the nameIdentifier property.

The OpenAIRE/oai_datacite export does include it. For example:

<nameIdentifier
    nameIdentifierScheme="DAI">info:eu-repo/dai/nl/072728442
</nameIdentifier>

The DataCite/Datacite export should be changed to include the DAI identifier in the nameIdentifier property in the same way that the OpenAIRE/oai_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

Start at the DataCite/Datacite metadata export and compare its creator handling with the OpenAIRE/oai_datacite export, using issues #11916 and #12281 for alignment context. Verify the export for a creator with a DAI identifier and consider the change complete when it emits a creator nameIdentifier with nameIdentifierScheme="DAI" and the identifier value.

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
65/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.