Table 1
Overview of the different DataCite metadata fields included in the study.
| DATACITE METADATA FIELD | EXPLANATION |
|---|---|
| DOI (or other persistent identifier) | Persistent identifier that refers to the landing page containing the metadata of the dataset. If the data are open, download of the data is also available. |
| URL | URL that refers to the landing page containing the metadata of the dataset. If the data are open, download of the data is also available. |
| Publisher | The archiving organization/data repository that publishes the dataset. |
| Client ID | Unique identifier for a DataCite client. Since the publisher field sometimes contains different names for the same publisher, this Client ID seems useful to group together dataset records originating from the same archiving organization. |
| Publication year | The year when the data was or will be made publicly available. The DataCite documentation also specifies that, if there is no standard publication year value, the date that is preferred from a citation perspective should be used. |
| Description | Description of the dataset (free text), for example in the form of an abstract. |
| Name of data creators | First name and family name of the researchers who collected or created the data. |
| Identifier of data creators | ORCID that uniquely identifies each data creator. |
| Affiliation of data creators | Research institution to which each data creator contributing to the dataset is affiliated. |
| Identifiers of related output | Persistent identifiers that refer to research outputs related to the dataset in question. These outputs can be other datasets or associated publications (such as articles in journals). |
Table 2
Flemish universities and name variants.
| FLEMISH UNIVERSITY | SEARCH QUERY |
|---|---|
| Katholieke Universiteit Leuven | Katholieke AND Universiteit AND Leuven |
| KU AND Leuven | |
| KULeuven | |
| Catholic AND University AND Leuven | |
| https://ror.org/05f950310 | |
| Universiteit Antwerpen | Universiteit AND Antwerpen UAntwerpen University AND Antwerp |
| https://ror.org/008x57b05 | |
| Universiteit Gent | Universiteit AND Gent |
| UGent | |
| Ghent AND University AND NOT (Global AND Biodiversity AND Information AND Facility)4 | |
| https://ror.org/00cv9y106 | |
| Universiteit Hasselt | Universiteit AND Hasselt |
| UHasselt | |
| Hasselt AND University AND NOT (Global AND Biodiversity AND Information AND Facility) | |
| https://ror.org/04nbhqj75 | |
| Vrije Universiteit Brussel | Vrije AND Universiteit AND Brussel5 |
| https://ror.org/006e5kg04 |
Table 3
Number of datasets, per publication year (1989–2020).
| PUBLICATION YEAR | NUMBER OF DOIS |
|---|---|
| 1989 | 1 |
| 2002 | 1 |
| 2006 | 1 |
| 2007 | 15 |
| 2009 | 1 |
| 2011 | 2 |
| 2012 | 1 |
| 2013 | 3 |
| 2014 | 8 |
| 2015 | 16 |
| 2016 | 61 |
| 2017 | 31 |
| 2018 | 29 |
| 2019 | 40 |
| 2020 | 47 |
| Total | 257 |
Table 4
Number of DOIs, per archiving organization.
| ARCHIVING ORGANIZATION | NUMBER OF DOIS |
|---|---|
| delft.vliz (Marine Data Archive) | 72 |
| gdcc.harvard-dv (Harvard Dataverse) | 46 |
| cern.zenodo (Zenodo) | 40 |
| dans.archive (DANS - Data Archiving and Networked Services) | 26 |
| gbif.gbif (Global Biodiversity Information Facility)11 | 24 |
| delft.rbins (RBINS - Royal Belgian Institute for Natural Sciences, OD Nature - Directorate Natural Environment, BMDC - Belgian Marine Data Centre) | 10 |
| figshare.ars (Figshare) | 10 |
| pangaea.repository (PANGAEA - Data Publisher for Earth & Environmental Science) | 9 |
| bl.mendeley (Mendeley) | 7 |
| delft.data4tu (4TU.Centre for Research Data) | 3 |
| doe.lbnl | 2 |
| dryad.dryad (Dryad) | 2 |
| bl.oxdb (FAIRsharing) | 1 |
| europ.odin (European Commission JRC) | 1 |
| gesis.gesis (GESIS Data Archive) | 1 |
| gesis.icpsr (ICPSR - Interuniversity Consortium for Political and Social Research) | 1 |
| ieee.dataport (IEEE DataPort) | 1 |
| tib.ldeo (IEDA - Interdisciplinary Earth Data Alliance) | 1 |
| Total | 257 |
Figure 1
In which metadata fields do researchers encode affiliation information? An overview for the period 2006–2020.
Figure 2
Do researchers add their ORCID at the moment of data archiving? An overview for the period 2006–2020.
Figure 3
Overview of ORCID registration per archiving organization (operationalized as Client IDs).
Figure 4
Detection of related outputs for different archiving organizations.
Figure 5
Example dataset on the Harvard Dataverse portal.
Figure 6
Heatmap of data repositories.
Figure 7
Mosaic plot cross-tabulating archiving organizations with the third parameter about identifiers of related output.
Figure 8
Example dataset with associated publication on PANGAEA.
Figure 9
Example dataset with associated publication on Zenodo.