Corrections Policy

How to report an error

Use the form on the Contact page (reason: "Correction request") with: which record or report, what's wrong, and — where possible — a source supporting the correction. For a dataset record, the event's id (visible in its detail view) makes it easy to locate.

Dataset corrections

events_portal_v1.jsonl is version-controlled in Git. A correction is applied as a normal, reviewed commit to that file — never a silent in-place edit outside of version control. Bulk corrections (e.g. a source revises many records at once) are batched and noted in the commit message rather than merged into unrelated changes.

We do not delete a record because it is contested — see Methodology on classification tiers. A record is corrected (wrong date, wrong casualty figure, wrong location) or, rarely, removed if it turns out not to describe a real event at all.

Report corrections

Published reports in /reports/ are Git-tracked files with a version field. A substantive correction bumps the version and is described in the report's history; the report is not silently rewritten. Minor corrections (typos, broken links) do not require a version bump.

Response time

This is a small, largely volunteer-run project. We aim to acknowledge correction requests within a few days, but do not currently commit to a fixed SLA. Safety- or defamation-relevant errors are prioritized.