Correction loci — where the fixes land in the printed book
Every accepted correction to a Cologne dictionary's digital text is recorded as
a change-file line in
csl-corrections; its
correction_loci.tsv
feed resolves each record to the printed <pc> page it touches. This page
reads that feed as a spatial and editorial signal: where in each printed
edition the reported errors sit, and how actively maintained each
dictionary is — the editorial axes of the per-dictionary radar
(METALEXICOGRAPHY_ROADMAP §2.6/§3).
Read the process split first. 76% of all records are machine batches (the BOR digitization completion and the LRV markup-homogenization sweep), not human proofreading. Every view below separates
humanfrombulk; cross-dictionary maintenance comparisons should default to the human series.
The feed carries
correction records across dictionaries — human, bulk; are resolved to a printed page.
Editorial KPIs — corrections per 1,000 entries
Corrections per 1k current entries (<L> records in csl-orig v02), stacked by
process. This is the "how actively maintained" axis: BOR's enormous per-1k
value is its one-shot digitization completion batch, not ongoing editorial
attention — which is exactly why the human slice is drawn separately.
Editorial radar — the correction-fed axes
Five editorial axes per dictionary, each normalized to the maximum across the dictionaries currently shown (per-1k axes on a log scale, so BOR's batch spike does not flatten everyone else). These are the axes this feed contributes to the roadmap's per-dictionary radar; markup-density and citation axes stay on HOLD in the roadmap and are not drawn here.
Locus heatmap — normalized page position × dictionary
Each row is one dictionary's printed edition, left edge = page 1, right edge =
its last corrected page (see the trust block: the feed's own maximum, not
the true page count). Colour is corrections per position bin
(
One dictionary in detail — position × column
For dictionaries whose change files carry a regular column notation
(
Hottest pages — deep links into the source
The most-corrected printed pages per dictionary. Each row links into the source viewer at a sample corrected line, so a cell of the heatmap is one click from the actual dictionary text (headwords shown in IAST).
Batch cadence
Records per batch month, by process. Change files land in dated batches, so this is delivery cadence (when fixes were filed into csl-orig), not discovery dates.
Related correction-lane pages
- Correction front — month × component diachronic strip (OBS-T events; when/which layer).
- Lineage Sankey — shared-corrected-error overlay on the PWG/PW→MW edge (F4b apparatus-not-errors).
Maker QA — correction-pressure column
Prioritization signal for the H5 maker-QA worksheet: how much human correction
traffic has already touched the candidate lemma or its nearest-real neighbour
(form-keyed via slp1_norm). No new queue — one column on the existing H5
packet (docs/H5_MAKER_QA_CANDIDATES.md).
Bulk machine batches are excluded.
Chart Trust Block
- Claim: where reported-and-fixed errors sit in each printed edition, and how much accepted correction activity each dictionary has received per 1,000 entries, split machine-batch vs human.
- Evidence label:
derived— deterministic aggregation of the locus-resolved correction feed; no classification or model. - Source files:
csl-corrections/data/derived/correction_loci.tsv(records; parser build_correction_loci.pyowned by csl-corrections) +dict_entry_counts.tsv(csl-orig v02<L>counts, 2026-07-07); committed atlas packetsrc/data/corrections/correction_loci.jsonwith feed-commit provenance in its.source.jsonsidecar. - Generated by:
npm run build-correction-feed - Validation:
npm run validate-correction-feed— per-dict sums, heatmap cell sums vs pc-resolved counts, per-1k arithmetic, plus a full row-count cross-check against the sibling feed when the checkout is present. - Known false positives: hot pages read as reader attention, not print quality — corrections require a reader to pass by (C6 confound in the csl-corrections memo). BOR/LRV bulk batches are digitization completion / markup homogenization, not error findings.
- Known false negatives: the normalized position axis ends at each
dictionary's last corrected page, so never-corrected tail pages are
invisible; STC records carry no
<pc>headers at all; corrections merged before the change-file convention (2014) are absent. - Review status: machine-reviewed (deterministic validator; no human review of individual loci).
- Owner repo:
csl-atlas(rendering + aggregation); the feed itself is owned bycsl-corrections. - Next action: proofreading targets — sort the heatmap's cold bins of heavily-read dictionaries (MW mid-alphabet troughs) for the next human correction sweep; and when the observatory's component-labeled event feed is wired, add component mix + fix-latency as the two missing radar axes (roadmap §2.6).
- External dependencies:
csl-corrections(feed), csl-orig v02 (entry counts, via the feed's sidecar). - Boundary note: the atlas aggregates and renders; correction typology,
corrector stats, and trends stay with
csl-observatory's event data, and the change-file parser stays in csl-corrections.