Corrections — The Stare
Corrections
We get things wrong sometimes. When we do, we fix it in the open — and this page is the open.
The policy
- Substantive errors get corrected visibly. A dated correction line goes at the top of the corrected article saying what was wrong and what changed — we don't quietly rewrite history. The correction is also logged in the archive below, permanently.
- Typos and formatting slips we just fix, without ceremony. If a fix changes the meaning of a sentence, it's not a typo — it's a correction, and it's handled as one.
- Anyone can flag an error. Email corrections@kcstare.com. A real person reads it, checks it against the sourcing, and answers. You don't need to be the subject of the story.
- The Wire links out — headlines in the feed belong to the newsrooms that reported them. If a linked headline is wrong, that's the original publisher's to correct; if our excerpt or framing introduced an error, that's ours, and we'll correct it here.
The archive
-
How to look up code violations on a property in Kansas City
Wrong: The guide said the open-data portal's own search box was case-sensitive and would return an empty result for an address typed in capitals.
Corrected: The search box ignores capitalization and returns the same 2,015 rows for Prospect, PROSPECT and prospect. The case-sensitivity belongs to the street_address column filter, which returned 2,013 rows for Prospect and zero for PROSPECT. The guide now says which search is which.