In DataCite/Datacite export, when user chooses cstr and URL from Related Publication Identifier Type dropdown, add cstr and URL to related identifiers
Nobody has claimed this yet.
- 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 Related Publication and chooses cstr or URL from the Related Publication Identifier Type dropdown, the DataCite/Datacite export should include the related identifiers, as the OpenAIRE/oai_datacite export already does. Currently, the DataCite/Datacite export does not include the related identifiers in these cases.
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 in the closed issue 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 chooses cstr or URL from the Related Publication Identifier Type dropdown, the DataCite/Datacite export does not include the related identifier. See https://github.com/IQSS/dataverse/issues/11089 for more context.
The OpenAIRE/oai_datacite export does include the related identifier in these cases. For example:
<relatedIdentifier
relationType="IsCitedBy"
relatedIdentifierType="cstr">CSTR:16666.11.nbsdc.J0V2mNIU
</relatedIdentifier>
<relatedIdentifier
relationType="IsCitedBy"
relatedIdentifierType="URL">https://url.org
</relatedIdentifier>
The DataCite/Datacite export should be changed to include related identifiers when the user chooses cstr or URL as the identifier type, matching the behavior of the OpenAIRE/oai_datacite export.
Any open or closed issues related to this feature request?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Compare the DataCite/Datacite export with the OpenAIRE/oai_datacite export, focusing on related publication identifiers with types cstr and URL. Reproduce both cases and confirm that the DataCite XML includes relatedIdentifier elements with the selected type, relation type, and value.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 62/100