<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: How big data helps Ancestry.com map people, places and time</title>
	<atom:link href="http://gigaom.com/2012/06/12/how-ancestry-com-is-using-big-data-to-map-time-place-and-people/feed/" rel="self" type="application/rss+xml" />
	<link>http://gigaom.com/2012/06/12/how-ancestry-com-is-using-big-data-to-map-time-place-and-people/</link>
	<description></description>
	<lastBuildDate>Tue, 18 Jun 2013 07:02:30 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: J</title>
		<link>http://gigaom.com/2012/06/12/how-ancestry-com-is-using-big-data-to-map-time-place-and-people/#comment-883956</link>
		<dc:creator><![CDATA[J]]></dc:creator>
		<pubDate>Thu, 09 Aug 2012 22:10:07 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=531644#comment-883956</guid>
		<description><![CDATA[One must keep in mind that not only are there errors in the online family trees, but also in the records used to make them.  Though I truly like the automation of trees and data, I am very careful to verify the data before attaching and I rarely allow a tree to become public precisely because of the error factor.

Automation has lead unfortunately to what a scientist would call bad science.  Attach, attach, attach and publish should be changed to verify, verify, verify.  Alas, too many want instant gratification.

J]]></description>
		<content:encoded><![CDATA[<p>One must keep in mind that not only are there errors in the online family trees, but also in the records used to make them.  Though I truly like the automation of trees and data, I am very careful to verify the data before attaching and I rarely allow a tree to become public precisely because of the error factor.</p>
<p>Automation has lead unfortunately to what a scientist would call bad science.  Attach, attach, attach and publish should be changed to verify, verify, verify.  Alas, too many want instant gratification.</p>
<p>J</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Clareita</title>
		<link>http://gigaom.com/2012/06/12/how-ancestry-com-is-using-big-data-to-map-time-place-and-people/#comment-859147</link>
		<dc:creator><![CDATA[Clareita]]></dc:creator>
		<pubDate>Sat, 30 Jun 2012 20:55:22 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=531644#comment-859147</guid>
		<description><![CDATA[Maybe Charlemagne, but not Henry VIII since he has no descendants.]]></description>
		<content:encoded><![CDATA[<p>Maybe Charlemagne, but not Henry VIII since he has no descendants.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Derrick Harris</title>
		<link>http://gigaom.com/2012/06/12/how-ancestry-com-is-using-big-data-to-map-time-place-and-people/#comment-852013</link>
		<dc:creator><![CDATA[Derrick Harris]]></dc:creator>
		<pubDate>Thu, 14 Jun 2012 05:43:51 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=531644#comment-852013</guid>
		<description><![CDATA[LOL.]]></description>
		<content:encoded><![CDATA[<p>LOL.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alice_Crain</title>
		<link>http://gigaom.com/2012/06/12/how-ancestry-com-is-using-big-data-to-map-time-place-and-people/#comment-852008</link>
		<dc:creator><![CDATA[Alice_Crain]]></dc:creator>
		<pubDate>Thu, 14 Jun 2012 05:17:52 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=531644#comment-852008</guid>
		<description><![CDATA[On the bright side, though, one day we may ALL be descended from Henry VIII and Charlemagne!  ;)]]></description>
		<content:encoded><![CDATA[<p>On the bright side, though, one day we may ALL be descended from Henry VIII and Charlemagne!  ;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alice_Crain</title>
		<link>http://gigaom.com/2012/06/12/how-ancestry-com-is-using-big-data-to-map-time-place-and-people/#comment-852007</link>
		<dc:creator><![CDATA[Alice_Crain]]></dc:creator>
		<pubDate>Thu, 14 Jun 2012 05:12:03 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=531644#comment-852007</guid>
		<description><![CDATA[If I spend 2 hours watching a PBS Civil War documentary on  Netflix, or plunk down $20 on Battle Cry of Freedom at Amazon, it would indeed be a fair assumption to conclude that I am interested in the Civil War.

But if I attach a Social Security Death Index to Katherine Compton in my family tree... because the name matches, and I&#039;m excited to suddenly &quot;know&quot; her dates of birth and death, and, hey, the Ancestry hints are telling me that other users have attached the same SSDI to their Katherine Compton too... does that make my choice to attach the record a fair assumption with regard to historical fact?  No.  It does not.  

*IF* Ancestry&#039;s users were all painstakingly careful, deliberate, well-reasoned constructors of family trees, then Mr. Sorenson&#039;s model would make sense.  But they are not.  Ken Piper (in the comment below) is right.  Ancestry&#039;s user-submitted trees are rife with inaccuracies.

To answer your question - the only way I can think of to solve this problem is to leave user choices out of the algorithm altogether.]]></description>
		<content:encoded><![CDATA[<p>If I spend 2 hours watching a PBS Civil War documentary on  Netflix, or plunk down $20 on Battle Cry of Freedom at Amazon, it would indeed be a fair assumption to conclude that I am interested in the Civil War.</p>
<p>But if I attach a Social Security Death Index to Katherine Compton in my family tree&#8230; because the name matches, and I&#8217;m excited to suddenly &#8220;know&#8221; her dates of birth and death, and, hey, the Ancestry hints are telling me that other users have attached the same SSDI to their Katherine Compton too&#8230; does that make my choice to attach the record a fair assumption with regard to historical fact?  No.  It does not.  </p>
<p>*IF* Ancestry&#8217;s users were all painstakingly careful, deliberate, well-reasoned constructors of family trees, then Mr. Sorenson&#8217;s model would make sense.  But they are not.  Ken Piper (in the comment below) is right.  Ancestry&#8217;s user-submitted trees are rife with inaccuracies.</p>
<p>To answer your question &#8211; the only way I can think of to solve this problem is to leave user choices out of the algorithm altogether.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Derrick Harris</title>
		<link>http://gigaom.com/2012/06/12/how-ancestry-com-is-using-big-data-to-map-time-place-and-people/#comment-851894</link>
		<dc:creator><![CDATA[Derrick Harris]]></dc:creator>
		<pubDate>Wed, 13 Jun 2012 23:02:29 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=531644#comment-851894</guid>
		<description><![CDATA[That&#039;s a good point, although how would you solve it to account for poor judgment? It seems like a fair assumption when building a model that user behavior is determinative of accuracy.]]></description>
		<content:encoded><![CDATA[<p>That&#8217;s a good point, although how would you solve it to account for poor judgment? It seems like a fair assumption when building a model that user behavior is determinative of accuracy.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ken Piper</title>
		<link>http://gigaom.com/2012/06/12/how-ancestry-com-is-using-big-data-to-map-time-place-and-people/#comment-851885</link>
		<dc:creator><![CDATA[Ken Piper]]></dc:creator>
		<pubDate>Wed, 13 Jun 2012 22:37:04 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=531644#comment-851885</guid>
		<description><![CDATA[I agree that I worry about user judgement.  Aside from record images, the bulk of &quot;data&quot; on Ancestry is submitted family trees with a horrible record of accuracy.  I have given up fighting the wave of citations pointing to other users as a record.  The inaccuracies become &quot;fact&quot; and when you truly find the correct fact you are drowned out by the glut of bad data.  It will only get worse.]]></description>
		<content:encoded><![CDATA[<p>I agree that I worry about user judgement.  Aside from record images, the bulk of &#8220;data&#8221; on Ancestry is submitted family trees with a horrible record of accuracy.  I have given up fighting the wave of citations pointing to other users as a record.  The inaccuracies become &#8220;fact&#8221; and when you truly find the correct fact you are drowned out by the glut of bad data.  It will only get worse.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alice_Crain</title>
		<link>http://gigaom.com/2012/06/12/how-ancestry-com-is-using-big-data-to-map-time-place-and-people/#comment-851653</link>
		<dc:creator><![CDATA[Alice_Crain]]></dc:creator>
		<pubDate>Wed, 13 Jun 2012 12:28:49 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=531644#comment-851653</guid>
		<description><![CDATA[Unfortunately, user judgment is not always sound, and Mr. Sorenson&#039;s algorithm mucks up the search engine precisely because it &quot;learns&quot; from those user choices.

Big Data?  As the algorithm incorporates inaccuracies, and then prompts more people to confirm those &quot;judgments&quot; in making choices of their own... Big Bad Data is what it becomes.]]></description>
		<content:encoded><![CDATA[<p>Unfortunately, user judgment is not always sound, and Mr. Sorenson&#8217;s algorithm mucks up the search engine precisely because it &#8220;learns&#8221; from those user choices.</p>
<p>Big Data?  As the algorithm incorporates inaccuracies, and then prompts more people to confirm those &#8220;judgments&#8221; in making choices of their own&#8230; Big Bad Data is what it becomes.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
