IQSS / IQSS/dataverse

Metadata export with ROR support

Open
#11,955 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Feature: Metadata Type: Bug
Dominant language
Java
Stars
1.1k
Forks
564
Avg merge
2d 2h
Merged PRs (30d)
29

Description

What steps does it take to reproduce the issue?
Using Dataverse External Vocabulary with Author Affilation ROR support https://github.com/gdcc/dataverse-external-vocab-support/blob/main/examples/authorIDandAffilationUsingORCIDandROR.md. ORCID & ROR support works fine, but when exporting oai_ddi metadata, the ROR identifier is displayed instead of the name:
<AuthEnty affiliation="https://ror.org/03prydq77">Bischof, Christian</AuthEnty>

All other XML exports deliver the same result (if affilation is exported), with the exception of datacite (but this export follows a other structure):
<affiliation affiliationIdentifier="https://ror.org/03prydq77" schemeURI="https://ror.org" affiliationIdentifierScheme="ROR">University of Vienna</affiliation>

The ROR name should be exported, not the ROR identifier. Correct export is necessary to harvest a Dataverse server.

Example:
https://demo.dataverse.org/api/datasets/export?exporter=oai_ddi&persistentId=doi%3A10.70122/FK2/EEAP40
https://demo.dataverse.org/api/datasets/export?exporter=Datacite&persistentId=doi%3A10.70122/FK2/EEAP40

Which version of Dataverse are you using?
v6.8

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 with the API export examples for exporter=oai_ddi and exporter=Datacite, and compare their affiliation handling with the external-vocabulary example. Done means the ROR name is emitted instead of the ROR identifier in oai_ddi and the other affected XML exports, while Datacite retains its existing structure.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
api, backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.