[cross-posted from the PBS MediaShift Idea Lab]
A window of opportunity is open right now for online journalists to build accuracy and accountability into the publishing systems we use every day. To understand why this is such a big deal, first hop with me for a minute into the Wayback Machine.
It’s the mid-1990s. Journalists have just arrived on the web. They’re starting sites like Hotwired and Pathfinder, Salon and Slate. They’re doing good work, but also, inevitably, making mistakes. Their customary corrections routine — post a notice in the next edition or issue — makes no sense in the new medium, where stories are just files on servers or data in databases, and fixes can take effect instantly and invisibly.
Editors at the dawn of the web understood they had to be accountable for changes they made to published stories, and so improvised a routine for handling substantive corrections: Fix the problem; place a notice on the story page indicating that you’ve fixed it; and — this step was only taken by extra-conscientious organizations — add a notice to a separate page logging the fact of the correction (and linking to the corrected story).
>p>Fast-forward to the present. The web’s publishing environment is vastly more complex, flexible and elaborate. But when it comes to corrections, virtually every news site still handles things the way we did 15 years ago: Go into the story, often by hand (i.e., by adding to the body of the story text), fix the error, and append a correction notice to the story top or bottom. Then, if your site has a separate corrections-listing page, go into that by hand and add the notice there. Insert any cross-links. Republish the story and the corrections page. And you’re finally done.
The process is cumbersome, to be sure; it’s also not smart. Most publishing systems don’t actually “know” that the story has been corrected. There’s no data stored that distinguishes a corrected story from, say, one that’s been altered in some other way. The typical content-management system software package will track each successive edit or revision to a document, but it doesn’t distinguish garden-variety edits from formal corrections.
For years now, I’ve dreamed of a smarter publishing software tool that would handle corrections intelligently and seamlessly as part of the publishing cycle and editorial workflow, rather than as a clumsy kludge. One goal, certainly, is to make editors’ lives easier. If corrections can be handled with less fuss, maybe news sites will be less reluctant to make them.
But an even more important goal is to give journalists and the public better information about corrections. Once corrections are treated as data, developers can do things with them — say, allow readers to sign up to be notified of corrections for a site, individual story or story category; or create display boxes that automatically link to the half-dozen most recent corrected stories. The ultimate purpose of all this is for news organizations to demonstrate accountability and transparency to a public that views them with sparse and dwindling trust.
So when I read about the new Armstrong CMS project, I got excited. Armstrong is an effort by the software teams at the Bay Citizen and the Texas Tribune to build a new-model, open source publishing system for local news sites. It’s working off the highly regarded Django content-management framework, funded by a $975,000 grant from the Knight Foundation, and building on existing work already in use at the two sites.
The Armstrong project has a chance to create a new standard for corrections for the entire field of web journalism. I asked Brian Kelley, the Bay Citizen CTO who is a co-leader of the project, whether Armstrong had plans for corrections yet. He suggested that, because many organizations have different needs, Armstrong’s open plug-in and extension options might be the best way to handle the corrections process.
But there’s a bigger opportunity for the Armstrong community here: They can build a smart correction-handling process into the heart of the tool they’re creating. The best practices in this area are widely understood and agreed upon; why not bake them into the technology? No one, to my knowledge, has done this before in a free, open source publishing system. (If there are proprietary systems that do a better job, I’d love to hear about them.)
Here are the basic features I’d want any corrections tool to provide:
That’s it! None of this is particularly challenging as programming or design work. My experience is that when I describe what’s needed to most developers, they’re not interested — the problem’s too “trivial.” Maybe it is — but not to the editors I’ve talked to, who groan about the pain their software inflicts on them whenever they try to do a correction the right way.
Each time we rewrite the software used to publish news on the web we have another chance to raise the bar for the whole field. I’m crossing my fingers that Armstrong will be the project to make smart corrections a reality.