Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deliver ROR ID to DataCite via Metadata Schema #43

Closed
yvgrossmann opened this issue Aug 3, 2022 · 2 comments
Closed

Deliver ROR ID to DataCite via Metadata Schema #43

yvgrossmann opened this issue Aug 3, 2022 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@yvgrossmann
Copy link

Current status: Currently, no ROR IDs of datasets are supplied to DataCite. Therefore, no datasets from Edmond currently appear in the DataCite Commons: https://commons.datacite.org/ror.org/01hhn8329?rorid=01hhn8329&resource-type=dataset.

Result: It would be desirable, however, that the ROR IDs of datasets are delivered to DataCite. Then Edmond datasets would also appear in the DataCite Commons.

@haarli haarli added the enhancement New feature or request label Aug 4, 2022
@haarli
Copy link
Member

haarli commented Aug 4, 2022

Currently, neither the 2nd or 3rd affilation, nor the ROR identifier of any affiliation is mapped to the DataCite schema or any other export, as this was a custom enhancement on Dataverse.
see e.g. here:
Dataset: https://edmond.mpdl.mpg.de/dataset.xhtml?persistentId=doi:10.17617/3.8w
Datacite Export: https://edmond.mpdl.mpg.de/api/datasets/export?exporter=Datacite&persistentId=doi:10.17617/3.8w

<creator>
<creatorName>Wei, David</creatorName>
<nameIdentifier schemeURI="https://orcid.org/" nameIdentifierScheme="ORCID">https://orcid.org/0000-0002-7849-9935</nameIdentifier>
<affiliation>Max Planck Institute of Quantum Optics</affiliation>
</creator>

The DataCite Metadata schema supports affiliation identifiers since version 4.3: https://blog.datacite.org/identify-your-affiliation-with-metadata-schema-4-3/

In the export example above, a mapping including 2nd affiliation and ROR IDs should look like this:

<creator>
<creatorName>Wei, David</creatorName>
<nameIdentifier schemeURI="https://orcid.org/" nameIdentifierScheme="ORCID">https://orcid.org/0000-0002-7849-9935</nameIdentifier>
<affiliation schemeURI="https://ror.org/" affiliationIdentifierScheme="ROR" affiliationIdentifier="https://ror.org/01vekys64">Max Planck Institute of Quantum Optics</affiliation>
<affiliation schemeURI="https://ror.org/" affiliationIdentifierScheme="ROR" affiliationIdentifier="https://ror.org/04xrcta15">Munich Center for Quantum Science and Technology</affiliation>
</creator>

Changes in the export code would require a re-export afterwards:
https://guides.dataverse.org/en/latest/admin/metadataexport.html

However, a reexport does not send updated metadata to DataCite. It is still unclear how this could be achieved within Dataverse

@haarli haarli self-assigned this Sep 1, 2022
@helkv
Copy link

helkv commented Nov 11, 2022

Testserver: qa-edmond2.mpdl.mpg.de
Browser: ff
Version: v5.12.1-mpdl-1 (3dce49c)
User: Admin
Result: OK

All author affiliations (with ROR IDs) of a Dataset are now included in the Datacite Export and are send to Datacite during publication. As mentioned in #43 (comment) this change only affects newly created Datasets (No update of existing published metadata).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants