Question; should 10.5281/zenodo.7035342 work as an import, now or later or never?

[mietcls]

Steps to reproduce:

Add publication via DOI

Get error

[nics]

error:

import single publication: could not fetch publication	{"errors": "can't import publication: Resource not found.", "publication": "10.5281/zenodo.7035342", "user": "F72763F2-F0ED-11E1-A9DE-61C894A0A6B4"}

[nics]

@mietcls not findable through crossref, will have to be fixed later

[mietcls]

@nics Stefanie just provided this information, since this DOI is provided via Zenodo / DataCite.

CrossRef is a central organisation that handles publications only. When a publisher creates a DOI for a publication, he will do that through CrossRef (using the CrossRef metadata schema).

The Zenodo repository allows to deposit different outputs, not only data but also publications. However, Zenodo always uses DataCite as a central organisation for the creation of DOIs, also for publications. The metadata schema of DataCite is different from that of CrossRef. The resourceType in the DataCite metadata denotes whether it is a publication.

Currently, we have decided not to put a filter on resourceType in the Biblio dataset workflow, but the guidelines will state that publications are not in scope and the curators will take that check into account during curation. Publications on publisher's websites have most of the time undergone a peer review process while publications in Zenodo have not. The peer-reviewed journal articles are the focus of the publication policy and the reporting for the Open Science KPI (FRIS). We could in the future consider expanding the functionality of the Biblio publication workflow to cover the DOI-based import of these non-peer-reviewed publications from Zenodo for instance, but that would need discussion and investigation on whether it is worth it.

For now, they can be added manually if needed.

Edited in October, remarked again Wednesday 8 March 2023.

[nicolasfranck]

See #1138
See #1163

[mietcls]

Related #1185