I’m a man of modest dreams.
I’d like to see the Montreal Canadiens win another Stanley Cup as soon as possible, and for the Toronto Maple Leafs to never win one again. I’d like to enjoy good health and a happy life. And I’d like to see corrections evolve in new and useful ways as journalism continues its march online.
By those standards, it’s been a good week. Hockey season kicked off last night with the Habs beating the Leafs, and I had a phone conversation with a programmer at the Los Angeles Times that gives me hope for the future of corrections.
My conversation with Ben Welsh, a database producer at the Times, also helped me realize one of the barriers to innovation: corrections aren’t viewed the same way as articles, sports scores, or a breaking news ticker. They are perceived only as being part of the stories that spawned them, rather than content that can stand on its own.
I guess I’m saying: if you love corrections, set them free.
If we can change the way news organizations view corrections, then corrections can truly become integrated within the river of news we hear so much about.
Right now, I can sign up to receive e-mail alerts from The New York Times about just about any topic or personality that appears in their stories, but I can’t subscribe for correction alerts. For whatever reason, corrections aren’t seen as being important enough to warrant this kind of treatment. This is why we don’t have more RSS feeds for corrections, why many organizations still don’t have online corrections pages, and why there are so few correction-related tools for readers.
The good news is that, thanks to some work by Welsh, we have a small test case of what a corrections back-end could look like.
Earlier this year, Welsh was working on a mapping project for the Times’s special projects group. In the course of his work, he created some code that would enable the site to publish all of the updates and corrections made to the map. He called it “django-correx” to indicate that it was built for the Django Web application framework, and to indicate that it deals with corrections. This bit of code takes corrections and allows them to be customized and integrated as part of a Django-based Web site or application. It’s in effect saying: this is valuable information for readers, and here’s a way to manage it.
Django-correx allows a news organization to attach a correction, or update for that matter, to any object, whether it be a photo, news story, map, or other piece of content. Not only will a correction exist as part of the object it seeks to fix, but it can also exist as a stand-alone entity. As a result, you could publish a constantly updated corrections feed on a homepage, or slice and dice the corrections into customized content packages.
“You could have on your site a list of all the changes made, or create an RSS feed,” Welsh told me. “Or could have a list or feed of all the changes about photos or blog posts.”
I asked him if this framework could grant my wish of an article-specific corrections feed or sign-up feature, and he said yes. Django-correx took him a few hours to develop and a few more to improve. Now anyone can download the code to use and improve it.
Django-correx was never implemented by the Times (“I came up with technology to solve a problem, and then we decided we didn’t want to solve it anymore”), but Welsh has a very basic implementation of it on his personal Web site, Palewire. Just click on the red loop icon that’s positioned sixth from the left on the top menu bar and you’ll be brought to an automatically generated online corrections page. Click on the post listed there and you’ll see the highlighted correction appear at the top.