<?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; error tracking</title>
	<atom:link href="http://www.regrettheerror.com/tag/error-tracking/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>MediaBugs reports shows Bay Area media falling down when it comes to corrections</title>
		<link>http://www.regrettheerror.com/2010/07/15/mediabugs-reports-shows-bay-area-media-falling-down-when-it-comes-to-corrections/</link>
		<comments>http://www.regrettheerror.com/2010/07/15/mediabugs-reports-shows-bay-area-media-falling-down-when-it-comes-to-corrections/#comments</comments>
		<pubDate>Thu, 15 Jul 2010 12:00:19 +0000</pubDate>
		<dc:creator>Craig Silverman</dc:creator>
				<category><![CDATA[Behind the scenes]]></category>
		<category><![CDATA[Newspapers]]></category>
		<category><![CDATA[Online]]></category>
		<category><![CDATA[Regret Articles]]></category>
		<category><![CDATA[corrections systems]]></category>
		<category><![CDATA[error tracking]]></category>
		<category><![CDATA[mediabugs]]></category>

		<guid isPermaLink="false">http://www.regrettheerror.com/?p=11205</guid>
		<description><![CDATA[Scott Rosenberg and Mark Follman of MediaBugs released a new report this week that highlights some corrections-related problems with Bay Area news outlets. (I&#8217;m an unpaid advisor to the project, but didn&#8217;t have any involvement with the report.) Here&#8217;s the core information: The results of MediaBugs&#8217; first survey of Bay Area media correction practices show [...]]]></description>
			<content:encoded><![CDATA[<p>Scott Rosenberg and Mark Follman of <a href="http://mediabugs.org">MediaBugs</a> released <a href="http://mediabugs.org/pages/hard-to-get-a-fix-state-of-bay-area-corrections-july-2010">a new report this week </a>that highlights some corrections-related problems with Bay Area news outlets. (I&#8217;m an unpaid advisor to the project, but didn&#8217;t have any involvement with the report.) Here&#8217;s the core information:</p>
<blockquote><p><em>The results of MediaBugs&#8217; first survey of Bay Area media correction practices show that 21 out of 28 news sites examined &#8212; including many of the region&#8217;s leading daily newspapers and broadcast news outlets &#8212; provide no corrections link on their websites&#8217; home pages and article pages. The websites for 17 of the 28 news organizations examined have no corrections policy or substantive corrections content at all.</p>
<p>Sites that do offer corrections-related content frequently make it relatively difficult to find: It is located two or three obscure clicks into the site, or requires visitors to use the site&#8217;s search function. Once located, the corrections content is, in most cases, poorly organized and not easily navigated.</em></p></blockquote>
<p>As Rosenberg noted in an email to me, this isn&#8217;t exactly surprising. Online correction pages are still the exception, not the rule. The same is true for error reporting tools. The MediaBugs report offers some much needed proof that media organizations aren&#8217;t putting the proper amount of thought and effort into corrections. Here&#8217;s what Rosenberg wrote in a blog <a href="http://www.pbs.org/idealab/2010/07/when-it-comes-to-corrections-most-news-sites-fail194.html">post</a> for PBS MediaShift Idea Lab (where I&#8217;m an editor):</p>
<blockquote><p><em>Fifteen years ago, in the early days of web publishing, it might have been understandable for editors to have a hard time figuring out how to handle corrections: This pliable medium was new and strange.</p>
<p>But news on the web is no longer in its infancy, and &#8220;We&#8217;re new to this&#8221; just doesn&#8217;t cut it anymore as an explanation for the kind of poor practices our MediaBugs survey documents. The explanations you generally hear are truthful but don&#8217;t excuse the problems: &#8220;Our content management system makes it too hard to do that&#8221; or &#8220;we just don&#8217;t have the resources to do that&#8221; or &#8220;we&#8217;ve been meaning to fix that for a while but never seem to get around to it.&#8221;</p>
<p>The web excels at connecting people. That&#8217;s what its technology is for. Yet when it comes to the most basic areas of accuracy and accountability, the professional newsrooms of the Bay Area (and so many other communities) continue to do a poor job of connecting with their own readers.</em> </p></blockquote>
<p>Rosenberg and I agree that it&#8217;s important to create a standardized error reporting function for the web. Something that every organization can implement in the same way. (He cited RSS as an example of how this kind of standardization can work.)  I wrote about this idea in <a href="http://www.cjr.org/behind_the_news/report_the_error.php">a recent column for Columbia Journalism Review</a>:</p>
<blockquote><p><em>Another example would be RSS. One way that it achieved mass adoption was by becoming standardized on major blogging platforms and then adopted by major Web sites. At the same time, the adoption of the RSS icon created a universal visual cue that helped drive understanding among Internet users.</p>
<p>Rosenberg is currently pondering the creation of something similar for â€œreport an errorâ€ functionality. There are currently some large news Web sites that offer thisâ€”including the Toronto Star and Huffington Post (though theirs is hidden near the bottom of articles)â€”but it is by no means a standard. The New York Times, The Washington Post, the Los Angeles Times, and CNN, among many others, donâ€™t include that option on their articles and pages. Itâ€™s such a simple, effective way to collect error reports, not to mention give readers a chance to participate and contribute.</p>
<p>But where it should be placed on the page? Do we need a universal icon? How about the interface that pops up after you click on that button? Should that be standardized? The fundamental idea is sound, but there are lots of details to work out. Rosenberg is thinking of the best way to move forward with the idea, and Iâ€™m hoping to help. </em></p></blockquote>
<p>Who else wants to pitch in?</p>
]]></content:encoded>
			<wfw:commentRss>http://www.regrettheerror.com/2010/07/15/mediabugs-reports-shows-bay-area-media-falling-down-when-it-comes-to-corrections/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>NYT public editor addresses errors made in Cronkite article; some basic advice for preventing errors</title>
		<link>http://www.regrettheerror.com/2009/08/02/nyt-public-editor-addresses-errors-made-in-cronkite-article-some-basic-advice-for-preventing-errors/</link>
		<comments>http://www.regrettheerror.com/2009/08/02/nyt-public-editor-addresses-errors-made-in-cronkite-article-some-basic-advice-for-preventing-errors/#comments</comments>
		<pubDate>Sun, 02 Aug 2009 16:35:56 +0000</pubDate>
		<dc:creator>Craig Silverman</dc:creator>
				<category><![CDATA[Behind the scenes]]></category>
		<category><![CDATA[Newspapers]]></category>
		<category><![CDATA[Regret Articles]]></category>
		<category><![CDATA[alessandra stanley]]></category>
		<category><![CDATA[checklists]]></category>
		<category><![CDATA[error prevention]]></category>
		<category><![CDATA[error tracking]]></category>
		<category><![CDATA[new york times]]></category>

		<guid isPermaLink="false">http://www.regrettheerror.com/?p=8758</guid>
		<description><![CDATA[New York Times public editor Clark Hoyt has weighed in on the paperâ€™s recent, error-riddled story about Walter Cronkite. The story, written by television critic Alessandra Stanley, resulted in two corrections, one of which was for seven mistakes. I wrote about the mistakes, and Stanleyâ€™s history of error, in a recent column for Columbia Journalism [...]]]></description>
			<content:encoded><![CDATA[<p><img class="alignnone size-thumbnail wp-image-6855" title="nytbanner1" src="http://www.regrettheerror.com/wp-content/uploads/2009/01/nytbanner1-150x25.gif" alt="nytbanner1" width="150" height="25" />New York Times public editor Clark Hoyt has <a href="http://www.nytimes.com/2009/08/02/opinion/02pubed.html?src=twt&amp;twt=thepubliceditor">weighed in</a> on the paperâ€™s recent, <a href="http://www.nytimes.com/2009/07/18/arts/television/18appraisal.html?_r=1">error-riddled story</a> about Walter Cronkite. The story, written by television critic Alessandra Stanley, resulted in two corrections, one of which was for seven mistakes. I wrote about the mistakes, and Stanleyâ€™s history of error, in a recent <a href="http://www.cjr.org/regret_the_error/wrong_wrong_wrong_wrong_wrong.php#comments">column for Columbia Journalism Review</a>.</p>
<p>Hoytâ€™s column offers new information, such as how five different editors reviewed her story and missed the mistakes. This is a classic example of how easy it is for mistakes to end up in print. It doesnâ€™t matter how many people look at an article; they have to know what theyâ€™re supposed to be looking for.</p>
<p>The most interesting revelation in Hoytâ€™s piece was that, after attention was drawn to Stanleyâ€™s errors in 2005, the Times introduced a program to increase the fact checking of her work:</p>
<blockquote><p><em>For all her skills as a critic, Stanley was the cause of so many corrections in 2005 that she was assigned a single copy editor responsible for checking her facts. Her error rate dropped precipitously and stayed down after the editor was promoted and the arrangement was discontinued. Until the Cronkite errors, she was not even in the top 20 among reporters and editors most responsible for corrections this year. Now, she has jumped to No. 4 and will again get special editing attention. </em></p></blockquote>
<p>The extra scrutiny helped. Then things regressed, and thatâ€™s the lesson here. The gap in the plan for â€œspecial editing attentionâ€ is that it doesnâ€™t include a training component. Stanley could, with a little bit of effort, improve her level of accuracy. Additional oversight isnâ€™t going to train her to be more accurate. It will make her more careful, but it wonâ€™t fix the source of the problem. Eventually she will stop receiving special attention and things will go back to the way they were.</p>
<p>Itâ€™s kind of a variation on the old â€œgive a man a fishâ€ saying:  Give an error-prone reporter special editing attention and youâ€™ll publish fewer of her errors. But train her how to be more accurate and sheâ€™ll make fewer errors.   Thatâ€™s a big difference.</p>
<p>I concluded my CJR column by writing that â€œwhatever system [Stanley] has for checking her work isnâ€™t sufficient. The same goes for how the copy desk is handling her articles. The Times can let her twist in the wind with errors like these, or realize this situation is hurting the organization and come up with a training program that helps her stop making simple factual errors at such an alarming rate.â€</p>
<p>This is, as they say, a teachable moment. Itâ€™s an opportunity for the paper to create a newsroom-wide program that will help all reporters. After all, you canâ€™t give everyone special editing attention. But you can teach good habits that prevent the need for special attention. Eliminate or at least reduce the errors at the source and suddenly there are less things that can slip through the cracks.</p>
<p>After my CJR column appeared online, I received an email from an editor asking me for some error-prevention advice. Hereâ€™s what I sent to him:</p>
<blockquote><p><strong>1. Self-Diagnose:</strong> Are you making or missing the same kinds of errors. Do you misspell names? Garble numbers? Etc. Take a month and track your mistakes. Write them down. Note how they happened and any other relevant information. At the end of the month, tally up your errors. Now you know your pain points. I recommend keeping an error journal; just create an Excel doc or Google Doc spreadsheet and keep track of your errors. This is hugely valuable data. (The Times has an internal errors database, so it already keeps some of this data.)</p>
<p><strong>2. Create Good Habits:</strong> If you have a tendency to misspell names, then you need to start every interview by asking the person to spell their name. If, as an editor, you tend to overlook misspelled names, then the first thing you do with a new story is check the names. The key is to create habits/actions that are mapped to your mistakes. The best way to do this is to&#8230;</p>
<p><strong>3. Use A Checklist:</strong> Whether youâ€™re writing or editing, you should use a checklist to guide your fact checking process. I have a sample checklist available as a free download <a href="http://www.regrettheerror.com/regret-articles/announcing-the-regret-the-error-paperback-and-a-free-accuracy-checklist">here</a>. And if you need convincing, read <a href="http://www.cjr.org/regret_the_error/checklist_charlie.php">this column</a> about why checklists are so powerful.</p></blockquote>
<p>I know one thing for sure: if Alessandra Stanley started using a checklist to review her work prior to sending it for editing, her level of accuracy would improve.</p>
<p><strong>UPDATE August 3:</strong> Steven A. Smith has some good thoughts about this situation <a href="http://www.stillanewspaperman.com/2009/08/03/when-does-inaccuracy-justify-termination/">over on his blog</a>. A sample:</p>
<blockquote><p><em>Reporters with fact-error issues have to work a bit harder, have to develop personal double-checks that can be time-consuming and frustrating, especially on deadline. But that is the only way reporters can work themselves out of an accuracy funk. Some take on the challenge because of professional pride and a genuine desire to do their jobs as well as they can.</em></p>
<p><em>Others require a bigger stick. Thatâ€™s just the truth of it.</em></p>
<p><em>I remember one reporter who worked on my regional staff at The Pioneer Press in St. Paul. He had experienced a terrible run of corrections, all the result of careless reporting practices. Working with him, we developed a series of steps he was urged to take before moving any story to his editors. Within days his desktop computer was covered in yellow sticky notes reminding him to check phone numbers and addresses, use the city directory, and so on. He took responsibility and his hard work produced results. His correction rate dropped dramatically and the new habits stuck with him.</em></p>
<p><em>But the reporter knew his job was on the line. â€˜Fix it or lose itâ€ was the message.</em></p>
<p><em>Was such a message delivered to Stanley at the time her editors developed a personalized editing program? If so, does the latest debacle mean she will lose her job? Should she lose her job?</em></p>
<p><em>Does â€œintellectual heftâ€ in reporting compensate for inaccurate reporting?</em></p></blockquote>
]]></content:encoded>
			<wfw:commentRss>http://www.regrettheerror.com/2009/08/02/nyt-public-editor-addresses-errors-made-in-cronkite-article-some-basic-advice-for-preventing-errors/feed/</wfw:commentRss>
		<slash:comments>13</slash:comments>
		</item>
		<item>
		<title>Wash Post ombud links loss of copy editors to increase in errors</title>
		<link>http://www.regrettheerror.com/2009/07/07/wash-post-ombud-links-loss-of-copy-editors-to-increase-in-errors/</link>
		<comments>http://www.regrettheerror.com/2009/07/07/wash-post-ombud-links-loss-of-copy-editors-to-increase-in-errors/#comments</comments>
		<pubDate>Tue, 07 Jul 2009 12:00:35 +0000</pubDate>
		<dc:creator>Craig Silverman</dc:creator>
				<category><![CDATA[Behind the scenes]]></category>
		<category><![CDATA[Newspapers]]></category>
		<category><![CDATA[Ombudsmen]]></category>
		<category><![CDATA[copy editing]]></category>
		<category><![CDATA[correction tallies]]></category>
		<category><![CDATA[error tracking]]></category>
		<category><![CDATA[quality revolution]]></category>
		<category><![CDATA[washington post]]></category>

		<guid isPermaLink="false">http://www.regrettheerror.com/?p=8503</guid>
		<description><![CDATA[Just over two years ago, the public editor of the Orlando Sentinel wrote a column alerting readers to the fact that the paper had experienced a spike in the number of corrections. He was clear about the cause of the increased errors: When the Sentinel tightened its financial belt back in June, it lost a [...]]]></description>
			<content:encoded><![CDATA[<p><img height="28" width="138" class="alignnone size-full wp-image-6574" title="washpost4" alt="washpost4" src="http://www.regrettheerror.com/wp-content/uploads/2008/11/washpost4.gif" />Just over two years ago, the public editor of the Orlando Sentinel wrote a <a href="http://www.regrettheerror.com/newspapers/orlando-sentinel-sees-corrections-rise-at-frightening-pace-the-quality-revolution">column</a> alerting readers to the fact that the paper had experienced a spike in the number of corrections. He was clear about the cause of the increased errors:</p>
<blockquote>
<p><em>When the Sentinel tightened its financial belt back in June, it lost a wealth of seasoned veterans, many of them editors. Those journalists not only wrote headlines and captions. They also scrutinized the work of reporters &mdash; correcting spelling, straightening out syntax, double-checking facts &mdash; before publication.<br />
With fewer people to do that now, less of that important work gets done, and the result is more published errors.</em></p>
</blockquote>
<p>Yesterday, the ombudsman of the Washington Post wrote basically the same <a href="http://www.washingtonpost.com/wp-dyn/content/article/2009/07/03/AR2009070301129_pf.html">column</a>:</p>
<blockquote>
<p><em>&#8230;Growing numbers of readers are contacting the ombudsman to complain about typos and small errors.</em></p>
<p><em>&quot;As a virtually lifelong subscriber, I am disheartened by the increasingly poor quality of the editing of The Post,&quot; wrote Richard Murphy of Alexandria. If typos can&#8217;t be caught by a spell-checker, &quot;then The Post should restore a couple of copy editor positions. You have cut that staff too much.&quot;</em></p>
<p><em>The Post&#8217;s copy editors are among the best I&#8217;ve worked with during nearly four decades in the newspaper business. But they&#8217;ve been badly depleted by staff cuts as the money-losing paper struggles to control costs. Those who remain are stretched thin while The Post expands to a 24-hour news operation in print and online.</em></p>
<p><em>Between early 2005 and mid-2008, the number of full-time copy editors dropped from about 75 to 43 through buyouts or voluntary departures. It has declined further since then, but Post managers won&#8217;t provide precise figures beyond saying that six took a recent buyout offer. The need is so critical that most are being hired back on contract through at least the end of the year, and part-timers are taking up some of the slack.</em></p>
<p><em>Copy editors are the unsung heroes of newsrooms. Unknown to the public, and often underappreciated by their colleagues, they&#8217;re the last line of defense against a correction or, worse, a libel suit&#8230;</em></p>
<p><em>&quot;By definition, you&#8217;ll see more errors when there&#8217;s reduced staffing,&quot; said Bill Walsh, the A-section copy desk chief. On a typical weeknight a few years ago, Walsh said, the three copy desks handling national, foreign and business news could rely on perhaps 20 editors. Those desks have since been combined into one desk, headed by Walsh. Today, he said, &quot;there are some shifts where I&#8217;m looking at seven or eight people total.&quot;&#8230;</em></p>
</blockquote>
<p>These papers are by no means the only ones experiencing a spike in errors due to the loss of bodies on the copy desk. Adding to the problem is the fact that the move online means papers are churning out more content than ever before. Yet copy editors &#8212; and magazine fact checkers &#8212; are being shown the door.</p>
<p>Carl Sessions Stepp examined how some newsrooms are coping with this challenge is his recent article, &quot;<a target="_blank" href="http://www.ajr.org/Article.asp?id=4742">The Quality-Control Quandary,&rdquo;</a> It&#8217;s a must-read. I fear, though, that few organizations are rethinking their quality control process and means of verification. They&#8217;re just trying to do more with less. It&#8217;s a recipe for disaster.</p>
<p>I looked at this issue in a recent <a href="http://www.nieman.harvard.edu/reportsitem.aspx?id=100948">essay</a> I wrote for Harvard&#8217;s <strike>Niemen</strike> Neiman Reports:</p>
<blockquote>
<p><em>For more than 100 years, one of the most recognizable slogans in journalism has been &ldquo;All the News That&rsquo;s Fit to Print.&rdquo; Lately, The New York Times motto is being challenged by the familiar phrase, &ldquo;do more with less.&rdquo; This new saying was, in fact, the theme of the World Editors Forum scheduled for March, but the event had to be cancelled &ldquo;due to the impact of the global financial downturn on newspaper companies.&rdquo;</p>
<p>News organizations are shedding employees. Those that remain are expected to pick up the slack and also push ahead with digital initiatives. Included in the exodus are valuable copyeditors&mdash;the people in whose encyclopedic brains reside a lot of what prevents errors from surfacing in stories. The few, the proud&mdash;and disappearing&mdash;magazine fact checkers are also being told to grab their World Almanacs and Book of Facts and move along.</p>
<p>Accuracy is a huge journalistic challenge. When reporters are asked to take on more work while the newsroom&rsquo;s same fallible processes and error-prone technologies remain in place, the result will undoubtedly be a further downward slide in quality. More errors will be followed by more apologies and more corrections. And this is happening at a critical time for journalism&mdash;a time when consumers are being asked by journalists using digital media to lend support to their newsgathering mission&#8230;</em></p>
</blockquote>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.regrettheerror.com/2009/07/07/wash-post-ombud-links-loss-of-copy-editors-to-increase-in-errors/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>What IT security can teach us about accuracy</title>
		<link>http://www.regrettheerror.com/2007/11/15/what-it-security-can-teach-us-about-accuracy/</link>
		<comments>http://www.regrettheerror.com/2007/11/15/what-it-security-can-teach-us-about-accuracy/#comments</comments>
		<pubDate>Thu, 15 Nov 2007 12:00:04 +0000</pubDate>
		<dc:creator>Craig Silverman</dc:creator>
				<category><![CDATA[Regret Articles]]></category>
		<category><![CDATA[error prevention]]></category>
		<category><![CDATA[error tracking]]></category>
		<category><![CDATA[Fabrication]]></category>
		<category><![CDATA[Plagiarism]]></category>
		<category><![CDATA[quality revolution]]></category>

		<guid isPermaLink="false">http://www.regrettheerror.com/regret-articles/what-it-security-can-teach-us-about-accuracy</guid>
		<description><![CDATA[Bruce Schneier, one of the leading thinkers in IT security, recently wrote a column for Wired.com in which he uses the example of corrupt NBA referee Tim Donaghy to examine systems that suffer from single points of failure. The same concept directly relates to journalism and accuracy. What sorts of systems &#8212; IT, financial, NBA [...]]]></description>
			<content:encoded><![CDATA[<p>Bruce Schneier, one of the leading thinkers in IT security, recently wrote a <a href="http://www.wired.com/politics/security/commentary/securitymatters/2007/09/securitymatters_0906">column</a> for Wired.com in which he uses the example  of corrupt NBA referee Tim Donaghy to examine systems that suffer from single points of failure. The same concept directly relates to journalism and accuracy.</p>
<blockquote><p><em>What sorts of systems &#8212; IT, financial, <a href="http://msn.foxsports.com/nba/story/7047984">NBA games</a> or whatever &#8212; are most at risk of being manipulated? The ones where the smallest change can have the greatest impact, and the ones where <a href="http://sports.espn.go.com/espn/blog/index?entryID=2979711&amp;name=sheridan_chris">trusted insiders</a> can make that change. </em></p></blockquote>
<p>Donaghy used his position to try and influence the outcome of games, and he was able to because of the way the NBA games operate:</p>
<blockquote><p><em>Because individual players matter so much, a single referee can <a href="http://sports.espn.go.com/nba/news/story?page=expertexplainsNBAbets">affect a basketball game</a> more than he can in any other sport. Referees call fouls. Contact occurs on nearly every play, any of which could be called as a foul. They&#8217;re called &#8220;touch fouls,&#8221; and they are mostly, but not always, ignored. The refs get to decide which ones to call. </em></p></blockquote>
<p>Schneier lists other examples of jobs where people are &#8220;both trusted insiders and single points of catastrophic failure.&#8221; It could be a &#8220;dishonest computer-repair technician&#8230;a corrupt judge, police officer, customs inspector, border-control officer, food-safety inspector&#8230;&#8221;</p>
<p>Or a journalist. Newsrooms build in layers of auditing in an attempt to mitigate the ability of a trusted insider to subvert the system: copy editors, assignment editors etc. But each person in the chain of audit (editing process) is both a point of quality control and a potential point of failure. We then attempt to mitigate that reality by requiring reporters to take notes or record interviews, cite sources, and talk to experts.</p>
<p>Yet we still see people like Jayson Blair and Stephen Glass, trusted insiders who become single points of catastrophic failure. Incidents of plagiarism, fabrication, and extreme error abound. Clearly, we need to evolve our audit systems. The current reality of <a href="http://www.regrettheerror.com/newspapers/orlando-sentinel-sees-corrections-rise-at-frightening-pace-the-quality-revolution">shrunken newsrooms</a> &#8212; and therefore reduced audit controls &#8212; makes it even more imperative that we innovate new ways of ensuring quality. The speed of online news also requires us to find ways to do it at a faster pace.</p>
<p>Yes, a tough challenge. But an exciting one, too.</p>
<p>&#8220;All systems have trusted insiders,&#8221; according to Schneier. &#8220;All systems have catastrophic points of failure. The key is recognizing them, and building monitoring and audit systems to secure them.&#8221;</p>
<p>So what does the ideal newsroom monitoring and auditing system look like? Likely a combination of prevention &#8212; fact checking, plagiarism detection, training, editing etc.  &#8212; mixed with post-publication/post-broadcast error tracking and analysis.  These elements demand a mix of people, processes and technology. The challenge is creating the right mix and then constantly managing, evolving and improving the system.</p>
<p>It&#8217;s a difficult  task, but the status quo is a recipe for repeated &#8220;catastrophic failures.&#8221;</p>
<p>Would you keep following the NBA if you knew another Tim Donaghy was inevitable?</p>
<p><em>Have an idea for newsroom auditing? Share it in the comments. </em></p>
]]></content:encoded>
			<wfw:commentRss>http://www.regrettheerror.com/2007/11/15/what-it-security-can-teach-us-about-accuracy/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>More on the Times&#8217; corrections database</title>
		<link>http://www.regrettheerror.com/2007/11/01/more-on-the-times-corrections-database/</link>
		<comments>http://www.regrettheerror.com/2007/11/01/more-on-the-times-corrections-database/#comments</comments>
		<pubDate>Thu, 01 Nov 2007 12:00:21 +0000</pubDate>
		<dc:creator>Craig Silverman</dc:creator>
				<category><![CDATA[Behind the scenes]]></category>
		<category><![CDATA[Newspapers]]></category>
		<category><![CDATA[corrections database]]></category>
		<category><![CDATA[corrections tallies]]></category>
		<category><![CDATA[error tracking]]></category>
		<category><![CDATA[new york times]]></category>

		<guid isPermaLink="false">http://www.regrettheerror.com/newspapers/more-on-the-times-corrections-database/</guid>
		<description><![CDATA[CheckYourFacts.org has expanded on a previous report about the recently-launched New York Times corrections database. The new story offers more details about how the database works and how the paper will use it to track and improve accuracy. It also includes an interview with Greg Brock, the senior editor who oversees the database and the [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://checkyourfacts.org"><img src="http://graphics8.nytimes.com/images/misc/nytlogo153x23.gif" align="left" height="23" width="153" />CheckYourFacts.org</a> has expanded on a <a href="http://www.regrettheerror.com/newspapers/ny-times-corrections-database-goes-live/">previous report </a>about the recently-launched New York Times corrections database. The <a href="http://checkyourfacts.org/latest-journalism-news-updates-57.php">new story </a>offers more details about how the database works and how the paper will use it to track and improve accuracy. It also includes an interview with Greg Brock, the senior editor who oversees the database and the paper&#8217;s corrections. Reports CYF:</p>
<blockquote><p>&#8230;The new Times database holds comprehensive information about the nature of errors made by reporters and editors. The editors fill in a number of fields, starting with where the error occurred (in a column, an article, a caption, a headline, a photo, or even a byline).<br />
Next, they enter the field â€œidentified by,â€ which names the person who called the error to their attention. The paper previously had no record of this information, which is particularly important for understanding the source of more questionable corrections.<br />
The field â€œoriginatorâ€ points to person who came up with the story in question. â€œCategoryâ€ lists the type of correction printed, usually â€œFor the Record,â€ â€œA Correction,â€ or â€œEditorâ€™s Notes.â€ Finally, the editor enters the person responsible, and a section for miscellaneous notes for pertinent information that does not fit anywhere else.</p></blockquote>
<p>Sounds like the paper, which had to scrap an earlier version of the system, is gathering the appropriate information. One more thing:</p>
<blockquote><p> Brock says the system will also allow the paper to track another common mistake made by reporters: using uncorroborated information from the Internet in their articles. â€œPeople turn to the Internet with a quick Google search, and put â€˜Fact Xâ€™ in an article,â€ says Brock. â€œWe know thatâ€™s happening, and weâ€™ve asked people to please not do that.â€</p></blockquote>
<p>Nice. The subsequent interview with Brock also has him explaining how the paper will use the data it collects to make decisions for the paper. This is really key:</p>
<blockquote><p>The purpose of this one is to pinpoint certain types of errors and how theyâ€™re happening. For instance, if we discover that â€œDepartment Xâ€ is having a lot of errors appearing in the Monday paper, it would probably tell us right off the bat that theyâ€™re lightly staffed on Sundays, and might need more help. It might be a department that, like â€œCulture,â€ for instance, would be putting out a Monday paper that has a lot of articles that are prepared in advance. Perhaps they should have come in on Friday, but maybe are coming in late on Sunday afternoon. So, we can pinpoint a problem area.</p></blockquote>
<p>It&#8217;s essential that the database is not only used to deliver a simple numerical tally. Its data should be put to use in evaluating reporters, finding weak spots in sections, and making staffing decisions. If a section&#8217;s head count goes down and the number of corrections spikes, then managers can see the effect that resources, and a lack thereof, have on accuracy.<br />
Another topic of conversation with Brock is how this system could possibly catch another Jayson Blair-type earlier on. He notes that Blair &#8220;had 50 some corrections, but no one person knew. This department would use him, and he made a few errors. Then, another department would use him, and heâ€™d made some more. And then when he got handed off in National, they didnâ€™t know, and there was really no way to check. Plus, I donâ€™t think anybody thought to check, frankly.&#8221;<br />
The lack of a centralized system was certainly a factor, but there&#8217;s also the issue of severity to consider. Blair may have had a lot of corrections, but early on he had two back-to-back corrections that were the result of highly unethical behavior on his part. The first correction, from Oct. 23, 2001:</p>
<blockquote><p>AN ARTICLE IN SOME COPIES on Sunday about a benefit at Madison Square Garden for victims of the Sept. 11 terror attack misstated the price of the most expensive tickets. They were $10,000, not $1,000.<br />
The article also quoted incorrectly from a remark by former President Bill Clinton to the audience, many of them police officers and firefighters. Mr. Clinton said he had been given the bracelet of Raymond Downey, the deputy fire chief who died in the attackâ€”not Chief Downey&#8217;s hat.<br />
Referring to the terrorists, he said, â€œI hope they saw this tonight, because they thought America was about money and power. They thought that if they took down the World Trade Center, we would collapse. But weâ€™re not about mountains of money or towers of steel. Youâ€™re about mountains of courage and hearts of gold, and I hope they saw you here tonight.â€ He did not say â€œhearts of steel.â€</p></blockquote>
<p>It was followed by another the next day:</p>
<blockquote><p>AN ARTICLE IN SOME LATE EDITIONS on Sunday about the benefit concert at Madison Square Garden for victims of the Sept. 11 attack referred incorrectly to scenes in a short film made for the event by Woody Allen, â€œScenes from a Town I Love,â€ which showed New Yorkers talking on cell phones. An actor in one scene complained that his anthrax drugs had been stolen by muggers; he did not say the police took them.<br />
Another man talked about opening Starbucks coffee shops in Afghanistan after the war; he did not say one had already opened there.<br />
The article also included two performers erroneously among the participants. Bono and the Edge, of the band U2, were scheduled to appear but canceled before the concert.</p></blockquote>
<p>Blair hadn&#8217;t gone to the concert at all. He watched it on TV while drinking at a bar, and then just sent in a story as if he had been there. His editor found out and gave him a â€œa formal reprimand,â€ according to <a href="http://www.sethmnookin.com/">Seth Mnookin&#8217;s</a> <a href="http://www.sethmnookin.com/hardnews/index.php">book</a> about the scandal. But Blair remained at the paper for more than two more years before resigning in the face of growing accusations. So, aside from treating such egregious lapses in a more serious manner, perhaps the Times database could also include a means of rating the severity of an error?<br />
Obviously, this is a subjective criteria. But frequency alone isn&#8217;t the only issue to consider. Content also matters.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.regrettheerror.com/2007/11/01/more-on-the-times-corrections-database/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>NY Times corrections database goes live</title>
		<link>http://www.regrettheerror.com/2007/10/12/ny-times-corrections-database-goes-live/</link>
		<comments>http://www.regrettheerror.com/2007/10/12/ny-times-corrections-database-goes-live/#comments</comments>
		<pubDate>Fri, 12 Oct 2007 23:01:00 +0000</pubDate>
		<dc:creator>Craig Silverman</dc:creator>
				<category><![CDATA[Behind the scenes]]></category>
		<category><![CDATA[Newspapers]]></category>
		<category><![CDATA[Regret Articles]]></category>
		<category><![CDATA[correction database]]></category>
		<category><![CDATA[correction tallies]]></category>
		<category><![CDATA[error tracking]]></category>
		<category><![CDATA[new york times]]></category>

		<guid isPermaLink="false">http://regrettheerrorbook.com/uncategorized/ny-times-corrections-database-goes-live/</guid>
		<description><![CDATA[The good folks at Check Your Facts recently published an item stating that the roll out of the New York Times internal corrections database is complete. The paper is now entering all of its corrections into a central database, much like how the Boston Globe, Rocky Mountain News and a few other US papers have [...]]]></description>
			<content:encoded><![CDATA[<p><img src="http://www.regrettheerror.com/wp-content/uploads/2007/10/nytbanner.thumbnail.gif" />The good folks at <a href="http://checkyourfacts.org">Check Your Facts</a> recently <a href="http://checkyourfacts.org/latest-journalism-news-updates-56.php">published an item</a> stating that the roll out of the New York Times internal corrections database is complete. The paper is now entering all of its corrections into a central database, much like how the Boston Globe, Rocky Mountain News and a few other US papers have been doing. Reports CYF:</p>
<blockquote><p> Check Your Facts has learned that the <em>New York Times</em> may finally be making good on one of the recommendations laid out in a 2005 report titled <a href="http://64.233.169.104/search?q=cache:6YxD8wd474YJ:www.nytco.com/pdf/siegal-report050205.pdf+%22preserving+our+readers%22&amp;hl=en&amp;ct=clnk&amp;cd=1&amp;gl=us&amp;client=firefox-a">â€œPreserving Our Readersâ€™ Trust.â€</a><br />
Fresh from a &#8220;training class,&#8221; a well-placed source at the Times says a computerized tracking system for corrections is being implemented. Correspondent Adam Klasfeld learned of the new system through correspondence with a <em>New York Times </em>editor (Check Your Facts is withholding the editor&#8217;s name in order to maintain open communications on the matter). The NYT editor said that no tracking system as described in the report currently exists but that a â€œtraining classâ€ was held for a new system. â€œWe are just implementing it,â€ wrote the editor. â€œWe are beginning with corrections on October 1.â€</p></blockquote>
<p>We <a href="http://www.regrettheerror.com/2006/12/advances_in_onl.html">reported</a> on the roll out of the system in December of last year after speaking with Greg Brock, the paper&#8217;s corrections editor:</p>
<blockquote><p>A final note from the Times: Brock says the paper does have a corrections database that is being used by some departments. Each department can see its own corrections tally, and Brock has access to the total data. He says they are working to roll it out within all departments. This database was one of the recommendations of the <a href="http://www.regrettheerror.com/2005/05/our_take_on_the.html">Siegal Committee</a>. It&#8217;s good to see the paper following up on this project. We hope it&#8217;s fully operational ASAP.</p></blockquote>
<p>In an email response this week, Brock said the system was fully operational as of September 17. &#8220;So it is in place, though we are continuing to train editors who will use it only occasionally because they work on sections or special issues of magazines that publish just a few times a year,&#8221; he wrote. &#8220;The main news desks are already using it.&#8221;</p>
<p>We asked if the paper plans to release its tallies the way some other paper do (see these links: <a href="http://www.regrettheerror.com/2007/01/2006_correction.html">1</a>, <a href="http://www.regrettheerror.com/2006/01/2005_correction.html">2</a>, <a href="http://www.regrettheerror.com/2006/12/an_early_correc.html">3</a>, <a href="http://www.regrettheerror.com/2005/12/arizona_daily_s.html">4</a>), and Brock said the issue hadn&#8217;t yet been raised, but that he would look into it. As of now, he is distributing reports to the relevant editors on a monthly, quarterly, and annual basis in order to show them the most common types of errors in their sections. It&#8217;s good to hear the data is being put to use to help fuel preventative initiatives.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.regrettheerror.com/2007/10/12/ny-times-corrections-database-goes-live/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

