<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Updating archives to protect the innocent</title>
	<atom:link href="http://www.lostremote.com/2008/06/18/updating-archives-to-protect-the-innocent/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.lostremote.com/2008/06/18/updating-archives-to-protect-the-innocent/</link>
	<description>Where TV Finds the Future</description>
	<pubDate>Tue, 02 Dec 2008 22:54:02 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Anonymous</title>
		<link>http://www.lostremote.com/2008/06/18/updating-archives-to-protect-the-innocent/#comment-1036708</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Fri, 20 Jun 2008 10:33:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.lostremote.com/?p=5125#comment-1036708</guid>
		<description>You should try that for Usenet.</description>
		<content:encoded><![CDATA[<p>You should try that for Usenet.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://www.lostremote.com/2008/06/18/updating-archives-to-protect-the-innocent/#comment-1035860</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Thu, 19 Jun 2008 21:51:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.lostremote.com/?p=5125#comment-1035860</guid>
		<description>People have an insane idea as to how much effort this would take or the magnitude of what's being suggested. This is obviously not something that comes up very often AT ALL. There is ZERO liability here, unless the original article was defamatory to begin with. It's a freaking extra sentence a couple times a year, people, and it's the respectable thing to do.</description>
		<content:encoded><![CDATA[<p>People have an insane idea as to how much effort this would take or the magnitude of what&#8217;s being suggested. This is obviously not something that comes up very often AT ALL. There is ZERO liability here, unless the original article was defamatory to begin with. It&#8217;s a freaking extra sentence a couple times a year, people, and it&#8217;s the respectable thing to do.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ed</title>
		<link>http://www.lostremote.com/2008/06/18/updating-archives-to-protect-the-innocent/#comment-1035772</link>
		<dc:creator>Ed</dc:creator>
		<pubDate>Thu, 19 Jun 2008 20:48:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.lostremote.com/?p=5125#comment-1035772</guid>
		<description>@Grimmy: "The smart thing to do is to link your related stories together so that someone can follow the path of the story to see the eventual outcome."

And a good CMS/publishing system should provide that feature, allowing you to relate stories together in a way that makes it seamless, and automatic.</description>
		<content:encoded><![CDATA[<p>@Grimmy: &#8220;The smart thing to do is to link your related stories together so that someone can follow the path of the story to see the eventual outcome.&#8221;</p>
<p>And a good CMS/publishing system should provide that feature, allowing you to relate stories together in a way that makes it seamless, and automatic.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Grimmy</title>
		<link>http://www.lostremote.com/2008/06/18/updating-archives-to-protect-the-innocent/#comment-1035715</link>
		<dc:creator>Grimmy</dc:creator>
		<pubDate>Thu, 19 Jun 2008 20:06:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.lostremote.com/?p=5125#comment-1035715</guid>
		<description>No updates.  The person was charged with a crime at that point in time.  A later acquittal does not change that fact.

You have to look at stories as a moment in time. At the time the story was published, it contained the facts available at that time.

The smart thing to do is to link your related stories together so that someone can follow the path of the story to see the eventual outcome.</description>
		<content:encoded><![CDATA[<p>No updates.  The person was charged with a crime at that point in time.  A later acquittal does not change that fact.</p>
<p>You have to look at stories as a moment in time. At the time the story was published, it contained the facts available at that time.</p>
<p>The smart thing to do is to link your related stories together so that someone can follow the path of the story to see the eventual outcome.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Capt</title>
		<link>http://www.lostremote.com/2008/06/18/updating-archives-to-protect-the-innocent/#comment-1035634</link>
		<dc:creator>Capt</dc:creator>
		<pubDate>Thu, 19 Jun 2008 19:15:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.lostremote.com/?p=5125#comment-1035634</guid>
		<description>I say no updates to the main story. Write a second story and add a link in the first to the update. 

I believe strongly in a paper trail. Changing the original destroys that trail.</description>
		<content:encoded><![CDATA[<p>I say no updates to the main story. Write a second story and add a link in the first to the update. </p>
<p>I believe strongly in a paper trail. Changing the original destroys that trail.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Orren</title>
		<link>http://www.lostremote.com/2008/06/18/updating-archives-to-protect-the-innocent/#comment-1035210</link>
		<dc:creator>Mike Orren</dc:creator>
		<pubDate>Thu, 19 Jun 2008 14:45:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.lostremote.com/?p=5125#comment-1035210</guid>
		<description>Glad to see my post sparked some debate -- Seem to be some misconceptions here about what we do that I want to clear up.

Primary is this: We never alter old copy. We do one of two things: 1. Post a new story and link it to the old one. In our CMS, that automatically puts a related link to the new story, including the headline in the old; 2. Post no new story and just post an update line in the old.

&lt;a href="http://www.pegasusnews.com/news/2007/jun/13/euless-man-jailed-sexually-assaulting-possibly-dru/" rel="nofollow"&gt;Example of the latter.&lt;/a&gt;

Our stories are publicly timestamped twice. Once with the posting and again with the most recent update. When updated, the story gets kicked back to the various hubpages and/or homepage as if it was new. (Note we don't mark updated if we've just fixed a typo)

Even though we're all-digital, I come from a print background. I wrestled with some of the questions above, but in practice...

"My mindset as a developer/journalist would be to datestamp each story anyway, so as to justify the datedness of the original story, and then provide some sort of “related items” collection within the larger article as a sidebar to at least try and expose more recent coverage of the storyline."

Pretty close to what we do.

"What if the media outlet doesn’t report an update through their main channel, so there’d be no new informaton to link?"

Link to (horrors!) another outlet or just post it as new reporting.

"1) What types of information need to be retroactively added to stories? Ok, so maybe an acquittal in a murder case is obvious, but what about not-so-serious things? “Johnson’s Baby Oil Might Cause Itchiness — UPDATE: No, it doesn’t.” “Local Shoe Store Nears Bankruptcy — UPDATE: They were bought out by Payless”"

Actually, the biggest learning for us is how much this liberates you from posting endless inverted pyramid updates. So if the story is "Council to vote on x tonight" and it happens without controversy, SO much more efficient just to update old story with "They decided Y".

"Yes, but I would argue that the fundamental dynamic has not changed." 

Go Google some names of acquitted accused in your area. Results will argue that the fundamental dynamic has turned upside down. Google search for "YourName" is now a national publication about you.</description>
		<content:encoded><![CDATA[<p>Glad to see my post sparked some debate &#8212; Seem to be some misconceptions here about what we do that I want to clear up.</p>
<p>Primary is this: We never alter old copy. We do one of two things: 1. Post a new story and link it to the old one. In our CMS, that automatically puts a related link to the new story, including the headline in the old; 2. Post no new story and just post an update line in the old.</p>
<p><a href="http://www.pegasusnews.com/news/2007/jun/13/euless-man-jailed-sexually-assaulting-possibly-dru/" rel="nofollow">Example of the latter.</a></p>
<p>Our stories are publicly timestamped twice. Once with the posting and again with the most recent update. When updated, the story gets kicked back to the various hubpages and/or homepage as if it was new. (Note we don&#8217;t mark updated if we&#8217;ve just fixed a typo)</p>
<p>Even though we&#8217;re all-digital, I come from a print background. I wrestled with some of the questions above, but in practice&#8230;</p>
<p>&#8220;My mindset as a developer/journalist would be to datestamp each story anyway, so as to justify the datedness of the original story, and then provide some sort of “related items” collection within the larger article as a sidebar to at least try and expose more recent coverage of the storyline.&#8221;</p>
<p>Pretty close to what we do.</p>
<p>&#8220;What if the media outlet doesn’t report an update through their main channel, so there’d be no new informaton to link?&#8221;</p>
<p>Link to (horrors!) another outlet or just post it as new reporting.</p>
<p>&#8220;1) What types of information need to be retroactively added to stories? Ok, so maybe an acquittal in a murder case is obvious, but what about not-so-serious things? “Johnson’s Baby Oil Might Cause Itchiness — UPDATE: No, it doesn’t.” “Local Shoe Store Nears Bankruptcy — UPDATE: They were bought out by Payless”&#8221;</p>
<p>Actually, the biggest learning for us is how much this liberates you from posting endless inverted pyramid updates. So if the story is &#8220;Council to vote on x tonight&#8221; and it happens without controversy, SO much more efficient just to update old story with &#8220;They decided Y&#8221;.</p>
<p>&#8220;Yes, but I would argue that the fundamental dynamic has not changed.&#8221; </p>
<p>Go Google some names of acquitted accused in your area. Results will argue that the fundamental dynamic has turned upside down. Google search for &#8220;YourName&#8221; is now a national publication about you.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brink</title>
		<link>http://www.lostremote.com/2008/06/18/updating-archives-to-protect-the-innocent/#comment-1035190</link>
		<dc:creator>Brink</dc:creator>
		<pubDate>Thu, 19 Jun 2008 14:33:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.lostremote.com/?p=5125#comment-1035190</guid>
		<description>Darn near every single story on your website could be updated as condition change. How many people are you going to employ to continously update all 75,000 (and counting) stories in your archives so they are all "up to date?"</description>
		<content:encoded><![CDATA[<p>Darn near every single story on your website could be updated as condition change. How many people are you going to employ to continously update all 75,000 (and counting) stories in your archives so they are all &#8220;up to date?&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gorman</title>
		<link>http://www.lostremote.com/2008/06/18/updating-archives-to-protect-the-innocent/#comment-1035169</link>
		<dc:creator>Gorman</dc:creator>
		<pubDate>Thu, 19 Jun 2008 14:20:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.lostremote.com/?p=5125#comment-1035169</guid>
		<description>Doesn't an organization open itself up from a liability standpoint once it starts doing this? An organization is bound to miss a story, and someone's going to take them to court saying "They didn't update the article involving me like they updated all these others, and it's caused me irreparable harm."</description>
		<content:encoded><![CDATA[<p>Doesn&#8217;t an organization open itself up from a liability standpoint once it starts doing this? An organization is bound to miss a story, and someone&#8217;s going to take them to court saying &#8220;They didn&#8217;t update the article involving me like they updated all these others, and it&#8217;s caused me irreparable harm.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim</title>
		<link>http://www.lostremote.com/2008/06/18/updating-archives-to-protect-the-innocent/#comment-1035088</link>
		<dc:creator>Jim</dc:creator>
		<pubDate>Thu, 19 Jun 2008 13:49:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.lostremote.com/?p=5125#comment-1035088</guid>
		<description>If the story needs to be updated within the same day, then updates are fine. For example, a fire is raging and initial reports have two dead. If during the same time frame that the fire is being fought a third body is found, then continue to add to the story. If, however, we're talking about an arrest, and then three months later there is a trial that finds the person not guilty -- a new story should be written that can link back to the first story, but both stories should stand alone.</description>
		<content:encoded><![CDATA[<p>If the story needs to be updated within the same day, then updates are fine. For example, a fire is raging and initial reports have two dead. If during the same time frame that the fire is being fought a third body is found, then continue to add to the story. If, however, we&#8217;re talking about an arrest, and then three months later there is a trial that finds the person not guilty &#8212; a new story should be written that can link back to the first story, but both stories should stand alone.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rocker</title>
		<link>http://www.lostremote.com/2008/06/18/updating-archives-to-protect-the-innocent/#comment-1035081</link>
		<dc:creator>Rocker</dc:creator>
		<pubDate>Thu, 19 Jun 2008 13:46:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.lostremote.com/?p=5125#comment-1035081</guid>
		<description>This is obvious so I'm surprised nobody has pointed it out yet...the ability to read old stories that haven't been updated is not new.  Libraries have archived old newspapers forever, and those have long been available to the public (remember microfiches?)  Are un-updated stories more accessible now via the net?  Yes, but I would argue that the fundamental dynamic has not changed.  And besides the practical issues involved with trying to update everything retroactively, something about going back and re-write the record makes me profoundly uncomfortable - I guess you could say from a historical/historian's p.o.v. (not claiming to be a historian!).</description>
		<content:encoded><![CDATA[<p>This is obvious so I&#8217;m surprised nobody has pointed it out yet&#8230;the ability to read old stories that haven&#8217;t been updated is not new.  Libraries have archived old newspapers forever, and those have long been available to the public (remember microfiches?)  Are un-updated stories more accessible now via the net?  Yes, but I would argue that the fundamental dynamic has not changed.  And besides the practical issues involved with trying to update everything retroactively, something about going back and re-write the record makes me profoundly uncomfortable - I guess you could say from a historical/historian&#8217;s p.o.v. (not claiming to be a historian!).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://www.lostremote.com/2008/06/18/updating-archives-to-protect-the-innocent/#comment-1034791</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Thu, 19 Jun 2008 10:26:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.lostremote.com/?p=5125#comment-1034791</guid>
		<description>Slippery slope arguments are logical fallacies. Guidelines such as these could help: Updates could be considered upon request. The applicant should be otherwise relatively low-profile, not a corporation, celebrity, or other high-profile individual seeking publicity enhancement. The story would have to suggest the possibility of wrongdoing. And the applicant would have to provide official new information to the contrary, such as dropped charges, charges against someone else, an acquittal, etc. The news outlet could then make a brief note of, or link to, the new information as an update. These are only suggestions.</description>
		<content:encoded><![CDATA[<p>Slippery slope arguments are logical fallacies. Guidelines such as these could help: Updates could be considered upon request. The applicant should be otherwise relatively low-profile, not a corporation, celebrity, or other high-profile individual seeking publicity enhancement. The story would have to suggest the possibility of wrongdoing. And the applicant would have to provide official new information to the contrary, such as dropped charges, charges against someone else, an acquittal, etc. The news outlet could then make a brief note of, or link to, the new information as an update. These are only suggestions.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: db</title>
		<link>http://www.lostremote.com/2008/06/18/updating-archives-to-protect-the-innocent/#comment-1034518</link>
		<dc:creator>db</dc:creator>
		<pubDate>Thu, 19 Jun 2008 07:21:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.lostremote.com/?p=5125#comment-1034518</guid>
		<description>This could get very tricky to effectively implement.

1) What types of information need to be retroactively added to stories?  Ok, so maybe an acquittal in a murder case is obvious, but what about not-so-serious things?  "Johnson's Baby Oil Might Cause Itchiness --- UPDATE: No, it doesn't."  "Local Shoe Store Nears Bankruptcy --- UPDATE: They were bought out by Payless"

2) What about stories that are extensively covered?  For example, some stations in the D.C. area probably cranked out a half-dozen stories a day for several weeks related to the sniper shootings; do they all need to be updated?</description>
		<content:encoded><![CDATA[<p>This could get very tricky to effectively implement.</p>
<p>1) What types of information need to be retroactively added to stories?  Ok, so maybe an acquittal in a murder case is obvious, but what about not-so-serious things?  &#8220;Johnson&#8217;s Baby Oil Might Cause Itchiness &#8212; UPDATE: No, it doesn&#8217;t.&#8221;  &#8220;Local Shoe Store Nears Bankruptcy &#8212; UPDATE: They were bought out by Payless&#8221;</p>
<p>2) What about stories that are extensively covered?  For example, some stations in the D.C. area probably cranked out a half-dozen stories a day for several weeks related to the sniper shootings; do they all need to be updated?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: discreet_chaos</title>
		<link>http://www.lostremote.com/2008/06/18/updating-archives-to-protect-the-innocent/#comment-1034305</link>
		<dc:creator>discreet_chaos</dc:creator>
		<pubDate>Thu, 19 Jun 2008 04:58:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.lostremote.com/?p=5125#comment-1034305</guid>
		<description>Seth's comment brings up an interesting queston -- What if the media outlet doesn't report an update through their main channel, so there'd be no new informaton to link?</description>
		<content:encoded><![CDATA[<p>Seth&#8217;s comment brings up an interesting queston &#8212; What if the media outlet doesn&#8217;t report an update through their main channel, so there&#8217;d be no new informaton to link?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Seth Keever</title>
		<link>http://www.lostremote.com/2008/06/18/updating-archives-to-protect-the-innocent/#comment-1034189</link>
		<dc:creator>Seth Keever</dc:creator>
		<pubDate>Thu, 19 Jun 2008 03:19:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.lostremote.com/?p=5125#comment-1034189</guid>
		<description>I think it should be updated in a web story, especially if the television counterpart updates the story on the air.

If the story isn't furthered on television, the majority of the public won't know or care. Most people will have forgotten about the case. But the Internet isn't a linear medium like TV.

10 years from now, someone could be searching for that person and come across the story. They'll find that this person was arrested/charged, and not know they're actually guilty. In the reader's mind, they're guilty, and that's their sole take-away from the article. The reader should be provided with all of the facts.

Even though it takes more time, to truly cover the story updates need to be posted. Even 3 months later.</description>
		<content:encoded><![CDATA[<p>I think it should be updated in a web story, especially if the television counterpart updates the story on the air.</p>
<p>If the story isn&#8217;t furthered on television, the majority of the public won&#8217;t know or care. Most people will have forgotten about the case. But the Internet isn&#8217;t a linear medium like TV.</p>
<p>10 years from now, someone could be searching for that person and come across the story. They&#8217;ll find that this person was arrested/charged, and not know they&#8217;re actually guilty. In the reader&#8217;s mind, they&#8217;re guilty, and that&#8217;s their sole take-away from the article. The reader should be provided with all of the facts.</p>
<p>Even though it takes more time, to truly cover the story updates need to be posted. Even 3 months later.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://www.lostremote.com/2008/06/18/updating-archives-to-protect-the-innocent/#comment-1034182</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Thu, 19 Jun 2008 03:09:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.lostremote.com/?p=5125#comment-1034182</guid>
		<description>Nick: You're not altering to past to add "UPDATE (6/18/08): Charges Dropped [LINK]." or "UPDATE (6/18/08): Meyers Acquitted [LINK]." or whatever to the top of the story.</description>
		<content:encoded><![CDATA[<p>Nick: You&#8217;re not altering to past to add &#8220;UPDATE (6/18/08): Charges Dropped [LINK].&#8221; or &#8220;UPDATE (6/18/08): Meyers Acquitted [LINK].&#8221; or whatever to the top of the story.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
