cometadata/crossref-datacite-citations

Crossref DataCite Citations

A dataset of DataCite-registered works and the Crossref-registered works that cite them, extracted from Crossref reference metadata and confirmed against the DataCite monthly data file.

Dataset Description

Each record in the citation configurations is one DataCite DOI together with every confirmed citing work found in Crossref reference metadata. A reference is confirmed when it carries a DOI registered in DataCite or an arXiv identifier whose arXiv DOI is registered in DataCite. Registered landing-page URLs are evaluated against release metadata before an exact decision joins citations.

Built from the Crossref Metadata Plus monthly snapshot 2026-07 and the DataCite monthly data file 2026-07 with crossref-citation-extraction version 2.2.0.

Provenance and Ambiguity Policy

• —publisher and crossref matches come from references whose structured DOI field holds the cited DOI with a doi-asserted-by value of publisher or crossref. Every other match is mined: a DOI, arXiv identifier, or registered landing-page URL found in the reference's DOI (without that assertion), URL, article-title, journal-title, or unstructured field.
• —A landing-page URL registered by more than one DataCite record never produces a citation. Such references are published separately in the ambiguous_urls configuration with every candidate DOI and are excluded from every citation count.
• —Counts are recomputed per configuration: a citing work appears in a configuration only with its matches of that configuration's provenances.

Dataset Configurations

The ambiguous_urls configuration holds 2,631 unresolved URL references. It is evidence for downstream resolution, not citations, and it is excluded from the counts above. The url_evidence configuration records all URL decisions. Status totals are exact 38,508, related 396, uncertain 34,163, and rejected 282.

Build Identity

The manifest lists every published file with its size and SHA-256 digest; the SHA-256 of the manifest bytes identifies this publication.

Loading the Dataset

from datasets import load_dataset

dataset = load_dataset("cometadata/crossref-datacite-citations")
asserted = load_dataset("cometadata/crossref-datacite-citations", "asserted")
mined = load_dataset("cometadata/crossref-datacite-citations", "mined")
ambiguous = load_dataset("cometadata/crossref-datacite-citations", "ambiguous_urls")
url_evidence = load_dataset("cometadata/crossref-datacite-citations", "url_evidence")

Data Schema

Citation Configurations (all, asserted, mined)

Each record contains:

Each citing work object in cited_by contains:

Each match contains:

ambiguous_urls

url_evidence

Every row records a unique URL candidate and its semantic decision from selected DataCite metadata. A unique registered URL creates a candidate; it does not confirm a citation. Only exact decisions enter citation configurations.

Candidate fields:

Decision fields:

exact identifies the same object, version, and granularity as target_doi. related identifies a different but related object, version, or granularity. uncertain has insufficient semantic evidence. rejected conflicts with the target or an exclusion rule. The manifest binds the four status totals to this ledger separately from citation counts and ambiguous_urls totals.

Provenance Values

• —publisher - the reference's structured DOI field holds the DataCite DOI with doi-asserted-by: publisher
• —crossref - the reference's structured DOI field holds the DataCite DOI with doi-asserted-by: crossref
• —mined - any other match: a DOI, arXiv identifier, or registered landing-page URL found in the reference's DOI, URL, article-title, journal-title, or unstructured field (a structured DOI counts as mined unless doi-asserted-by is publisher or crossref)

The asserted config contains only publisher and crossref matches; the mined config contains only mined matches.

Extraction Process

References in the Crossref snapshot are scanned for DOIs, arXiv identifiers, and landing-page URLs. Each candidate is normalized and looked up in an index built from the DataCite monthly data file 2026-07: DOIs must be registered in DataCite, arXiv identifiers must map to a registered arXiv DOI, and uniquely registered landing-page URLs create candidates. Candidate URLs are semantically validated against selected release metadata, and only exact decisions enter citation configurations. URLs registered by several records are recorded as ambiguous evidence instead.

Data Sources

• —Crossref Metadata Plus monthly snapshot 2026-07
• —DataCite monthly data file 2026-07
• —Extraction tools: cometadata/crossref-arxiv-citation-extraction

Limitations

• —Only citations registered in Crossref reference metadata are included.
• —Only DOIs and landing-page URLs registered in DataCite are matched; works registered with other agencies are not represented.
• —Landing-page matching uses the URLs registered in the DataCite release 2026-07; earlier or historical URLs of a record are not matched.
• —Registered landing pages on DOI resolver hosts (doi.org, dx.doi.org, www.doi.org), bare site roots, and hosts without a dot are ignored for URL matching, so records registered with such a URL are matched only by DOI.
• —The dataset reflects one Crossref snapshot and one DataCite release; each publication replaces the previous contents rather than accumulating them.
• —References whose URL is registered by several DataCite records appear only in ambiguous_urls and are never counted as citations.
• —Reference parsing depends on successful identifier extraction from reference metadata; the mined subset may contain lower-quality matches from noisy reference text.

License

This dataset is released under CC0 1.0 Universal.

Citation

@dataset{crossref_datacite_citations,
  title = {Crossref DataCite Citations},
  author = {Cometadata},
  publisher = {Hugging Face},
  url = {https://huggingface.co/datasets/cometadata/crossref-datacite-citations}
}