<?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/"
		>
<channel>
	<title>Comments on: Webinar next Tuesday:  New Site Features Added to Ancestry.com in 2008</title>
	<atom:link href="http://blogs.ancestry.com/ancestry/2009/01/21/webinar-next-tuesday-new-site-features-added-to-ancestrycom-in-2008/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.ancestry.com/ancestry/2009/01/21/webinar-next-tuesday-new-site-features-added-to-ancestrycom-in-2008/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=webinar-next-tuesday-new-site-features-added-to-ancestrycom-in-2008</link>
	<description>The official blog of Ancestry.com</description>
	<lastBuildDate>Sat, 25 May 2013 04:38:25 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.2</generator>
	<item>
		<title>By: RON</title>
		<link>http://blogs.ancestry.com/ancestry/2009/01/21/webinar-next-tuesday-new-site-features-added-to-ancestrycom-in-2008/#comment-36102</link>
		<dc:creator>RON</dc:creator>
		<pubDate>Wed, 11 Mar 2009 16:19:18 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/2009/01/21/webinar-next-tuesday-new-site-features-added-to-ancestrycom-in-2008/#comment-36102</guid>
		<description>Our you going to give the correct time for the show?

8 PM EST 

Wake up! The rest of use are using
Daylight Saving Time</description>
		<content:encoded><![CDATA[<p>Our you going to give the correct time for the show?</p>
<p>8 PM EST </p>
<p>Wake up! The rest of use are using<br />
Daylight Saving Time</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Terry Carter</title>
		<link>http://blogs.ancestry.com/ancestry/2009/01/21/webinar-next-tuesday-new-site-features-added-to-ancestrycom-in-2008/#comment-34663</link>
		<dc:creator>Terry Carter</dc:creator>
		<pubDate>Tue, 03 Mar 2009 15:27:45 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/2009/01/21/webinar-next-tuesday-new-site-features-added-to-ancestrycom-in-2008/#comment-34663</guid>
		<description>Eric,

I&#039;m also a newbie and already experienced my share of frustrations (which brought me to this blog). Reading the comments here from the &quot;old timers,&quot; what strikes me the most is that you apparently redesigned your site in a vacuum. You introduced new &quot;features&quot; and eliminated some old ones, only to reverse yourselves (e.g., state and country pages).

Frankly, I don&#039;t know if I&#039;m going to stick with you. Your site is buggy and unintuitive. I end up with duplicate records, &quot;children of unknown spouse&quot; (and I can&#039;t delete the unknown spouse), people drop off for no apparent reason and more. Mostly, making changes to your site without proper testing (and vetting) is inexcusable. Microsoft can get away with this crap, but you can&#039;t. The marketpalce will punish you.</description>
		<content:encoded><![CDATA[<p>Eric,</p>
<p>I&#8217;m also a newbie and already experienced my share of frustrations (which brought me to this blog). Reading the comments here from the &#8220;old timers,&#8221; what strikes me the most is that you apparently redesigned your site in a vacuum. You introduced new &#8220;features&#8221; and eliminated some old ones, only to reverse yourselves (e.g., state and country pages).</p>
<p>Frankly, I don&#8217;t know if I&#8217;m going to stick with you. Your site is buggy and unintuitive. I end up with duplicate records, &#8220;children of unknown spouse&#8221; (and I can&#8217;t delete the unknown spouse), people drop off for no apparent reason and more. Mostly, making changes to your site without proper testing (and vetting) is inexcusable. Microsoft can get away with this crap, but you can&#8217;t. The marketpalce will punish you.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Shoup</title>
		<link>http://blogs.ancestry.com/ancestry/2009/01/21/webinar-next-tuesday-new-site-features-added-to-ancestrycom-in-2008/#comment-33744</link>
		<dc:creator>Eric Shoup</dc:creator>
		<pubDate>Sun, 22 Feb 2009 00:21:52 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/2009/01/21/webinar-next-tuesday-new-site-features-added-to-ancestrycom-in-2008/#comment-33744</guid>
		<description>Thanks Julie for the input.  I&#039;ll pass this along to our Trees team.

eric</description>
		<content:encoded><![CDATA[<p>Thanks Julie for the input.  I&#8217;ll pass this along to our Trees team.</p>
<p>eric</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Julie Mulroy</title>
		<link>http://blogs.ancestry.com/ancestry/2009/01/21/webinar-next-tuesday-new-site-features-added-to-ancestrycom-in-2008/#comment-33715</link>
		<dc:creator>Julie Mulroy</dc:creator>
		<pubDate>Sat, 21 Feb 2009 18:42:34 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/2009/01/21/webinar-next-tuesday-new-site-features-added-to-ancestrycom-in-2008/#comment-33715</guid>
		<description>I couldn&#039;t figure out how to comment on the &quot;adding other relatives on the record&quot; feature, so I&#039;ll do it here. The concept is great. However, it seems to work best (or only) when the record is found via head of household. Work-arounds such as adding the record to the husband when it was turned up in a search (or hint) for the wife can lead to a parent married to a child and other oddities. One has to be careful not to duplicate relatives whose names aren&#039;t recognized as variants, and the original image must be scrutinized for relatives not included (especially those identified as in-laws and their children, who are clearly grandchildren of the head and spouse). And sometimes only the first of several children is listed.

Since using this feature I have ended up with &quot;children of unknown spouse&quot; (often duplicating the names and associated information of children of the spouse on the record), and multiple attachments of a record to the same individual. This means checking every replicated event on a profile to make sure the one with the most information and proper documentation (especially the original document IMAGE attached, which I repeatedly consult as new questions arise) remains.

So this feature, while great in concept and a typing-saver, is definitely not a time saver, and must be used with great care

In an ideal world, all the ancillary information for each person would be added ss well.</description>
		<content:encoded><![CDATA[<p>I couldn&#8217;t figure out how to comment on the &#8220;adding other relatives on the record&#8221; feature, so I&#8217;ll do it here. The concept is great. However, it seems to work best (or only) when the record is found via head of household. Work-arounds such as adding the record to the husband when it was turned up in a search (or hint) for the wife can lead to a parent married to a child and other oddities. One has to be careful not to duplicate relatives whose names aren&#8217;t recognized as variants, and the original image must be scrutinized for relatives not included (especially those identified as in-laws and their children, who are clearly grandchildren of the head and spouse). And sometimes only the first of several children is listed.</p>
<p>Since using this feature I have ended up with &#8220;children of unknown spouse&#8221; (often duplicating the names and associated information of children of the spouse on the record), and multiple attachments of a record to the same individual. This means checking every replicated event on a profile to make sure the one with the most information and proper documentation (especially the original document IMAGE attached, which I repeatedly consult as new questions arise) remains.</p>
<p>So this feature, while great in concept and a typing-saver, is definitely not a time saver, and must be used with great care</p>
<p>In an ideal world, all the ancillary information for each person would be added ss well.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Debbie Scott</title>
		<link>http://blogs.ancestry.com/ancestry/2009/01/21/webinar-next-tuesday-new-site-features-added-to-ancestrycom-in-2008/#comment-31875</link>
		<dc:creator>Debbie Scott</dc:creator>
		<pubDate>Wed, 04 Feb 2009 11:42:33 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/2009/01/21/webinar-next-tuesday-new-site-features-added-to-ancestrycom-in-2008/#comment-31875</guid>
		<description>Hi Eric,
Thank you. I hope it&#039;s something they can rectify.
Debbie</description>
		<content:encoded><![CDATA[<p>Hi Eric,<br />
Thank you. I hope it&#8217;s something they can rectify.<br />
Debbie</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jswatson71</title>
		<link>http://blogs.ancestry.com/ancestry/2009/01/21/webinar-next-tuesday-new-site-features-added-to-ancestrycom-in-2008/#comment-31363</link>
		<dc:creator>jswatson71</dc:creator>
		<pubDate>Thu, 29 Jan 2009 20:34:16 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/2009/01/21/webinar-next-tuesday-new-site-features-added-to-ancestrycom-in-2008/#comment-31363</guid>
		<description>I wasn&#039;t able to listen to the Tuesday night webinar but listened this afternoon and really learned a lot. Thanks!</description>
		<content:encoded><![CDATA[<p>I wasn&#8217;t able to listen to the Tuesday night webinar but listened this afternoon and really learned a lot. Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Shoup</title>
		<link>http://blogs.ancestry.com/ancestry/2009/01/21/webinar-next-tuesday-new-site-features-added-to-ancestrycom-in-2008/#comment-31350</link>
		<dc:creator>Eric Shoup</dc:creator>
		<pubDate>Thu, 29 Jan 2009 18:16:55 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/2009/01/21/webinar-next-tuesday-new-site-features-added-to-ancestrycom-in-2008/#comment-31350</guid>
		<description>We had a little over 400 people turnout for the webinar.  98% of attendees surveyed said they would recommend the webinar to a friend.

For those of you who missed the webinar, you can find it &lt;a href=&quot;http://event.on24.com/eventRegistration/EventLobbyServlet?target=lobby.jsp&amp;eventid=131590&amp;sessionid=1&amp;key=FCD7B37960E09B88BB2279119F4B154A&amp;eventuserid=22138751&quot; style=&quot;color: #546a00&quot; rel=&quot;nofollow&quot;&gt;here&lt;/a&gt;.


For those who attended, we also sent out a set of links to additional resources that were referred to in the webinar:
	  &lt;p&gt;&lt;a href=&quot;http://blogs.ancestry.com/ancestry/2008/05/29/new-record-merge-feature/&quot; style=&quot;color: #546a00&quot; rel=&quot;nofollow&quot;&gt;New Merge Blog &lt;/a&gt;&lt;/p&gt;
	  &lt;p&gt;&lt;a href=&quot;http://landing.ancestry.com/toolbar/default.aspx&quot; style=&quot;color: #546a00&quot; rel=&quot;nofollow&quot;&gt;The Ancestry Toolbar&lt;/a&gt;&lt;/p&gt;

      &lt;p&gt;&lt;a href=&quot;http://search.ancestry.com/search/CardCatalog.aspx&quot; style=&quot;color: #546a00&quot; rel=&quot;nofollow&quot;&gt;Ancestry Card Catalog&lt;/a&gt;&lt;/p&gt;
      &lt;p&gt;&lt;a href=&quot;http://www.ancestry.com/WorldArchivesProject/&quot; style=&quot;color: #546a00&quot; rel=&quot;nofollow&quot;&gt;Ancestry.com World Archives Project&lt;/a&gt;&lt;/p&gt;
      &lt;p&gt;&lt;a href=&quot;http://blogs.ancestry.com/circle/&quot; style=&quot;color: #546a00&quot; rel=&quot;nofollow&quot;&gt;24/7 Family History Circle&lt;/a&gt;&lt;/p&gt;

See you next time.

Eric</description>
		<content:encoded><![CDATA[<p>We had a little over 400 people turnout for the webinar.  98% of attendees surveyed said they would recommend the webinar to a friend.</p>
<p>For those of you who missed the webinar, you can find it <a href="http://event.on24.com/eventRegistration/EventLobbyServlet?target=lobby.jsp&#038;eventid=131590&#038;sessionid=1&#038;key=FCD7B37960E09B88BB2279119F4B154A&#038;eventuserid=22138751" style="color: #546a00" rel="nofollow">here</a>.</p>
<p>For those who attended, we also sent out a set of links to additional resources that were referred to in the webinar:</p>
<p><a href="http://blogs.ancestry.com/ancestry/2008/05/29/new-record-merge-feature/" style="color: #546a00" rel="nofollow">New Merge Blog </a></p>
<p><a href="http://landing.ancestry.com/toolbar/default.aspx" style="color: #546a00" rel="nofollow">The Ancestry Toolbar</a></p>
<p><a href="http://search.ancestry.com/search/CardCatalog.aspx" style="color: #546a00" rel="nofollow">Ancestry Card Catalog</a></p>
<p><a href="http://www.ancestry.com/WorldArchivesProject/" style="color: #546a00" rel="nofollow">Ancestry.com World Archives Project</a></p>
<p><a href="http://blogs.ancestry.com/circle/" style="color: #546a00" rel="nofollow">24/7 Family History Circle</a></p>
<p>See you next time.</p>
<p>Eric</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Shoup</title>
		<link>http://blogs.ancestry.com/ancestry/2009/01/21/webinar-next-tuesday-new-site-features-added-to-ancestrycom-in-2008/#comment-31349</link>
		<dc:creator>Eric Shoup</dc:creator>
		<pubDate>Thu, 29 Jan 2009 18:10:14 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/2009/01/21/webinar-next-tuesday-new-site-features-added-to-ancestrycom-in-2008/#comment-31349</guid>
		<description>Thank you for the additional feedback.

Claudia - We realize we have more to do on search.  We are actively working on improvements to our algorithms that you will see in the coming months.  We also reinstated the state &amp; country pages yesterday after removing them during our site outage a couple of weeks ago.

Derla - I am hoping that you were able to see the webinar on Tuesday.  If not, we have posted in the Learning Center for your review.  I will post links to its location in just a minute.

Debbie - I will pass this feedback along to my Trees team.

regards

eric</description>
		<content:encoded><![CDATA[<p>Thank you for the additional feedback.</p>
<p>Claudia &#8211; We realize we have more to do on search.  We are actively working on improvements to our algorithms that you will see in the coming months.  We also reinstated the state &#038; country pages yesterday after removing them during our site outage a couple of weeks ago.</p>
<p>Derla &#8211; I am hoping that you were able to see the webinar on Tuesday.  If not, we have posted in the Learning Center for your review.  I will post links to its location in just a minute.</p>
<p>Debbie &#8211; I will pass this feedback along to my Trees team.</p>
<p>regards</p>
<p>eric</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim Livermore</title>
		<link>http://blogs.ancestry.com/ancestry/2009/01/21/webinar-next-tuesday-new-site-features-added-to-ancestrycom-in-2008/#comment-31346</link>
		<dc:creator>Jim Livermore</dc:creator>
		<pubDate>Thu, 29 Jan 2009 17:11:23 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/2009/01/21/webinar-next-tuesday-new-site-features-added-to-ancestrycom-in-2008/#comment-31346</guid>
		<description>How was the turnout?</description>
		<content:encoded><![CDATA[<p>How was the turnout?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: davidfra</title>
		<link>http://blogs.ancestry.com/ancestry/2009/01/21/webinar-next-tuesday-new-site-features-added-to-ancestrycom-in-2008/#comment-31301</link>
		<dc:creator>davidfra</dc:creator>
		<pubDate>Thu, 29 Jan 2009 03:04:18 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/2009/01/21/webinar-next-tuesday-new-site-features-added-to-ancestrycom-in-2008/#comment-31301</guid>
		<description>I agree with all the comments here with the exception of &quot;Mary&quot;. Your company, website, genealogy software, etc. shows a complete lack of concern for any problems which users may have. Year after year you charge more for software and services and do less and less to earn those increases. A large portion of information that you provide for a fee has been taken from users for nothing. You produce new software (FTM) every year or two with little regard for what customers want and with no attempt to correct software problems. There is no way that name searches on your site was coded by a real software programmer, when I get over two million results on a specific name with a specific birthdate, race, place of birth. If you don&#039;t want to provide useful software and services please sell the company to someone who does. Your company sets genealogy back years.</description>
		<content:encoded><![CDATA[<p>I agree with all the comments here with the exception of &#8220;Mary&#8221;. Your company, website, genealogy software, etc. shows a complete lack of concern for any problems which users may have. Year after year you charge more for software and services and do less and less to earn those increases. A large portion of information that you provide for a fee has been taken from users for nothing. You produce new software (FTM) every year or two with little regard for what customers want and with no attempt to correct software problems. There is no way that name searches on your site was coded by a real software programmer, when I get over two million results on a specific name with a specific birthdate, race, place of birth. If you don&#8217;t want to provide useful software and services please sell the company to someone who does. Your company sets genealogy back years.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
