Data Citation Corpus documentation release 3.0
The Data Citation Corpus is a project by DataCite and Make Data Count funded by the Wellcome Trust, which has as focus the development of a comprehensive, centralized and publicly-available resource of data citations from a variety of sources.
Release 3.0
The third release of the Data Citation Corpus was delivered in February 2025. This follows the first release of the Data Citation Corpus in January 2024, and the second release in August 2024. The current release incorporates the following additions and improvements:
Additions
- 65,524 new data citations created in DataCite Event Data between August 2024 and December 2024
- 750 new data citations provided by the Aligning Science Across Parkinson’s (ASAP) initiative, identified through their Open Science Compliance Review process, which involves a partnership with DataSeer (described in Dumanis et al. and Cobb-Lewis et al.). Citations with provenance from ASAP are identified as “asap” in the source field.
Metadata enhancements
- Reconcile and normalize organization names for affiliations and funders in a subset of records with the Research Organization Registry (ROR)
- Add ror_name and ror_id subfields for affiliations and funders in JSON files. Unreconciled affiliation and funder strings are identified with values of null
- Add new columns affiliationsROR and fundersROR in CSV files. Unreconciled affiliation and funder strings are identified with values of NONE NONE (this is to ensure consistency in number and order of values in cases where some strings have been reconciled and others have not)
- Normalize DOI formats for articles and papers as full URLs
The current data file for the Data Citation Corpus consists of 5.3 million data citations and a dashboard for visualizing the contents of the data file.
Data citation records
Each data citation record is comprised of a pair of identifiers i.e. an identifier for the dataset (a DOI or an accession number) and the DOI of the publication object (journal article or preprint) in which the dataset is cited, and various metadata for the dataset and for the citing object.
{
“id”:”cdfe1599-7288-4fbd-b8d8-4a25fb6d170d”,
“created”:”2023-09-26T10:26:21.549Z”,
“updated”:”2023-11-15T23:17:25.755Z”,
“repository”:”European Nucleotide Archive”,
“publisher”:”F1000 Research Ltd”,
“journal”:”Wellcome Open Research”,
“title”:null,
“publication”:”10.12688/wellcomeopenres.17706.1″,
“dataset”:”OU744360.1″,
“publishedDate”:”2022-02-15T00:00:00.000Z”,
“source”:”czi”,
“subjects”:[],
“affiliations”:[],
“funders”:[]
}
Data file
he data file is available on Zenodo, in JSON and CSV formats: https://zenodo.org/records/11216814. The JSON file is the version of record.
Version 1.0 of the corpus data file was released in January 2024. Release v1.1 provided an optimized version of v1.0 designed to make the original citation records more usable, with no change to the citations included. Release 2.0 reflected the removal of citations that were not in scope, the inclusion of new data citations created in DataCite Event Data since the first release and inclusion of disciplinary information for citations for data with accession numbers. Release 3.0 incorporates the data citations contributed by ASAP, new citations in DataCite Event Data since the last release and addition of ROR information for affiliation and funder metadata.
Feedback on the data file can be submitted via Github. For general questions, email info@makedatacount.org.
Data Sources
The file includes three sources for data citations:
DataCite Event Data: Citations are determined based on the resource type and the relation type designated in the metadata for the dataset or the article (see DataCite documentation on contributing citations):
ResourceType= Dataset; relationType=IsReferencedBy/IsCitedBy/IsSupplementTo
ResourceType= Text; relationType= References/Cites/IsSupplementedBy
Event Data includes some citations originating from article metadata registered at Crossref, these may carry relation types different from the three listed above for DataCite metadata.
Chan Zuckerberg (CZI) Science Knowledge Graph: Mention to dataset identifier (accession number or DOI) identified in the text of an article by NER Model (SciBERT Model)
More information about open sourced algorithm is forthcoming.
Aligning Science Across Parkinson’s (ASAP): Mention to dataset identifier (accession number or DOI) identified in the text of an article by DataSeer through machine learning software, or via a manuscript’s Key Resource Table, and verified by a DataSeer and/or an ASAP curator.
The scope of the data file covers dataset-article pairs, i.e. it includes pairs where the citing object is a journal article or a preprint and the cited object is a dataset. DataCite Event Data includes records where the citing object involves a range of resource types (e.g. datasets, software), for the purposes of the data file of the Corpus, the only citations from DataCite Event Data included are those where the cited object is a dataset and the citing object is an article.
In addition to the identifier for the dataset and the citing object, each record includes metadata fields for the journal, publisher and publication date for the citing object (from Crossref metadata) and the repository where the dataset is hosted (via DataCite or EMBL-EBI). Where additional metadata fields are available (e.g. for affiliation, subject or other) this is included in the data citation record. Coverage of these additional metadata fields varies across citations.
Data Structure
Each data citation record includes the following fields:
| Field | Description | Required? |
| id | Internal identifier for the citation | Yes |
| created | Date of item’s incorporation into the corpus | Yes |
| updated | Date of item’s most recent update in corpus | Yes |
| repository | Repository where cited data is stored | No |
| publisher | Publisher for the article citing the data | No |
| journal | Journal for the article citing the data | No |
| title | Title of cited data | No |
| publication | DOI of article where data is cited | Yes |
| dataset | DOI or accession number of cited data | Yes |
| publishedDate | Date when citing article was published | No |
| source | Source where citation was harvested | Yes |
| subjects | Subject information for cited data | No |
| affiliations | Affiliation information for creator of cited data | No |
| funders | Funding information for cited data | No |
Dashboard
The dashboard at https://corpus.datacite.org/dashboard provides an overview of the content of the data file. This includes the six visualizations below with filtering options according to different facets (e.g. affiliation, repository, journal etc):
- Citation counts over time: Count of data citations spanning the time frame of currently available corpus data, from 2013 to 2024.
- Citation counts by publisher: Count of data citations by publisher.
- Counts of unique repositories, journals, subjects, affiliations, funders: Breakdown of the current coverage in the corpus for journals, affiliations, repositories and subjects.
- Citation counts by subject: Count of data citations per dataset subject, note this displays the distribution of records that contain this metadata field and is not representative of the full set of records in the data file.
- Citation counts by source of citation: Counts for citations ingested from DataCite Event Data, CZI Science Knowledge Graph, and ASAP.
- Data citations corpus growth: Citation counts and ingest date (into the corpus) by identifier type over time.
Existing Limitations & Planned Enhancements
The Data Citation Corpus brings together for the first time data citations associated with datasets with DOIs and accession number IDs. There are a few limitations and considerations that users should bear in mind when analyzing data in the current data file. We will continue our work to address these limitations in the course of future development of the Corpus.
Metadata coverage
As noted above, coverage of metadata fields varies across records. The current release incorporates subject information for a considerable number of the citations in the Corpus. We will work to add additional information to the existing data citations regarding affiliation details (ROR IDs and disambiguation of affiliation information) as well as funder details with ROR ID or Crossref Funder ID.
NER model output
The data citations contributed by Chan Zuckerberg Initiative were identified by a NER model – the methodology for this is outlined in the Appendix below. We have undertaken steps to minimize the number of false positives identified through the NER model by completing checks against the expected accession number structure for datasets coming from repositories with accession numbers. This resulted in the removal of 473,792 data citations previously included in the Corpus. We are confident this has increased the accuracy of data citations in the Corpus, but note to users the possibility of some additional false positives remaining in the data file.
Disciplinary coverage
The data citations identified via CZI’s NER model involved mining a set of articles indexed in Europe PMC, which has a biomedical scope. The accession numbers were associated with repositories also focused on life sciences disciplines. As a result, the data citations identified will be originating mostly from disciplines in the life sciences. The repositories included are well established in their fields and attract wide use in those disciplines, and so they provided a good starting point to identify citations to accession number IDs, but we will seek to extend the disciplinary coverage of the Data Citation Corpus as we ingest data citations from additional sources.
Appendix: CZI Science methodology
Full-text articles included
The set of articles employed for text mining involved 5.3 million articles, where the full text was available open access in Europe PMC.
Repositories mined
The list of repositories the NER model mined for are listed below, with a row entry for DOIs.
- List of terms mined for come from https://europepmc.org/pub/databases/pmc/TextMinedTerms/
- All but three repositories were linked through identifiers.org, those not linked are ebisc, gisaid, hipsci
- For the purposes of the data file, mentions to identifiers to eudract and nct were excluded as those are clinical trial registries. Per trial best practices, clinical trials are generally registered prior to the recruitment of patients, as a result, there is no guarantee that the clinical trial record will include a dataset from the trial.
| Repository name | Identifier prefix | Linking Methodology Where data is the extracted_word (or data mention) | Linked through identifiers.org Is the link an identifiers.org link? |
| ArrayExpress | arrayexpress | https://identifiers.org/arrayexpress:dataset | Y |
| BioModels | biomodels.db | https://identifiers.org/biomodels.db:dataset | Y |
| BioProject | bioproject | https://identifiers.org/bioproject:dataset | Y |
| biosample | https://identifiers.org/biosample:dataset | Y | |
| BioStudies | biostudies | https://identifiers.org/biostudies:dataset | Y |
| CATH | cath | https://identifiers.org/cath:dataset | Y |
| chebi | https://identifiers.org/chebi:dataset | Y | |
| ChEMBL | chembl | https://identifiers.org/chembl:dataset | Y |
| Complex Portal (CP) | complexportal | https://identifiers.org/complexportal:dataset | Y |
| NCBI dbGaP (DataBase of Genotypes And Phenotypes) | dbgap | https://identifiers.org/dbgap:dataset | Y |
| doi | https://dx.doi.org/:dataset | sometimes | |
| EBiSC Catalogue (European Bank for induced pluripotent Stem Cells catalogue) | ebisc | https://cells.ebisc.org/dataset | N |
| Experimental Factor Ontology | efo | https://identifiers.org/efo:dataset | Y |
| The European Genome-phenome Archive(EGA) | ega | https://identifiers.org/ega.dataset:dataset | Y |
| The Electron Microscopy Data Bank (EMDB) | emdb | https://identifiers.org/emdb:dataset | Y |
| Electron Microscopy Public Image Archive (EMPIAR) | empiar | https://identifiers.org/empiar:dataset | Y |
| Ensembl | ensembl | https://identifiers.org/ensembl:dataset | Y |
| EU Clinical Trial Register(EUCTR) | eudract | https://identifiers.org/euclinicaltrials:dataset | Y |
| Genome assembly database | gca | https://identifiers.org/insdc.gca:dataset | Y |
| European Nucleotide Archive | gen | https://identifiers.org/ena.embl:dataset | Y |
| Gene Expression Omnibus (GEO) | geo | https://identifiers.org/geo:dataset | Y |
| GISAID | gisaid | http://gisaid.org/EPI/dataset | N |
| Gene Ontology | go | https://identifiers.org/go:dataset | Y |
| HUGO Gene Nomenclature Committee | hgnc | https://identifiers.org/hgnc:dataset | Y |
| Human induced pluripotent stem cell initiative | hipsci | http://www.hipsci.org/lines/#/lines/dataset | N |
| The Human Protein Atlas | hpa | https://identifiers.org/hpa:dataset | Y |
| The International Genome Sample Resource | igsr | https://identifiers.org/coriell:dataset | Y |
| IntAct | intact | https://identifiers.org/intact:dataset | Y |
| InterPro | interpro | https://identifiers.org/interpro:dataset | Y |
| MetaboLights | metabolights | https://identifiers.org/metabolights:dataset | Y |
| MGnify | metagenomics | https://identifiers.org/mgnify.samp:dataset | Y |
| mint | https://identifiers.org/mint:dataset | Y | |
| ClinicalTrials.gov | nct | https://identifiers.org/clinicaltrials:dataset | Y |
| omim | https://identifiers.org/mim:dataset | Y | |
| Orphadata | orphadata | https://identifiers.org/orphanet:dataset | Y |
| The Protein Data Bank | pdb | https://identifiers.org/pdb:dataset | Y |
| Pfam Protein Families | pfam | https://identifiers.org/pfam:dataset | Y |
| PRIDE Proteomics Identification Database* | pxd | https://identifiers.org/pride:dataset | Y |
| Reactome | reactome | https://identifiers.org/reactome:dataset | Y |
| NCBI Reference Sequence Database | refseq | https://identifiers.org/refseq:dataset | Y |
| dbSNP Reference SNP | refsnp | https://identifiers.org/dbsnp:dataset | Y |
| Rfam | rfam | https://identifiers.org/rfam:dataset | Y |
| RNAcentral | rnacentral | https://identifiers.org/rnacentral:dataset | Y |
| Research Resource Identifiers | rrid | https://identifiers.org/rrid:dataset | Y |
| TreeFam | treefam | https://identifiers.org/treefam:dataset | Y |
| uniparc | https://identifiers.org/uniparc:dataset | Y | |
| UniProt | uniprot | https://identifiers.org/uniprot:dataset | Y |
*Listed as deactivated in identifiers.org as of 22 Mar 2024
DOIs
DOIs are particularly noisy as the model does not always distinguish between data and non-data DOIs. The primary reason being that there are many article-article citations in reference lists and the model could not easily distinguish this. In order to try and address this, we excluded reference lists from the text mining of articles, and completed an additional content negotiation step to verify that the DOI corresponds to a dataset. We intend to work with the community to better address this in future iterations.