<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Regret the Error &#187; Behind the scenes</title>
	<atom:link href="http://www.regrettheerror.com/category/behind-the-scenes/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.regrettheerror.com</link>
	<description>Mistakes Happen</description>
	<lastBuildDate>Mon, 19 Dec 2011 12:25:27 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Worth Reading: Two views on debunking lies and misinformation*</title>
		<link>http://www.regrettheerror.com/2011/12/01/worth-reading-two-views-on-debunkng-lies-and-misinformation/</link>
		<comments>http://www.regrettheerror.com/2011/12/01/worth-reading-two-views-on-debunkng-lies-and-misinformation/#comments</comments>
		<pubDate>Thu, 01 Dec 2011 12:30:10 +0000</pubDate>
		<dc:creator>Craig Silverman</dc:creator>
				<category><![CDATA[Behind the scenes]]></category>
		<category><![CDATA[Regret Articles]]></category>
		<category><![CDATA[fact checking]]></category>
		<category><![CDATA[regret corrections]]></category>

		<guid isPermaLink="false">http://www.regrettheerror.com/?p=14750</guid>
		<description><![CDATA[I came across two notable articles that both offer guidance on how journalists should handle (and debunk) misinformation provided by sources. Both cited a recent ad from the Mitt Romney campaign that included a falsehood. So, as the story from Nieman Watchdog Project asks, &#8220;When candidates lie, what&#8217;s a political reporter to do?&#8221; From Dan [...]]]></description>
			<content:encoded><![CDATA[<p>I came across two notable articles that both offer guidance on how journalists should handle (and debunk) misinformation provided by sources. Both cited a <a href="http://www.politifact.com/truth-o-meter/statements/2011/nov/22/mitt-romney/mitt-romney-says-obama-said-if-we-keep-talking-abo/">recent ad from the Mitt Romney campaign</a> that included a falsehood. So, as the <a href="http://www.niemanwatchdog.org/index.cfm?fuseaction=background.view&#038;backgroundid=00592">story from Nieman Watchdog Project</a> asks, &#8220;When candidates lie, what&#8217;s a political reporter to do?&#8221;</p>
<p>From Dan Froomkin&#8217;s piece at Nieman:</p>
<blockquote><p><em>Experts in journalistic ethics are encouraging reporters to take a more critical posture going forward.</p>
<p>&#8220;I think professional journalists have an absolute obligation to make lies transparent,&#8221; said Kelly McBride, who teaches ethics at the Poynter Institute.</p>
<p>The first step is &#8220;to do the reporting so that you can with authority point out that this is an act of deception,&#8221; McBride said. With the Romney ad, that was easy; the accompanying press release provided Obama&#8217;s full quote.</p>
<p>Step two, McBride said, is to assign blame.</p>
<p>&#8220;Professional journalists need to follow up and figure out who in the campaign is responsible for this,&#8221; McBride said &#8212; &#8220;and keep at it.&#8221;</p>
<p>&#8220;We have to call that sort of thing out,&#8221; Geneva Overholser, director of USC Annenberg&#8217;s School of Journalism and a former Washington Post ombudsman, wrote in an e-mail. &#8220;Journalists did that, last week, but it seems to me it needs to have been even stronger. This was such a blatant act of deception. Treating it just like any other fact-checked ad, so many of which contain something mildly misleading, is itself misleading.&#8221;</em></p></blockquote>
<p>I encourage you to <a href="http://www.niemanwatchdog.org/index.cfm?fuseaction=background.view&#038;backgroundid=00592">read the whole thing</a>. </p>
<p>The second piece is a post <a href="http://www.cjr.org/campaign_desk/fact-checking_versus_strategy.php?page=all">by Brendan Nyhan at Columbia Journalism Review</a>. (Disclosure: I&#8217;m a columnist for CJR.) Nyhan, an assistant professor at Dartmouth College, is doing some of the most interesting academic research into misinformation, and he&#8217;s now writing regularly for CJR. He looked at how some publications dealt with the Romney ad. Then he offered some advice on the best way to combat the misinformation:</p>
<blockquote><p><em>&#8230; A better approach would be for reporters to characterize the accuracy of ads in their own voice and to invoke non-partisan experts like PolitiFact. In some cases, it may even be possible to find credible sources on the side of the candidate airing the misleading ad who are willing to state the truth. For instance, WMUR’s Sexton briefly paraphrases a GOP strategist conceding that Romney’s ad is misleading: “Republican political strategist Mike Dennehy says it definitely appears as though Obama’s words are taken out of context.” This approach might be especially persuasive to Republicans who are inclined to trust Romney and distrust the mainstream press.</p>
<p>Still, it’s important to be realistic about the effectiveness of this sort of fact-checking. My co-author <a href="http://jasonreifler.com/">Jason Reifler</a> and I have shown in <a href="http://www.dartmouth.edu/~nyhan/nyhan-reifler.pdf">our research</a> (PDF) that fact-checking frequently fails to reduce misperceptions among the ideological group that is most likely to hold the misperception and in some cases makes the problem worse (what we call a “backfire effect”). In this case, reporters should not expect to convince skeptical readers that ads they support are false.</p>
<p>Nonetheless, aggressive fact-checking can <a href="http://www.dartmouth.edu/~nyhan/health-care-misinformation.pdf">provide reputational incentives</a> (PDF) for elites to make more careful claims. </em></p></blockquote>
<p>Earlier this year I wrote a CJR <a href="http://www.cjr.org/behind_the_news/the_backfire_effect.php?page=all">column about the backfire effect</a>, and how it presents a challenge for journalists:</p>
<blockquote><p><em>We present facts and evidence, and it often does nothing to change people’s minds. In fact, it can make people dig in even more. Humans also engage in motivated reasoning, a tendency to let emotions <a href="http://blogs.discovermagazine.com/intersection/2011/04/18/the-science-of-why-we-deny-science-motivated-reasoning/">“set us on a course of thinking that’s highly biased, especially on topics we care a great deal about”.</a></p>
<p>These two important cognitive effects can have a significant impact on society and debates in the public sphere. They also end up negating some of the debunking and reporting work done by the press.</em></p></blockquote>
<p><strong>*Correction December 2, 2011:</strong> The original headline on this piece misspelled debunking as &#8220;debunkng&#8221;. The first sentence also used the Canadian spelling of &#8220;across&#8221;. I use US spelling on this site, so I corrected that as well. I regret the errors, and thank rogerogreen for <a href="http://www.regrettheerror.com/2011/12/01/worth-reading-two-views-on-debunkng-lies-and-misinformation/#comment-377521126">spotting both</a>!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.regrettheerror.com/2011/12/01/worth-reading-two-views-on-debunkng-lies-and-misinformation/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>A case study in unpublishing, apologizing and correcting via social media</title>
		<link>http://www.regrettheerror.com/2011/11/25/a-case-study-in-unpublishing-apologizing-and-correcting-via-social-media/</link>
		<comments>http://www.regrettheerror.com/2011/11/25/a-case-study-in-unpublishing-apologizing-and-correcting-via-social-media/#comments</comments>
		<pubDate>Fri, 25 Nov 2011 15:37:39 +0000</pubDate>
		<dc:creator>Craig Silverman</dc:creator>
				<category><![CDATA[Behind the scenes]]></category>
		<category><![CDATA[Major Errors]]></category>
		<category><![CDATA[Regret Articles]]></category>
		<category><![CDATA[apologies]]></category>
		<category><![CDATA[openfile]]></category>
		<category><![CDATA[unpubpishing]]></category>

		<guid isPermaLink="false">http://www.regrettheerror.com/?p=14718</guid>
		<description><![CDATA[My main job at the moment is as editorial director of OpenFile, an online news organization operating in six Canadian cities. Late yesterday afternoon, I spent about an hour helping draft a blog post that would offer an apology and explanation for readers about why we had to remove a story just a few minutes [...]]]></description>
			<content:encoded><![CDATA[<p><img src="http://www.regrettheerror.com/wp-content/uploads/2011/11/Screen-shot-2011-11-25-at-10.35.19-AM-150x40.png" alt="" title="openfile" width="150" height="40" class="alignnone size-thumbnail wp-image-14722" />My main job at the moment is as editorial director of <a href="http://openfile.ca">OpenFile</a>, an online news organization operating in six Canadian cities. Late yesterday afternoon, I spent about an hour helping draft a blog post that would offer an apology and explanation for readers about why we had to remove a story just a few minutes after it was published. </p>
<p>This offers an opportunity for me to explain how we handled the situation. I&#8217;m not saying we did it perfectly. I&#8217;d be eager to hear comments from readers about anything we may have overlooked or handled poorly.</p>
<p>As a starting point, here&#8217;s <a href="http://halifax.openfile.ca/blog/curator-blog/explainer/2011/explanation-and-apology-we-removed-story-about-jericho-upshaw">the text of the apology that was published</a>:</p>
<blockquote><p><em>Around 2:45 p.m. today, we published a story about Jericho Upshaw, a Halifax man charged with first-degree murder, and his association with the North End.</p>
<p>It relied on two sources who said they had encountered him in the neighbourhood on several occasions. Unfortunately, the story was wrong: we had the wrong Jericho. The details in the story were about another young man with the same first name. Our two sources had seen Upshaw’s photo in a local paper and identified him as the man they had encountered in the North End. They were mistaken, and we were wrong in publishing the story.</p>
<p>Within about five minutes of posting the story online and sending out a tweet about it, we realized we had the wrong Jericho. We removed the story from our site and deleted the related tweet.</p>
<p>Our practice is to not unpublish content. We don’t want to erase the record; we prefer to correct it.</p>
<p>But in this case, the story was based on a mistaken identification by two sources. It was built on the information from those two sources. As a result, we felt it was essential to remove the story and publish this explanation of what went wrong. We also redirected the URL from the mistaken story to this blog post in order to ensure that anyone who finds that piece of content will understand why it was removed.</p>
<p>On behalf of OpenFile Halifax, I apologize for this error and will do everything I can to make sure something like this doesn’t happen again.</p>
<p>Neal Ozano<br />
Editor, OpenFile Halifax</em></p></blockquote>
<p>This is the kind of situation we journalists dread.</p>
<p>&#8220;My heart sank,&#8221; said OpenFile editor in chief Kathy Vey in an email to me today. &#8220;Neal had asked me to look over the story for legal issues, because it was a murder case. There weren&#8217;t any but we had a much more basic problem. We named the wrong guy.&#8221;</p>
<p>The story was based on totally incorrect information. It shouldn&#8217;t have been published. So what do you do now that you know that? I hate unpublishing content; it should only be done in very specific circumstances. In my view, this was one of them.</p>
<p>The story itself was completely incorrect. Once we knew we had the wrong person, there was nothing left in the piece that offered value to readers. So it had to come down — and we had to replace it with something as soon as possible. </p>
<p>I worked with Halifax editor Neal Ozano and editor in chief Kathy Vey to draft the apology. We also contacted our tech team to alert them that we would need to redirect the URL of the unpublished story to the new blog post. That way, anyone who found their way to the offending story would be given an explanation of what what happened, of why the story was gone. Sending people to an error page is not acceptable. You have to make it easy for them to understand what happened.</p>
<p>The apology itself also needed to be clear about what the mistake was, how it occurred and what action we took once we realized our error. Again: help people understand what went wrong. Be clear. We also had to be honest about the fact that it was a failure on our part. You can&#8217;t just blame your sources. It was published on our site. We needed to accept responsibility and offer a clear apology.</p>
<p>A final consideration was the fact that our OpenFile Halifax Twitter account tweeted a link to the story. So as soon as the post was live and URL redirect was working, we <a href="https://twitter.com/#!/jm_mcgrath/statuses/139818947779366912">tweeted the link</a> to the apology from the same local Twitter account. That was then retweeted by <a href="https://twitter.com/#!/CraigSilverman/statuses/139817168836624384">me</a>, <a href="https://twitter.com/#!/kvey">Kathy Vey</a> and by our <a href="https://twitter.com/#!/Open_File/statuses/139818720238374912">national OpenFile Twitter account</a>. Our Toronto news curator also <a href="http://twitter.com/jm_mcgrath/statuses/139818947779366912">retweeted</a> it of his own accord. We wanted to make sure Twitter followers had a chance to see the apology.</p>
<p>As of today, the apology is still on the homepage of our <a href="http://halifax.openfile.ca">Halifax site</a>. (It will probably scroll off by the end of day.)</p>
<p>Now the job is to make sure this doesn&#8217;t happen again. We cover local news in our cities, but we don&#8217;t do a lot of crime reporting. So the story was a bit out of our comfort zone and area of expertise. We will be extra cautious with any stories of this nature in the future. We&#8217;ll also ask ourselves whether what we have is really news. We will add extra eyes to contentious stories.</p>
<p>What else should we do? What could we have done better? I&#8217;d love to hear your thoughts.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.regrettheerror.com/2011/11/25/a-case-study-in-unpublishing-apologizing-and-correcting-via-social-media/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Canadian Association of Journalists releases &#8216;Best practices in digital accuracy and corrections&#8217;</title>
		<link>http://www.regrettheerror.com/2011/11/17/canadian-association-of-journalists-releases-best-practices-in-digital-accuracy-and-corrections/</link>
		<comments>http://www.regrettheerror.com/2011/11/17/canadian-association-of-journalists-releases-best-practices-in-digital-accuracy-and-corrections/#comments</comments>
		<pubDate>Thu, 17 Nov 2011 13:00:02 +0000</pubDate>
		<dc:creator>Craig Silverman</dc:creator>
				<category><![CDATA[Behind the scenes]]></category>
		<category><![CDATA[Regret Articles]]></category>
		<category><![CDATA[correction policy]]></category>
		<category><![CDATA[Online Corrections]]></category>

		<guid isPermaLink="false">http://www.regrettheerror.com/?p=14654</guid>
		<description><![CDATA[When should a news organization correct or remove archival content? Where should online corrections be placed? How should readers be encouraged to report mistakes and request corrections? These are some of the common questions I&#8217;m asked about online corrections. I think a lot of news organizations continue to struggle with them, and to look for [...]]]></description>
			<content:encoded><![CDATA[<p>When should a news organization correct or remove archival content? Where should online corrections be placed? How should readers be encouraged to report mistakes and request corrections?</p>
<p>These are some of the common questions I&#8217;m asked about online corrections. I think a lot of news organizations continue to struggle with them, and to look for guidance. I&#8217;m pleased to say that thanks to the <a href="http://www.caj.ca/">Canadian Association of Journalists</a>, we have the best and most comprehensive guide to help answer these and other important questions about online corrections. </p>
<p>Yesterday the CAJ released <a href="http://j-source.ca/article/best-practices-digital-accuracy-and-corrections">&#8220;Best practices in digital accuracy and corrections&#8221;</a>, a set of useful best practices to help newsrooms make sense of online corrections. It&#8217;s the result of hard work by a panel created by the <a href="http://www.caj.ca/?cat=9">Ethics Advisory Committee</a> of the CAJ. I serve on the Committee and also served on the panel, though I&#8217;ll note I was added after the group had already done some great work. </p>
<p>I hope journalists the world over will <a href="http://j-source.ca/article/best-practices-digital-accuracy-and-corrections">read the document</a> and use it as a basis for developing policies and practices. If you have feedback, I&#8217;d love to hear.</p>
<p>I wrote an accompanying article to go with the best practices document. Read it <a href="http://j-source.ca/article/where%E2%80%99s-page-two-online">here</a>. An excerpt:</p>
<blockquote><p><em>For several decades, newspaper readers in the U.S. and Canada have found the day’s corrections tucked away on page two of their paper of choice. This placement became a de facto standard after the New York Times began the practice in 1972. Newsrooms followed the Times’ lead.</p>
<p>Today, in 2011, we have yet to see a similar moment that standardizes the placement, wording and handling of online corrections. There are a myriad of questions when it comes to correcting online content, and news organization continue to struggle with best practices. At the same time, online errors spread father and faster than ever before. They speed across social networks and are deposited into search engine caches and databases large and small.</p>
<p>It’s essential that news organizations establish best practices for online corrections and digital accuracy. That’s why the Canadian Association of Journalists asked its Ethics Advisory Committee to create a panel to do so. The panel was chaired by Toronto Star public editor Kathy English and included Bert Bruser, Tim Currie, Rod Link, Shauna Snow-Capparelli, Scott White and myself.</p>
<p>The result of our work, “Best practices in digital accuracy and correction,” was publicly released this week. I encourage all journalists to download and read the document.</p>
<p>In addition to a set of clear and actionable best practices, the report provides useful (and interesting!) background on the challenges of online accuracy and corrections, and a look at what leading news organizations are doing. It offers much needed clarity for newsrooms when it comes to online accuracy and corrections &#8230;</em></p></blockquote>
]]></content:encoded>
			<wfw:commentRss>http://www.regrettheerror.com/2011/11/17/canadian-association-of-journalists-releases-best-practices-in-digital-accuracy-and-corrections/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Readers notice errors and can tell if a story has been edited, according to research</title>
		<link>http://www.regrettheerror.com/2011/11/06/readers-notice-errors-and-can-tell-if-a-story-has-been-edited-according-to-research/</link>
		<comments>http://www.regrettheerror.com/2011/11/06/readers-notice-errors-and-can-tell-if-a-story-has-been-edited-according-to-research/#comments</comments>
		<pubDate>Mon, 07 Nov 2011 02:46:29 +0000</pubDate>
		<dc:creator>Craig Silverman</dc:creator>
				<category><![CDATA[Behind the scenes]]></category>
		<category><![CDATA[Newspapers]]></category>
		<category><![CDATA[copy editing]]></category>
		<category><![CDATA[los angeles times]]></category>
		<category><![CDATA[quality control]]></category>

		<guid isPermaLink="false">http://www.regrettheerror.com/?p=14580</guid>
		<description><![CDATA[The Los Angeles Times has been hearing complaints from readers about typos and grammatical errors. The feedback was mentioned in this piece. Just about every newspaper these days gets complaints of that nature, and it&#8217;s good that readers speak up. But what&#8217;s notable about the Times story is the information offered up in response by [...]]]></description>
			<content:encoded><![CDATA[<p>The Los Angeles Times has been hearing complaints from readers about typos and grammatical errors. The feedback was <a href="http://www.latimes.com/news/opinion/letters/la-le-postscript-typos-20111105%2C0%2C5440830.story">mentioned in this piece</a>. Just about every newspaper these days gets complaints of that nature, and it&#8217;s good that readers speak up. </p>
<p>But what&#8217;s notable about the Times story is the information offered up in response by readers&#8217; representative Deirdre Edgar:<br />
<em><br />
<blockquote>When readers write in about errors, it shows they care, and that&#8217;s a good thing. Research done for the American Copy Editors Society this spring confirmed what the Readers&#8217; Rep inbox tells us.</p>
<p>Fred Vultee, a journalism professor at Wayne State University, studied a group of readers over a three-month period. His findings:</p>
<ul>
<li>Readers who read more news tend to be more critical than people who read less.
</li>
<li>Dedicated readers expect a higher level of quality than casual readers, particularly in terms of grammar and professionalism.</li>
<li>Readers notice grammar errors and find them troubling and distracting.
</li>
<li>Readers notice writing that is garbled and confusing, and when words are misspelled or misused.</li>
</ul>
<p>Most readers are less concerned about errors of style and story structure than they are about professionalism and grammar. &#8220;They really don&#8217;t care if you abbreviate &#8216;road,&#8217; Vultee said. &#8220;They don&#8217;t care if you start a paragraph with a number.&#8221;</p></blockquote>
<p></em></p>
<p>I hadn&#8217;t heard about Vultee&#8217;s work, and there&#8217;s a <a href="http://www.copydesk.org/211/aces-sponsored-research-study-says-yes/">summary of it here</a>. There&#8217;s one other key finding that&#8217;s worth noting:<br />
<em><br />
<blockquote>Readers can tell edited from unedited stories in significant ways.
</p></blockquote>
<p></em></p>
<p>That&#8217;s an interesting finding. I hope to learn more from Vultee about some of the differences noted by readers.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.regrettheerror.com/2011/11/06/readers-notice-errors-and-can-tell-if-a-story-has-been-edited-according-to-research/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Daily Mail gets favourable ruling from PCC regarding corrections</title>
		<link>http://www.regrettheerror.com/2011/11/01/daily-mail-gets-favourable-ruling-from-pcc-regarding-corrections/</link>
		<comments>http://www.regrettheerror.com/2011/11/01/daily-mail-gets-favourable-ruling-from-pcc-regarding-corrections/#comments</comments>
		<pubDate>Tue, 01 Nov 2011 12:00:20 +0000</pubDate>
		<dc:creator>Craig Silverman</dc:creator>
				<category><![CDATA[Behind the scenes]]></category>
		<category><![CDATA[Newspapers]]></category>
		<category><![CDATA[daily mail uk]]></category>
		<category><![CDATA[press complaints commission]]></category>

		<guid isPermaLink="false">http://www.regrettheerror.com/?p=14507</guid>
		<description><![CDATA[I recently blogged the fact that the Daily Mail, a paper that has long distinguished itself by issuing remarkable apologies for highly questionable reporting, decided to introduce a regular corrections column. We&#8217;re a couple of weeks into it and, as expected, there have been some gems. It&#8217;s a positive move for the paper to standardize [...]]]></description>
			<content:encoded><![CDATA[<p><img src="http://www.regrettheerror.com/wp-content/uploads/2009/09/dailymail-150x28.jpg" alt="" title="dailymail" width="150" height="28" class="alignnone size-thumbnail wp-image-9110" />I <a href="http://www.regrettheerror.com/2011/10/17/daily-mail-debuts-a-corrections-column/">recently blogged</a> the fact that the Daily Mail, a paper that has long distinguished itself by issuing <a href="http://www.regrettheerror.com/2011/08/29/daily-mail-has-a-run-of-bad-correctionsapologies/">remarkable apologies</a> for highly questionable reporting, decided to introduce a regular corrections column. </p>
<p>We&#8217;re a couple of weeks into it and, as expected, there have been <a href="http://www.regrettheerror.com/2011/10/19/sorry-for-saying-you-got-banned-from-a-french-bar-for-drunken-behaviour-and-encouraging-binge-drinking/">some gems</a>. It&#8217;s a positive move for the paper to standardize the way it presents printed corrections. Unfortunately, the paper has not been so diligent when it comes to adding corrections to its online content. The Mail is still a work in progress.</p>
<p>However, this week it received a <a href="http://www.pcc.org.uk/news/index.html?article=NzQzNg==">favourable ruling</a> from the Press Complaints Commission, a self-regulator for  the British press. <a href="http://www.guardian.co.uk/media/greenslade/2011/oct/31/dailymail-pcc?newsfeed=true">The Guardian&#8217;s Roy Greenslade laid out the details</a>. The important thing to note here is that the PCC found that front page errors by the paper did not require front page corrections. From Greenslade:</p>
<blockquote><p><em>In so doing [the PCC] took the opportunity to set out its thinking as to what constitutes due prominence, making clear that it &#8220;has strong regard for the location of the original article&#8221;. This, however, could not be the &#8220;only determining factor&#8221;.</p>
<p>Its ruling stated: &#8220;The commission will consider the full circumstances surrounding the complaint: the nature of the breach of the code; the scale of the error; the full context of the story; and the existence or otherwise of a designated corrections column&#8221;.</p>
<p>In other words, it is all about proportionality. There is a general rule, but each case must be treated on its merits (or demerits).</p>
<p>In these two cases, the commission clearly decided that although &#8220;the mistakes were sloppy, the issues were not personal to the complainant and had not caused personal harm.&#8221;</p>
<p>In addition, the PCC took the view that the errors did not render the coverage of either story to be wholly inaccurate. So page 2 corrections were sufficient in both cases.</em></p></blockquote>
<p>Here&#8217;s what PCC director Stephen Abell had to say:<br />
<em><br />
<blockquote>&#8220;The issue of ‘due prominence&#8217; as set out in the Editors&#8217; Code will never be an exact science and, as the adjudication makes clear, there will always be legitimate calls for newspapers and magazines to highlight corrections with greater clarity. It may be appropriate in some cases for a newspaper or magazine to publish a front page correction. However, whilst the errors in these two cases were unsatisfactory, the Commission judged that the publication of suitable corrections on page 2 was a sufficient offer which met the ‘due prominence&#8217; requirement of the Editors&#8217; Code&#8221;.</p></blockquote>
<p></em></p>
]]></content:encoded>
			<wfw:commentRss>http://www.regrettheerror.com/2011/11/01/daily-mail-gets-favourable-ruling-from-pcc-regarding-corrections/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Proofreading tips from the New York Times</title>
		<link>http://www.regrettheerror.com/2011/10/05/proofreading-tips-from-the-new-york-times/</link>
		<comments>http://www.regrettheerror.com/2011/10/05/proofreading-tips-from-the-new-york-times/#comments</comments>
		<pubDate>Wed, 05 Oct 2011 12:00:52 +0000</pubDate>
		<dc:creator>Craig Silverman</dc:creator>
				<category><![CDATA[Behind the scenes]]></category>
		<category><![CDATA[Newspapers]]></category>
		<category><![CDATA[accuracy tips]]></category>
		<category><![CDATA[new york times]]></category>

		<guid isPermaLink="false">http://www.regrettheerror.com/?p=14243</guid>
		<description><![CDATA[Patrick LaForge&#8217;s official title at the New York Times is editor of news presentation. In a practical sense, he oversees the copy desks at the paper. (His Twitter account is also worth a follow.) I met LaForge in person in the spring when I gave an error prevention workshop at the Times. (I offered to [...]]]></description>
			<content:encoded><![CDATA[<p>Patrick LaForge&#8217;s official title at the New York Times is editor of news presentation. In a practical sense, he oversees the copy desks at the paper. (His <a href="http://twitter.com/#!/palafo">Twitter account</a> is also worth a follow.)</p>
<p>I met LaForge in person in the spring when I gave an error prevention workshop at the Times. (I offered to give the session; he accepted. I wasn&#8217;t paid.) I mention him now because the Times Topics blog <a href="http://topics.blogs.nytimes.com/2011/10/04/the-readers-lament/">reprinted a notable memo</a> LaForge sent to editors at the paper. Among other information, it included a list of more than 10 proofreading tips &#8220;culled from years of journalism tip sheets.&#8221; </p>
<p>LaForge also addressed the issue of mistakes in the Times:<br />
<em><br />
<blockquote>Mistakes in copy have been a problem since Gutenberg, but it is hard to shake the impression that we have been slipping more than usual, especially in articles that are rushed onto the Web site, bypassing some of our traditional steps. Yes, speed is important in the modern news competition. But readers still have high expectations, especially now that they are paying for online news.</p></blockquote>
<p></em></p>
<p>And he explained that the paper has a policy of giving every article &#8220;at least two reads&#8221;:<br />
<em><br />
<blockquote>This era of news publishing has put a greater emphasis on speed, across multiple formats and platforms. Thanks to blogging and continuous updates, more people in the newsroom find themselves in the role of publishing live material. The same forces have increased the workload and distractions faced by reporters, backfield editors, copy editors and producers. It can be tempting to cut corners. You might decide, unwisely, to save some time by bypassing the copy desk. There is rarely a justification for doing so. Our policy is for every article to get at least two reads, preferably one of them by an experienced copy editor, before publication.</p>
<p>And then you should check your work again, or have someone else check it.
</p></blockquote>
<p></em></p>
<p>But the gold of the <a href="http://topics.blogs.nytimes.com/2011/10/04/the-readers-lament/">post</a> was that list of proofreading tips. Here we go:</p>
<p><em>
<ul>
<li>Break your mind-set: Read the copy out loud. Read it silently, one word at a time. Read it backward and focus on the spelling of words. Print a copy. Preview it in a different application. Change the format or the screen resolution. Justify or unjustify the type. Take a break and return to it with fresh eyes.</li>
<li>Use spelling checkers but don’t trust them. In particular, be aware of homophone confusion: complement and compliment, accept and except, effect and affect, oversees and overseas.</li>
<li>Memorize frequently misspelled and misused words. Here’s a list: http://www.yourdictionary.com/library/misspelled.html.</li>
<li>Beware of contractions and apostrophes: their and they’re, its and it’s, your and you’re.
</li>
<li>After reading for content and spelling, proofread separately for punctuation.
</li>
<li>Beware of doubled words at the end and start of a line. A doubled “that” will often slip right by if you let it.
</li>
<li>Double-check proper names and claims of distinction (first, best, oldest, tallest, etc.).
</li>
<li>Double-check little words that are often interchanged: or, of; it, is.
</li>
<li>Check all the numbers, especially any reference to millions, billions or trillions. Do the math. Do the math again.
</li>
<li>Set aside a regular time to review stylebook and usage rules. This includes backfield editors and reporters. If you don’t want someone to change your story on style grounds (and perhaps introduce an error), learn the basics and follow them.
</li>
<li>Be aware of dates and days of the week, especially in advance copy or copy that has been held. Be aware of references to next month/last month around the time the month is changing.
</li>
<li>Make a personal checklist of the things you tend to miss. Use it on every story.
</li>
<li>Have someone else, preferably a copy editor, read behind you.</li>
</ul>
<p></em></p>
<p>Good tips, and I of course love that he advocates the use of a <a href="http://www.regrettheerror.com/2009/02/04/announcing-the-regret-the-error-paperback-and-a-free-accuracy-checklist/">checklist</a>. Full post is <a href="http://topics.blogs.nytimes.com/2011/10/04/the-readers-lament/">here</a>.</p>
<p>Thanks, <a href="http://twitter.com/#!/BriscoPhoto/">@BriscoPhoto</a>!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.regrettheerror.com/2011/10/05/proofreading-tips-from-the-new-york-times/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Join me and Jack Shafer for a Poynter Institute chat about trust and accuracy today</title>
		<link>http://www.regrettheerror.com/2011/09/28/join-me-and-jack-shafer-for-a-poynter-institute-chat-about-trust-and-accuracy-today/</link>
		<comments>http://www.regrettheerror.com/2011/09/28/join-me-and-jack-shafer-for-a-poynter-institute-chat-about-trust-and-accuracy-today/#comments</comments>
		<pubDate>Wed, 28 Sep 2011 15:07:51 +0000</pubDate>
		<dc:creator>Craig Silverman</dc:creator>
				<category><![CDATA[Behind the scenes]]></category>
		<category><![CDATA[jack shafer]]></category>
		<category><![CDATA[regret press]]></category>
		<category><![CDATA[trust]]></category>

		<guid isPermaLink="false">http://www.regrettheerror.com/?p=14175</guid>
		<description><![CDATA[I&#8217;m joining with Reuters&#8217; Jack Shafer and Mallary Tenore of Poynter today at 12:30 p.m. ET to do a live chat about trust and accuracy. Go here to join in, make comments and ask questions. Here&#8217;s more about the chat: A Pew study released last week found that only 25 percent of the news consumers [...]]]></description>
			<content:encoded><![CDATA[<p><img alt="" src="http://www.poynter.org/wp-content/themes/poynter2011/images/logo_poynter.png" class="alignnone" width="150" height="45" />I&#8217;m joining with <a href="http://blogs.reuters.com/jackshafer/">Reuters&#8217; Jack Shafer</a> and <a href="http://www.poynter.org/author/mjtenore/">Mallary Tenore</a> of Poynter today at 12:30 p.m. ET to do a live chat about trust and accuracy. <a href="http://www.poynter.org/latest-news/top-stories/147423/live-chat-today-with-jack-shafer-why-getting-the-story-right-is-more-important-than-regaining-news-consumers-trust/">Go here</a> to join in, make comments and ask questions. </p>
<p>Here&#8217;s more about the chat:<br />
<em><br />
<blockquote><a href="http://www.poynter.org/latest-news/romenesko/147038/pew-75-of-americans-say-press-cant-get-their-facts-straight/">A Pew study released last week</a> found that only 25 percent of the news consumers surveyed said that news organizations get the facts right. Two-thirds say stories are often inaccurate, and nearly 75 percent believe journalists try to cover up their mistakes.</p>
<p>In a live chat today at 12:30 p.m. ET, Reuters’ Jack Shafer and Regret the Error’s Craig Silverman will talk about the connections between accuracy and trust. We welcome you to join the chat with your thoughts and questions. You can also tweet your questions using the hashtag #poynterchats.</p></blockquote>
<p></em></p>
]]></content:encoded>
			<wfw:commentRss>http://www.regrettheerror.com/2011/09/28/join-me-and-jack-shafer-for-a-poynter-institute-chat-about-trust-and-accuracy-today/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Editor of Kenyan paper does her best to avoid corrections*</title>
		<link>http://www.regrettheerror.com/2011/08/03/editor-of-kenyan-paper-does-her-best-avoid-corrections/</link>
		<comments>http://www.regrettheerror.com/2011/08/03/editor-of-kenyan-paper-does-her-best-avoid-corrections/#comments</comments>
		<pubDate>Wed, 03 Aug 2011 11:30:00 +0000</pubDate>
		<dc:creator>Craig Silverman</dc:creator>
				<category><![CDATA[Behind the scenes]]></category>
		<category><![CDATA[Newspapers]]></category>
		<category><![CDATA[correction policy]]></category>
		<category><![CDATA[regret corrections]]></category>
		<category><![CDATA[scrubbing]]></category>
		<category><![CDATA[the star (kenya)]]></category>

		<guid isPermaLink="false">http://www.regrettheerror.com/?p=13844</guid>
		<description><![CDATA[Karen Rothmyer, public editor of the Star of Nairobi, Kenya, dedicated a recent column to the issue of corrections. Specifically, the issue is that her paper seems to prefer to not publish them. It sometimes publishes a corrective article when a mistake is made, or it will occasionally go into online articles and scrub away [...]]]></description>
			<content:encoded><![CDATA[<p><img src="http://www.regrettheerror.com/wp-content/uploads/2011/08/Screen-shot-2011-08-02-at-9.52.27-PM-150x53.png" alt="" title="Screen shot 2011-08-02 at 9.52.27 PM" width="150" height="53" class="alignnone size-thumbnail wp-image-13856" />Karen Rothmyer, public editor of the Star of Nairobi, Kenya, dedicated <a href="http://www.the-star.co.ke/public-ed/29093-oops-how-the-star-deals-with-its-mistakes">a recent column</a> to the issue of corrections. Specifically, the issue is that her paper seems to prefer to not publish them. </p>
<p>It sometimes publishes a corrective article when a mistake is made, or it will occasionally go into online articles and scrub away mistakes. If it thinks it might get sued, the Star will offer an apology. But the paper&#8217;s editor believes corrections are a bad thing and she does her level best not to publish them.</p>
<p>Needless to say, I&#8217;m not a fan.<br />
<em><br />
<blockquote>
<p> Officially, the Star ethics code states, “Whenever it is noticed that a misleading, inaccurate or distorted article has been published, it must be corrected at the earliest opportunity.” This is similar to the wording in the Media Council’s Code of Conduct. But what does that really mean in practice? To answer that question I sat down with Star Editor Catherine Gicheru.</p>
<p>Gicheru says that she has no problem admitting an out-and-out error — for example when the paper, earlier this year, mixed up an MP’s wife with another woman of the same name who had been charged in a fraud case, the paper carried a page two ‘Apology’ the next day.</p>
<p>But Gicheru says that she tries hard to avoid corrections whenever possible. The main reason, she says, is her concern about the paper’s credibility. “If you have too many corrections, then your credibility starts to plummet,” she says.  And, she says, a lot depends on your competition: if they aren’t printing many corrections, you don’t want to print many either.</p>
</blockquote>
<p></em></p>
<p>This a backward attitude, though it&#8217;s one that used to prevail at many news organizations. </p>
<p>A few quick points: If you have too many <em>errors</em>, your credibility can plummet. It&#8217;s not the same for corrections. And if your competition doesn&#8217;t publish corrections, you have an opportunity to demonstrate your commitment to accountability and professionalism.</p>
<p>The truth is one of the worst things a media outlet can do when it comes to errors is to refuse to acknowledge them, or to offer disingenuous corrections. There is <a href="http://www.regrettheerror.com/2011/07/22/readers-say-corrections-help-a-papers-credibility/">evidence readers feel better about the quality of a newspaper when they see corrections</a>. It demonstrates accountability.<br />
<em><br />
<blockquote>
<p> There are some weeks when she fields as many as three serious demands for corrections, she says, and other weeks when there are none. Her first line of defence is to let the complainant simply blow off steam. Often, she says, that, plus a sympathetic manner and a believable explanation, is enough to cause the caller to relent. “Most often people cool down and say, ‘Okay, I can understand how it happened,’” she says.</p>
</blockquote>
<p></em><br />
Understanding how it happened is good, as is talking to people who request corrections. But it&#8217;s wrong to talk them out of a correction when there was a mistake.<br />
<em><br />
<blockquote>
<p>Some of her other time-tested responses are to offer the person the opportunity to write a letter or a commentary. Or, she may offer the prospect of a friendly story at a later date to make up for the offending one.</p>
</blockquote>
<p></em><br />
Really? Gicheru would rather promise favorable future coverage than issue a basic correction? That&#8217;s unethical.</p>
<blockquote><p><em>
<p> Gicheru also favours a technique that I’ve also seen used elsewhere: finding a reason to run a follow-up story that corrects the error without ever acknowledging that one has been made &#8230;</p>
<p></em></p></blockquote>
<p>Anything to avoid a correction&#8230;</p>
<blockquote><p><em>
<p> Gicheru says that if she decides that there is no other course but to print a correction, she will determine what to call it according to its severity. If it’s an honest mistake, it will be called a ‘clarification’. If it’s inexcusable, it will be called a ‘correction’. And if it has the potential to turn into a libel case, it will be billed as an ‘apology’.  “You’re really pleading at that point,” she says.</p>
<p></em></p></blockquote>
<p>I don&#8217;t think readers understand the distinction between a clarification and a correction, so I usually counsel news organizations to stick to one term. However, if you&#8217;re offering an apology then by all means call it that.</p>
<p>After hearing the many ways in which the paper&#8217;s editor goes out of her way to avoid corrections, Rothmyer offers this view:</p>
<blockquote><p><em>
<p> Maybe it’s because I’m no longer in the hot seat myself, either as a reporter or an editor, but I personally would like to see more Star corrections (called, moreover, by their right name rather than the weasel word ‘clarification’).</p>
<p></em></p></blockquote>
<p>Agreed, but what about the scrubbing and the unethical practice of promising favorable coverage after an error?</p>
<p>Hat tip to <a href="http://www.stinkyjournalism.org/">Stinky Journalism</a>.</p>
<p><strong>*Correction August 3, 2011:</strong> The original headline on this post left out the word &#8220;to&#8221;. Thanks to <a href="http://twitter.com/scottleadingham">@scottleadingham</a> for spotting the typo! </p>
]]></content:encoded>
			<wfw:commentRss>http://www.regrettheerror.com/2011/08/03/editor-of-kenyan-paper-does-her-best-avoid-corrections/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Fake Piers Morgan rumor takes Twitter, leads to debate</title>
		<link>http://www.regrettheerror.com/2011/07/28/fake-piers-morgan-rumor-takes-twitter-leads-to-debate/</link>
		<comments>http://www.regrettheerror.com/2011/07/28/fake-piers-morgan-rumor-takes-twitter-leads-to-debate/#comments</comments>
		<pubDate>Fri, 29 Jul 2011 00:31:11 +0000</pubDate>
		<dc:creator>Craig Silverman</dc:creator>
				<category><![CDATA[Behind the scenes]]></category>
		<category><![CDATA[Online]]></category>
		<category><![CDATA[crunks11]]></category>
		<category><![CDATA[twitter]]></category>

		<guid isPermaLink="false">http://www.regrettheerror.com/?p=13801</guid>
		<description><![CDATA[A variety of media folks got caught up in a false rumor today, after word began to spread that CNN had suspended Piers Morgan. Martin Bryant has a good roundup at the Next Web: The latest example of ‘think before you retweet’ emerged today when a false rumor spread like wildfire that British journalist and [...]]]></description>
			<content:encoded><![CDATA[<p>A variety of media folks got caught up in a false rumor today, after word began to spread that CNN had suspended Piers Morgan. Martin Bryant has a good <a href=http://thenextweb.com/socialmedia/2011/07/28/anatomy-of-a-twitter-rumor-when-a-storys-too-juicy-not-to-retweet/?awesm=tnw.to_1AAky&#038;utm_campaign=&#038;utm_medium=tnw.to-other&#038;utm_source=direct-tnw.to&#038;utm_content=spreadus_master>roundup at the Next Web</a>:<br />
<em><br />
<blockquote>
<p>The latest example of ‘think before you retweet’ emerged today when a false rumor spread like wildfire that British journalist and TV presenter Piers Morgan had been suspended from his position as a CNN talkshow host.</p>
<p>For ten minutes, my Twitter stream lit up with frantic retweets and discussion over the ‘news’, which followed speculation over the former UK tabloid editor’s possible knowledge of phone hacking. Quickly it emerged that it was a hoax and things calmed back down again. But what happened in those few minutes?</p>
<p>It appears that <a href="http://twitter.com/#!/JonSnowC4">Jon Snow</a>, the well-respected anchor of Channel 4 News in the UK, was the first to tweet out a report about Morgan’s alleged suspension. It appears he got the ‘news’ from @danwooden – a parody account based on former News of the World showbiz reporter Dan Wootton, which had <a href="http://twitter.com/#!/danwooden/status/96614618616700928">tweeted</a> &#8230;</p>
</blockquote>
<p></em></p>
<p>The episode led to a couple of interesting pieces of debate about how journalists should treat rumors on Twitter. From journalist Neal Mann:</p>
<p><img alt="" src="http://cdn.thenextweb.com/socialmedia/files/2011/07/Screen-Shot-2011-07-28-at-18.23.47-520x243.png" class="alignnone" width="400" height="200" /></p>
<p>Reuters blogger Felix Salmon also weighed in with a <a href="http://felixsalmon.tumblr.com/">post on his Tumblr</a> arguing that Twitter &#8220;behaves in many ways a lot more like a newsroom than a newspaper.&#8221; More:<br />
<em><br />
<blockquote>Rumors happen there, and then they get shot down — no harm no foul.</p>
<p>I think that big flagship Twitter accounts like @Reuters or @WSJ should be held to a higher standard. But for the rest of us, we’re conversing on Twitter just like we converse in real life. In the newsroom, we say things like “did you hear that Piers Morgan just got suspended?” and that’s fine. Is it really that bad to say that kind of thing in the new newsroom called Twitter? I don’t think so. People are human, they believe rumors, make mistakes, jump to conclusions. Twitter is just a healthy reminder of that fact.</p></blockquote>
<p></em></p>
<p>True, it&#8217;s a reminder. But this rumor originated with a fake account. It was pretty easy for Jon Snow to take an extra few minutes to check the source of the tweet and see that it wasn&#8217;t credible. You can debate and celebrate the self-correcting nature of Twitter, but it bears repeating that this wasn&#8217;t a case of confusion or conflicting information. A fake Twitter account tweeted a hoax and a bunch of journalists fell for it. That seems pretty straightforward. I thought Dan Gillmor <a href="http://twitter.com/#!/dangillmor/status/96680164129382401">put it well</a>:</p>
<p><img src="http://www.regrettheerror.com/wp-content/uploads/2011/07/Screen-shot-2011-07-28-at-8.19.03-PM.png" alt="" title="Screen shot 2011-07-28 at 8.19.03 PM" width="400" height="200" class="alignnone size-full wp-image-13806" /></p>
<p>I don&#8217;t mean to sound dismissive of the points made by Salmon, a writer whose work I enjoy; but this incident doesn&#8217;t strike me as a good example of how Twitter can be such a good tool for correcting misinformation and moving reporting and discussion forward.</p>
<p>Finally, <a href="http://storify.com/rossneumann/how-twitter-squashed-pierce-morgan-suspension-rumo">here&#8217;s</a> a great Storfiy from Ross Neumann that tracks the spread and correction of the rumor.</p>
<p><script src="http://storify.com/rossneumann/how-twitter-squashed-pierce-morgan-suspension-rumo.js"></script><noscript>[<a href="http://storify.com/rossneumann/how-twitter-squashed-pierce-morgan-suspension-rumo" target="blank">View the story "20 Minutes: Life of a Twitter Rumor" on Storify]</a></noscript></p>
]]></content:encoded>
			<wfw:commentRss>http://www.regrettheerror.com/2011/07/28/fake-piers-morgan-rumor-takes-twitter-leads-to-debate/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Worth reading: &#8216;Corrections in the Web Age: The Case of the New York Times&#8217; Terror Error&#8217;</title>
		<link>http://www.regrettheerror.com/2011/07/22/worth-reading-corrections-in-the-web-age-the-case-of-the-new-york-times-terror-error/</link>
		<comments>http://www.regrettheerror.com/2011/07/22/worth-reading-corrections-in-the-web-age-the-case-of-the-new-york-times-terror-error/#comments</comments>
		<pubDate>Fri, 22 Jul 2011 12:30:41 +0000</pubDate>
		<dc:creator>Craig Silverman</dc:creator>
				<category><![CDATA[Behind the scenes]]></category>
		<category><![CDATA[Newspapers]]></category>
		<category><![CDATA[crunks11]]></category>
		<category><![CDATA[delayed corrections]]></category>
		<category><![CDATA[new york times]]></category>

		<guid isPermaLink="false">http://www.regrettheerror.com/?p=13750</guid>
		<description><![CDATA[It is hard to describe the interview that took place on KQED&#8217;s Forum show on May 25, 2011, as anything other than a train wreck. Osama bin Laden was dead, and Frank Lindh &#8212; father of John Walker Lindh, the &#34;American Taliban&#34; &#8212; had been invited on to discuss a New York Times op-ed piece [...]]]></description>
			<content:encoded><![CDATA[<p><em><br />
<blockquote>
<p>It is hard to describe the interview that took place on KQED&#8217;s Forum show on May 25, 2011, as anything other than a train wreck.</p>
<p>Osama bin Laden was dead, and Frank Lindh &#8212; father of John Walker Lindh, the &quot;American Taliban&quot; &#8212; had been invited on to discuss a New York Times op-ed piece he&#8217;d just published about his son&#8217;s 20-year prison sentence. The moment host Dave Iverson completed his introduction about the politically and emotionally charged case, Lindh cut in: &quot;Can I add a really important correction to what you just said?&quot;</p>
<p>Iverson had just described John Walker Lindh&#8217;s 2002 guilty plea as &quot;one count of providing services to a terrorist organization.&quot; That, Frank Lindh said, was simply wrong.</p>
<p>Yes, his son had pled guilty to providing services to the Taliban, in whose army he had enlisted. Doing so was a crime because the Taliban government was under U.S. economic sanctions for harboring Al Qaeda. But the Taliban was not (and has never been) classified by the U.S. government as a terrorist organization itself.</p>
<p>This distinction might seem picayune. But it cut to the heart of the disagreement between Americans who have viewed John Walker Lindh as a traitor and a terrorist and those, like his father, who believe he was a fervent Muslim who never intended to take up arms against his own country.</p>
<p>That morning, the clash over this one fact set host and guest on a collision course for the remainder of the 30-minute interview. The next day, KQED ran a half-hour Forum segment apologizing for the mess and picking over its own mistakes.</p>
<p>KQED&#8217;s on-air fiasco didn&#8217;t happen randomly or spontaneously. The collision was set in motion nine years before by 14 erroneous words in the New York Times.</p>
<p>This is the story of how that error was made, why it mattered, why it hasn&#8217;t been properly corrected to this day &#8212; and what lessons it offers about how newsroom traditions of verification and correction must evolve in the digital age&#8230;</p>
<p></em></p></blockquote>
<p>&#8211; via <a href='http://www.theatlantic.com/technology/archive/2011/07/-strike-corrections-strike-in-the-web-age-the-case-of-the-new-york-times-terror-error/242204/'>&#8220;Corrections in the Web Age: The Case of the New York Times&#8217; Terror Error</a>,&#8221; a great piece by Scott Rosenberg and Mark Follman of MediaBugs. A must read.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.regrettheerror.com/2011/07/22/worth-reading-corrections-in-the-web-age-the-case-of-the-new-york-times-terror-error/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>New York Times redesigns its online corrections page</title>
		<link>http://www.regrettheerror.com/2011/07/13/new-york-times-redesigns-its-online-corrections-page/</link>
		<comments>http://www.regrettheerror.com/2011/07/13/new-york-times-redesigns-its-online-corrections-page/#comments</comments>
		<pubDate>Wed, 13 Jul 2011 12:00:34 +0000</pubDate>
		<dc:creator>Craig Silverman</dc:creator>
				<category><![CDATA[Behind the scenes]]></category>
		<category><![CDATA[Newspapers]]></category>
		<category><![CDATA[corrections systems]]></category>
		<category><![CDATA[new york times]]></category>
		<category><![CDATA[Online Corrections]]></category>

		<guid isPermaLink="false">http://www.regrettheerror.com/?p=13655</guid>
		<description><![CDATA[The New York Times has a new online corrections page. For several years the page (http://www.nytimes.com/pages/corrections/index.html) was updated to show only that day&#8217;s corrections. Now it links to the seven most recent days of corrections: It also has a list of recently corrected articles: Both these things are improvements. The links to recent days of [...]]]></description>
			<content:encoded><![CDATA[<p><img src="http://www.regrettheerror.com/wp-content/uploads/2009/01/nytbanner1-150x25.gif" alt="" title="nytbanner1" width="150" height="25" class="alignnone size-thumbnail wp-image-6855" />The New York Times has a new online corrections page. For several years the page (http://www.nytimes.com/pages/corrections/index.html) was updated to show only that day&#8217;s corrections. Now <a href="http://www.nytimes.com/pages/corrections/index.html">it</a> links to the seven most recent days of corrections:</p>
<p><a href="http://www.regrettheerror.com/wp-content/uploads/2011/07/Screen-shot-2011-07-12-at-9.14.44-PM.png"><img src="http://www.regrettheerror.com/wp-content/uploads/2011/07/Screen-shot-2011-07-12-at-9.14.44-PM.png" alt="" title="Screen shot 2011-07-12 at 9.14.44 PM" width="400" height="300" class="alignnone size-full wp-image-13656" /></a></p>
<p>It also has a list of recently corrected articles:</p>
<p><a href="http://www.regrettheerror.com/wp-content/uploads/2011/07/Screen-shot-2011-07-12-at-9.14.59-PM.png"><img src="http://www.regrettheerror.com/wp-content/uploads/2011/07/Screen-shot-2011-07-12-at-9.14.59-PM.png" alt="" title="Screen shot 2011-07-12 at 9.14.59 PM" width="400" height="300" class="alignnone size-full wp-image-13657" /></a></p>
<p>Both these things are improvements. The links to recent days of corrections makes additional corrections easily accessible from the page. The list of recently corrected articles also provides some nice context, as some readers may recognize a familiar headline and click through to read a correction they may have missed.</p>
<p>Three additions I&#8217;d like to see are an RSS feed for corrections, a link to a page where readers can learn more about the paper&#8217;s corrections policy, and a form people can use to submit a correction. (Have a look at the form on the <a href="http://www.chicagotribune.com/news/corrections/">Chicago Tribune&#8217;s corrections page</a>.)</p>
<p>Apart from that, it would be great to see the Times embrace a <a href="http://reportanerror.org/">report an error button</a> for its content.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.regrettheerror.com/2011/07/13/new-york-times-redesigns-its-online-corrections-page/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Worth reading: &#8216;There&#8217;s No Problem!&#8217; Newsrooms in Denial About Rampant Errors&#8217;</title>
		<link>http://www.regrettheerror.com/2011/04/28/worth-reading-theres-no-problem-newsrooms-in-denial-about-rampant-errors/</link>
		<comments>http://www.regrettheerror.com/2011/04/28/worth-reading-theres-no-problem-newsrooms-in-denial-about-rampant-errors/#comments</comments>
		<pubDate>Thu, 28 Apr 2011 12:00:31 +0000</pubDate>
		<dc:creator>Craig Silverman</dc:creator>
				<category><![CDATA[Behind the scenes]]></category>
		<category><![CDATA[Worth Reading]]></category>
		<category><![CDATA[accuracy studies]]></category>
		<category><![CDATA[error prevention]]></category>

		<guid isPermaLink="false">http://www.regrettheerror.com/?p=13065</guid>
		<description><![CDATA[This post, &#8220;There&#8217;s No Problem!&#8217; Newsrooms in Denial About Rampant Errors,&#8221; from MediaBugs executive director Scott Rosenberg is in reply to this post from Jonathan Stray. Together, they encompass much of the information you need to get a good understanding of newspaper accuracy and some of the failures of correction. So not just worth reading [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.pbs.org/idealab/2011/04/theres-no-problem-newsrooms-in-denial-about-rampant-errors115.html">This post</a>, &#8220;There&#8217;s No Problem!&#8217; Newsrooms in Denial About Rampant Errors,&#8221; from <a href="http://mediabugs.org">MediaBugs</a> executive director Scott Rosenberg is in reply to <a href="http://jonathanstray.com/measuring-and-increasing-accuracy-in-journalism">this post from Jonathan Stray</a>. Together, they encompass much of the information you need to get a good understanding of newspaper accuracy and some of the failures of correction. So not just worth reading &#8212; must reads. From Scott&#8217;s post:<br />
<i><br />
<blockquote>&#8230; In the field of corrections as anywhere else, &#8220;openness&#8221; isn&#8217;t binary &#8212; it has gradations and nuances. I like to imagine these as a sort of ladder of transparency that news organizations need to climb.</p>
<p>On the first rung of this ladder, journalists readily fix mistakes they learn about and conscientiously disclose and record the details of each fix. (Most newsrooms declare allegiance to this ideal but, sadly, our MediaBugs research shows, the majority still fail to live up to it.)</p>
<p>One rung up, news outlets effectively solicit error reports from their audiences, making it clear that they welcome the feedback and will respond. The Report an Error Alliance is trying to push more news organizations to climb up here.</p>
<p>On the next rung up, newsrooms also willingly expose their own internal deliberations over particular controversies, explaining why they did or didn&#8217;t correct some issue readers raised and leaving some sort of public trail of the decision. At some publications, the ombudsman or public editor takes care of some of this.</p>
<p>On the final, topmost rung, the news organization will assure accountability by turning to a neutral third party to maintain a fair record of issues raised by the public. This shows external critics that the newsroom isn&#8217;t hiding anything or trying to shove problems under the rug&#8230; </i></p></blockquote>
]]></content:encoded>
			<wfw:commentRss>http://www.regrettheerror.com/2011/04/28/worth-reading-theres-no-problem-newsrooms-in-denial-about-rampant-errors/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>U.K. Press Complaints Commission publishes guidance for online corrections</title>
		<link>http://www.regrettheerror.com/2011/02/11/u-k-press-complaints-commission-publishes-guidance-for-online-corrections/</link>
		<comments>http://www.regrettheerror.com/2011/02/11/u-k-press-complaints-commission-publishes-guidance-for-online-corrections/#comments</comments>
		<pubDate>Fri, 11 Feb 2011 13:34:44 +0000</pubDate>
		<dc:creator>Craig Silverman</dc:creator>
				<category><![CDATA[Behind the scenes]]></category>
		<category><![CDATA[correction policy]]></category>
		<category><![CDATA[Online Corrections]]></category>
		<category><![CDATA[press complaints commission]]></category>

		<guid isPermaLink="false">http://www.regrettheerror.com/?p=12699</guid>
		<description><![CDATA[A recent edition of my weekly column for Columbia Journalism Review featured a Q&#38;A with PCC director Stephen Abell. He told me that the organization recently set up a working group to come up with guidance regarding online corrections and apologies. The guidelines were published today, and here are the notable sections: The starting point [...]]]></description>
			<content:encoded><![CDATA[<p>A recent edition of my weekly column for Columbia Journalism Review <a href="http://www.cjr.org/behind_the_news/q_a_stephen_abell.php?page=all">featured a Q&amp;A with PCC director Stephen Abell</a>. He told me that the organization recently set up a working group to come up with guidance regarding online corrections and apologies. The guidelines were <a href="http://www.pcc.org.uk/news/index.html?article=NjkzOA==">published today</a>, and here are the notable sections:</p>
<blockquote>
<p><em>The starting point for the Commission will be that, if an article appears in print and online, the proposed remedy will often appear in both media. This note is not designed to be prescriptive, and will take into account the existence of differing practice. The test, in the end, will be whether the requirement of &quot;due prominence&quot; is met. The following points are relevant:<br />
		</em></p>
<ul>
<li><em>Negotiation is a key part of the PCC process, and discussion between complainant, editor and PCC will be necessary in the placement of online &#8211; as offline &#8211; corrections and apologies. Clause 1 (Accuracy) of the Code states: &quot;in cases involving the Commission, prominence should be agreed with the PCC in advance&quot;.</em></li>
<li><em>Readers will access information on newspaper and magazine websites via different means (such as searches or links), so there is not automatically a correlation between the original location of an article and the placement of a correction or apology. The existence of a paywall may impact on how a site is initially accessed, and this should be taken into account. However, for stand-alone corrections and apologies, editors should give consideration to appropriate placement on the relevant section where the original article appeared (such as the &quot;news&quot; or &quot;showbusiness&quot; section, for example).</em></li>
<li><em>If the resolution to a complaint is a stand-alone text (an apology, correction or letter), it will generally be appropriate to link to the original article under complaint (should it still be published online) and for the original article to link back to it. If the original article has been removed, then how long the apology, correction or letter should remain online should be the subject of negotiation with the PCC.</em></li>
<li><em>Corrections or apologies that appear on the original article should be clearly marked.</em></li>
<li><em>If the outcome of a complaint is that the text of the article is significantly amended, then consideration should be given to the publication making explicit reference to the existence of the alteration. How quickly the text has been amended will be a factor in this consideration.</em></li>
<li><em>Care must be taken that the URL of an article does not contain information that has been the subject of successful complaint. If an article is amended, then steps should be taken to amend the URL, as necessary.</em></li>
<li><em>Online corrections and apologies should be tagged when published to ensure that they are searchable.</em></li>
</ul>
</blockquote>
<p>I was hoping the guidance would endorse a dedicated online corrections page (here&#39;s <a href="http://www.guardian.co.uk/theguardian/series/correctionsandclarifications">the Guardian&#39;s</a>), and come out against <a href="http://www.cjr.org/regret_the_error/scrubbing_away_their_sins.php">scrubbing away errors</a>. PCC Watch also <a href="http://pccwatch.co.uk/pcc-guidance-on-digital-corrections-welcome/">raised another relevant point</a>:</p>
<p>&nbsp;</p>
<blockquote>
<p><em>In the longer term, the PCC will need to consider how it treats tweets and Facebook status updates from journalists where measuring online prominence is far harder. Equally, timely corrections of content that has appeared on apps will need to be addressed sooner rather than later.</em></p>
</blockquote>
]]></content:encoded>
			<wfw:commentRss>http://www.regrettheerror.com/2011/02/11/u-k-press-complaints-commission-publishes-guidance-for-online-corrections/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Washington Post hopes new editing system will reduce errors</title>
		<link>http://www.regrettheerror.com/2011/01/25/washington-post-hopes-new-editing-system-will-reduce-errors/</link>
		<comments>http://www.regrettheerror.com/2011/01/25/washington-post-hopes-new-editing-system-will-reduce-errors/#comments</comments>
		<pubDate>Tue, 25 Jan 2011 13:00:48 +0000</pubDate>
		<dc:creator>Craig Silverman</dc:creator>
				<category><![CDATA[Behind the scenes]]></category>
		<category><![CDATA[Newspapers]]></category>
		<category><![CDATA[copy editing]]></category>
		<category><![CDATA[quality control]]></category>
		<category><![CDATA[typos]]></category>
		<category><![CDATA[washington post]]></category>

		<guid isPermaLink="false">http://www.regrettheerror.com/?p=12599</guid>
		<description><![CDATA[In his final column, outgoing Washington Post ombudsman Andrew Alexander writes that the Post &#8230; has become riddled with typos, grammatical mistakes and intolerable &#34;small&#34; factual errors that erode credibility. Local news coverage, once robust, has withered. The Post often trails the competition on stories. The excessive use of anonymous sources has expanded into blogs. [...]]]></description>
			<content:encoded><![CDATA[<p><img alt="" class="aligncenter size-full wp-image-6574" height="28" src="http://www.regrettheerror.com/wp-content/uploads/2008/11/washpost4.gif" title="washpost4" width="138" />In his <a href="http://www.washingtonpost.com/wp-dyn/content/linkset/2009/02/25/LI2009022502075.html">final column</a>, outgoing Washington Post ombudsman Andrew Alexander writes that the Post</p>
<blockquote>
<p><em>&#8230; has become riddled with typos, grammatical mistakes and intolerable &quot;small&quot; factual errors that erode credibility. Local news coverage, once robust, has withered. The Post often trails the competition on stories. The excessive use of <a href="http://www.washingtonpost.com/wp-dyn/content/article/2010/12/17/AR2010121704658.html" target="">anonymous sources</a> has expanded into blogs. The once-broken system for publishing corrections has been repaired, but corrections often still take too long to appear. The list goes on. </em></p>
<div><em>Much of this is a result of upheaval, disruption and necessary cost-cutting. Over the past few years, once-separate </em></div>
<div><em>print and online staffs have been combined. The traditional newsroom structure was blown up and reconfigured. New editors are in charge. Scores of staffers have been reassigned.</em></div>
</blockquote>
<p>And in a <a href="http://live.washingtonpost.com/ask-the-post:-the-revamped-washington-post.html#question-9">Q&amp;A with readers</a>, Post executive editor Marcus Brauchli seems to agree:</p>
<blockquote>
<p><em>The ombudsman is right that there have been too many careless errors lately&#8211;typos, grammatical errors, silly factual mistakes. I don&#39;t want to make excuses, because we shouldn&#39;t tolerate&nbsp;these sorts of errors. But by way of explanation I will say that we have made a number of changes in our processes in the last couple of years and are putting in a new editing system that will further change workflows for editors. We try to be diligent about publishing corrections, and the data are interesting: we published 1,054 corrections in 2010, up from 1,040 a year earlier and 961 in 2008, but down from a recent high of 1,319 in 2005. We have room to improve.</em></p>
</blockquote>
<p>It&#39;s good news that the Post is bringing in a new system. The old one has been cut and altered to the point that it&#39;s a shell of its former self. Let&#39;s hope the new system improves workflow and quality. A challenge, to be sure. But a worthy one.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.regrettheerror.com/2011/01/25/washington-post-hopes-new-editing-system-will-reduce-errors/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Worth reading: &#8216;How NPR Giffords&#8217; Mistake Hurt The Families&#8217;</title>
		<link>http://www.regrettheerror.com/2011/01/19/worth-reading-how-npr-giffords-mistake-hurt-the-families/</link>
		<comments>http://www.regrettheerror.com/2011/01/19/worth-reading-how-npr-giffords-mistake-hurt-the-families/#comments</comments>
		<pubDate>Wed, 19 Jan 2011 13:00:57 +0000</pubDate>
		<dc:creator>Craig Silverman</dc:creator>
				<category><![CDATA[Behind the scenes]]></category>
		<category><![CDATA[Ombudsmen]]></category>
		<category><![CDATA[giffords]]></category>
		<category><![CDATA[obiticide]]></category>

		<guid isPermaLink="false">http://www.regrettheerror.com/?p=12530</guid>
		<description><![CDATA[I&#8217;ve since learned what real, excruciating pain NPR triggered with its false news report that Rep. Gabrielle Giffords had died, which was repeated on npr.org, e-mail alerts, Twitter and picked up by other news organizations. NPR correspondent Ted Robbins is based in Tucson. He was at the scene Jan. 8 when his cell phone rang [...]]]></description>
			<content:encoded><![CDATA[<blockquote>
<p><i>I&rsquo;ve since learned what real, excruciating pain NPR triggered with its false news report that Rep. Gabrielle Giffords had died, which was repeated on npr.org, e-mail alerts, Twitter and picked up by other news organizations.</i></p>
<p><i>NPR correspondent Ted Robbins is based in Tucson. He was at the scene Jan. 8 when his cell phone rang shortly after NPR aired at 2:01 p.m. EST that Giffords died. The call was a friend, who is also a friend of Giffords.</i></p>
<p><i>The friend was sitting outside the hospital operating room with Giffords&rsquo; mother Gloria, holding her hand.</i></p>
<p><i>&ldquo;Please tell them to stop reporting she is dead,&rdquo; he begged Robbins. &ldquo;She is in surgery.&rdquo;</i></p>
<p><i>Robbins immediately called NPR but was told NPR was sticking to the story since it had two sources.</i></p>
<p><i>Scott Simon, host of NPR&#39;s Weekend Edition Saturday, got a similar call. Simon and his family are close friends of Giffords and her husband, astronaut Mark Kelly.</i></p>
<p><i>At 2:08, a distraught family member called: &quot;Scott, where the hell is NPR getting that information?&quot;</i></p>
<p><i>&quot;The close family member is a huge NPR fan or was,&rdquo; said Simon. &ldquo;Until that moment, he found NPR more reliable than other news outlets. He had been told that Gabby was in surgery. But he was anxious, isolated, and wondered why NPR would report such a thing if it were not true.&rdquo;</i></p>
<p><i>Simon phoned the NPR news desk and was told the information was based on &quot;confirmation&quot; from the Pima County Sheriff&rsquo;s department and a congressional source.</i></p>
<p><i>He didn&rsquo;t think that was good enough &#8230;</i></p>
<p><i>Simon sent these suggested operating principles to top management:</i></p>
<p><i>&ldquo;There should be no room for doubt when a news organization declares someone dead. They should wait until the medical authorities directly involved declare death, or close family members announce it. There is simply no way that anyone else&mdash;not local police, not witnesses, not &#39;two governmental sources&#39;&mdash;would be in a position to know for certain especially when there are now, between respiration and brain activity, at least a couple of medical gauges of death.&rdquo;</i></p>
</blockquote>
<p>&#8211; via <a href="http://www.npr.org/blogs/ombudsman/2011/01/18/132964802/how-npr-giffords-mistake-hurt-the-families">How NPR Giffords&#39; Mistake Hurt The Families</a>, a blog post from NPR ombudsman Alicia Shepard.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.regrettheerror.com/2011/01/19/worth-reading-how-npr-giffords-mistake-hurt-the-families/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

