<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/atom10full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><feed xmlns="http://www.w3.org/2005/Atom" xmlns:openSearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:blogger="http://schemas.google.com/blogger/2008" xmlns:georss="http://www.georss.org/georss" xmlns:gd="http://schemas.google.com/g/2005" xmlns:thr="http://purl.org/syndication/thread/1.0" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" gd:etag="W/&quot;Ak8FRXs7eyp7ImA9WhFSFk4.&quot;"><id>tag:blogger.com,1999:blog-5512311610334754148</id><updated>2013-06-19T04:46:54.503-06:00</updated><category term="news and issues" /><category term="FamilySearch.org" /><category term="technology" /><category term="reviews" /><category term="citations" /><category term="FamilySearch Tree" /><category term="records" /><category term="FamilySearch Wiki" /><category term="genealogy tree managers" /><category term="Church of Jesus Christ..." /><category term="methodology" /><category term="Family History Centers" /><category term="indexing" /><category term="NARA" /><category term="no category" /><category term="Brigham Young University" /><category term="Records Say Darnedest" /><category term="libraries" /><category term="genealogy" /><category term="FamilySearch Affiliates" /><category term="Ancestry.com" /><category term="Dennis Brimhall" /><category term="websites" /><category term="trees" /><category term="FamilySearch" /><category term="Blog Help" /><category term="records access" /><category term="search" /><category term="video" /><category term="FamilySearch Labs" /><category term="serendipity" /><category term="conferences" /><category term="encyclopedia" /><category term="Family History Library" /><category term="humor" /><title>The Ancestry Insider</title><subtitle type="html">The unofficial, unauthorized view of Ancestry.com and FamilySearch.org. The Ancestry Insider reports on, defends, and constructively criticizes these two websites and associated topics. The author attempts to fairly and evenly support both.</subtitle><link rel="http://schemas.google.com/g/2005#feed" type="application/atom+xml" href="http://ancestryinsider.blogspot.com/feeds/posts/default" /><link rel="alternate" type="text/html" href="http://ancestryinsider.blogspot.com/" /><link rel="next" type="application/atom+xml" href="http://www.blogger.com/feeds/5512311610334754148/posts/default?start-index=26&amp;max-results=25&amp;redirect=false&amp;v=2" /><author><name>The Ancestry Insider</name><uri>http://www.blogger.com/profile/02490682912125335188</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="30" src="http://bp1.blogger.com/_mpUi75C5vC8/SBgCr-W4YOI/AAAAAAAAAXA/K3itFGYLq_4/S220/simpsonized3.jpg" /></author><generator version="7.00" uri="http://www.blogger.com">Blogger</generator><openSearch:totalResults>1154</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/atom+xml" href="http://feeds.feedburner.com/AncestryInsider" /><feedburner:info uri="ancestryinsider" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><feedburner:emailServiceId>AncestryInsider</feedburner:emailServiceId><feedburner:feedburnerHostname>http://feedburner.google.com</feedburner:feedburnerHostname><entry gd:etag="W/&quot;C04EQXo-cSp7ImA9WhFSFk8.&quot;"><id>tag:blogger.com,1999:blog-5512311610334754148.post-1030736035563216767</id><published>2013-06-19T00:05:00.000-06:00</published><updated>2013-06-19T00:05:00.459-06:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2013-06-19T00:05:00.459-06:00</app:edited><title>Found Another Photo of Me at NGS2013</title><content type="html">&lt;p&gt;&lt;a href="http://lh5.ggpht.com/-mw-VYOc7Dws/UbPCZ3vOjLI/AAAAAAAAErc/SnXCP5u4JP4/s1600-h/image%25255B3%25255D.png"&gt;&lt;img title="image" style="border-top: 0px; border-right: 0px; background-image: none; border-bottom: 0px; float: right; padding-top: 0px; padding-left: 0px; border-left: 0px; display: inline; padding-right: 0px" border="0" alt="image" align="right" src="http://lh4.ggpht.com/-J8croOZR5pc/UbPCbFEcb3I/AAAAAAAAErk/Pm2Dz1jZNpQ/image_thumb%25255B1%25255D.png?imgmax=800" width="324" height="244" /&gt;&lt;/a&gt;&lt;/p&gt;  &lt;p&gt;If you’re new to my blog, you may not be aware that I am the Wilson of genealogy bloggers. Julie Miller took this photograph of the Official Blogger Media Center, accidentally capturing me. I’m the one in blue in the back, behind Kathryn Doyle, behind Randy Seaver.&lt;/p&gt;  &lt;p&gt;See more photos from Julie in her article: “&lt;a href="http://upfront.ngsgenealogy.org/2013/05/day-2-of-ngs-family-history-conference.html" target="_blank"&gt;Day 2 of the NGS Family History Conference -- just as busy and exciting as Day 1&lt;/a&gt;.”&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;br /&gt;&lt;hr /&gt;
&lt;b&gt;Notice:&lt;/b&gt; The opinions expressed herein are those of the Ancestry Insider, not necessarily those of Ancestry.com or FamilySearch. All content is copyrighted by the Ancestry Insider unless designated otherwise. See http://ancestryinsider.blogspot.com for other important legal notices.&lt;/div&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/AncestryInsider?a=bb2MkIqAKNg:o1fglg5_uG0:2nqncYFp4_M"&gt;&lt;img src="http://feeds.feedburner.com/~ff/AncestryInsider?d=2nqncYFp4_M" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/AncestryInsider?a=bb2MkIqAKNg:o1fglg5_uG0:4cEx4HpKnUU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/AncestryInsider?i=bb2MkIqAKNg:o1fglg5_uG0:4cEx4HpKnUU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/AncestryInsider?a=bb2MkIqAKNg:o1fglg5_uG0:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/AncestryInsider?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/AncestryInsider/~4/bb2MkIqAKNg" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://ancestryinsider.blogspot.com/feeds/1030736035563216767/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://ancestryinsider.blogspot.com/2013/06/found-another-photo-of-me-at-ngs2013.html#comment-form" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/5512311610334754148/posts/default/1030736035563216767?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/5512311610334754148/posts/default/1030736035563216767?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/AncestryInsider/~3/bb2MkIqAKNg/found-another-photo-of-me-at-ngs2013.html" title="Found Another Photo of Me at NGS2013" /><author><name>The Ancestry Insider</name><uri>http://www.blogger.com/profile/02490682912125335188</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="30" src="http://bp1.blogger.com/_mpUi75C5vC8/SBgCr-W4YOI/AAAAAAAAAXA/K3itFGYLq_4/S220/simpsonized3.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://lh4.ggpht.com/-J8croOZR5pc/UbPCbFEcb3I/AAAAAAAAErk/Pm2Dz1jZNpQ/s72-c/image_thumb%25255B1%25255D.png?imgmax=800" height="72" width="72" /><thr:total>1</thr:total><feedburner:origLink>http://ancestryinsider.blogspot.com/2013/06/found-another-photo-of-me-at-ngs2013.html</feedburner:origLink></entry><entry gd:etag="W/&quot;D0IEQXs8eSp7ImA9WhFSFU4.&quot;"><id>tag:blogger.com,1999:blog-5512311610334754148.post-1318966864060632031</id><published>2013-06-18T00:05:00.000-06:00</published><updated>2013-06-18T00:05:00.571-06:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2013-06-18T00:05:00.571-06:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="conferences" /><title>The Ancestry Insider is an #FGS2013 Ambassador</title><content type="html">&lt;p&gt;&lt;a href="https://www.fgsconference.org/" target="_blank"&gt;&lt;img title="The Ancestry Insider is an FGS 2013 ambassador" style="border-top: 0px; border-right: 0px; background-image: none; border-bottom: 0px; float: right; padding-top: 0px; padding-left: 0px; border-left: 0px; display: inline; padding-right: 0px" border="0" alt="The Ancestry Insider is an FGS 2013 ambassador" align="right" src="http://lh4.ggpht.com/-57nm7plbAFk/UbOilDDYY5I/AAAAAAAAEq0/SZF_RuuoWSw/image%25255B4%25255D.png?imgmax=800" width="220" height="201" /&gt;&lt;/a&gt;I have volunteered to be an ambassador for the &lt;a href="https://www.fgsconference.org/" target="_blank"&gt;2013 annual conference&lt;/a&gt; of the &lt;a href="http://www.fgs.org/" target="_blank"&gt;Federation of Genealogical Societies&lt;/a&gt;. The conference is scheduled for 21-24 August 2013 in Fort Wayne, Indiana.&lt;/p&gt;  &lt;p&gt;I knew I had to go to this conference the moment I saw &lt;a href="https://www.fgsconference.org/assets/files/FGS-2013-Conference-Registration-Booklet.pdf" target="_blank"&gt;the cover of the brochure&lt;/a&gt;:&lt;/p&gt;  &lt;p&gt;&lt;a href="https://www.fgsconference.org/assets/files/FGS-2013-Conference-Registration-Booklet.pdf" target="_blank"&gt;&lt;img title="The planet on the cover of the FGS 2013 conference brochure" style="border-top: 0px; border-right: 0px; background-image: none; border-bottom: 0px; padding-top: 0px; padding-left: 0px; border-left: 0px; display: inline; padding-right: 0px" border="0" alt="The planet on the cover of the FGS 2013 conference brochure" src="http://lh4.ggpht.com/--LeQwUy018o/UbOinBFc7oI/AAAAAAAAEq8/MSmPkAIUigA/image%25255B9%25255D.png?imgmax=800" width="388" height="404" /&gt;&lt;/a&gt;&lt;/p&gt;  &lt;p&gt;Apparently, the mission of “the Federation” is “to explore strange new worlds, to seek out new lives and new generations. To boldly go where no man has gone before!” &lt;/p&gt;  &lt;p&gt;Certainly, I’ve never been to Fort Wayne, Indiana or the famous &lt;a href="http://www.acpl.lib.in.us/" target="_blank"&gt;Allen County Public Library&lt;/a&gt;. The &lt;a href="http://www.genealogycenter.org" target="_blank"&gt;Genealogy Center&lt;/a&gt; there is world class and I am looking forward to exploring it.&lt;/p&gt;  &lt;p&gt;We are fast approaching the Early Bird Deadline on July 1st. Register in June to save $50 off a full conference registration. Visit the &lt;a href="https://www.fgsconference.org/" target="_blank"&gt;conference home page&lt;/a&gt; to learn more about the conference and the &lt;a href="https://www.fgsconference.org/registration/" target="_blank"&gt;registration page&lt;/a&gt; to register.&lt;/p&gt;  &lt;p&gt;The prime directive is to maximize your learning at the conference and at the ACPL library. Live long and prosper.&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;br /&gt;&lt;hr /&gt;
&lt;b&gt;Notice:&lt;/b&gt; The opinions expressed herein are those of the Ancestry Insider, not necessarily those of Ancestry.com or FamilySearch. All content is copyrighted by the Ancestry Insider unless designated otherwise. See http://ancestryinsider.blogspot.com for other important legal notices.&lt;/div&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/AncestryInsider?a=RwX-Rzv83S8:LweY4WgKEXk:2nqncYFp4_M"&gt;&lt;img src="http://feeds.feedburner.com/~ff/AncestryInsider?d=2nqncYFp4_M" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/AncestryInsider?a=RwX-Rzv83S8:LweY4WgKEXk:4cEx4HpKnUU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/AncestryInsider?i=RwX-Rzv83S8:LweY4WgKEXk:4cEx4HpKnUU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/AncestryInsider?a=RwX-Rzv83S8:LweY4WgKEXk:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/AncestryInsider?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/AncestryInsider/~4/RwX-Rzv83S8" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://ancestryinsider.blogspot.com/feeds/1318966864060632031/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://ancestryinsider.blogspot.com/2013/06/the-ancestry-insider-is-fgs2013.html#comment-form" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/5512311610334754148/posts/default/1318966864060632031?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/5512311610334754148/posts/default/1318966864060632031?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/AncestryInsider/~3/RwX-Rzv83S8/the-ancestry-insider-is-fgs2013.html" title="The Ancestry Insider is an #FGS2013 Ambassador" /><author><name>The Ancestry Insider</name><uri>http://www.blogger.com/profile/02490682912125335188</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="30" src="http://bp1.blogger.com/_mpUi75C5vC8/SBgCr-W4YOI/AAAAAAAAAXA/K3itFGYLq_4/S220/simpsonized3.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://lh4.ggpht.com/-57nm7plbAFk/UbOilDDYY5I/AAAAAAAAEq0/SZF_RuuoWSw/s72-c/image%25255B4%25255D.png?imgmax=800" height="72" width="72" /><thr:total>2</thr:total><feedburner:origLink>http://ancestryinsider.blogspot.com/2013/06/the-ancestry-insider-is-fgs2013.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CUIEQXk5fip7ImA9WhFSEU0.&quot;"><id>tag:blogger.com,1999:blog-5512311610334754148.post-5217712402963926122</id><published>2013-06-13T00:05:00.000-06:00</published><updated>2013-06-13T00:05:00.726-06:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2013-06-13T00:05:00.726-06:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="conferences" /><title>#NGS2013 Recordings Now Available</title><content type="html">&lt;p&gt;&lt;a href="http://www.ngsgenealogy.org/cs/conference_info" target="_blank"&gt;&lt;img title="NGS 2013 Official Blogger" border="0" alt="NGS 2013 Official Blogger" align="right" src="http://lh5.ggpht.com/-BSAE2e3iiRw/UTtgN-zyelI/AAAAAAAAEYc/jDfN8KobDT0/NGS%2525202013%252520Official%252520Blogger%25255B3%25255D.jpg?imgmax=800" width="204" height="204" /&gt;&lt;/a&gt;The &lt;a href="http://www.ngsgenealogy.org/" target="_blank"&gt;National Genealogical Society&lt;/a&gt; has announced that “recordings of lectures presented at the NGS 2013 Family History Conference in Las Vegas, Nevada, from 8–11 May 2013 are now available from JAMB, Inc. The CDs may be purchased from the JAMB online store for $12.00 each. A full list of available lecture CDs can be found on their website at &lt;a href="http://www.jamb-inc.com/genealogy/ngs/2013-ngs-conference-las-vegas-nv" target="_blank"&gt;http://www.jamb-inc.com/genealogy/ngs/2013-ngs-conference-las-vegas-nv&lt;/a&gt;.”&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;br /&gt;&lt;hr /&gt;
&lt;b&gt;Notice:&lt;/b&gt; The opinions expressed herein are those of the Ancestry Insider, not necessarily those of Ancestry.com or FamilySearch. All content is copyrighted by the Ancestry Insider unless designated otherwise. See http://ancestryinsider.blogspot.com for other important legal notices.&lt;/div&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/AncestryInsider?a=dLXKI4iE8Zs:VJ-qLr8U_5o:2nqncYFp4_M"&gt;&lt;img src="http://feeds.feedburner.com/~ff/AncestryInsider?d=2nqncYFp4_M" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/AncestryInsider?a=dLXKI4iE8Zs:VJ-qLr8U_5o:4cEx4HpKnUU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/AncestryInsider?i=dLXKI4iE8Zs:VJ-qLr8U_5o:4cEx4HpKnUU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/AncestryInsider?a=dLXKI4iE8Zs:VJ-qLr8U_5o:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/AncestryInsider?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/AncestryInsider/~4/dLXKI4iE8Zs" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://ancestryinsider.blogspot.com/feeds/5217712402963926122/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://ancestryinsider.blogspot.com/2013/06/ngs2013-recordings-now-available.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/5512311610334754148/posts/default/5217712402963926122?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/5512311610334754148/posts/default/5217712402963926122?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/AncestryInsider/~3/dLXKI4iE8Zs/ngs2013-recordings-now-available.html" title="#NGS2013 Recordings Now Available" /><author><name>The Ancestry Insider</name><uri>http://www.blogger.com/profile/02490682912125335188</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="30" src="http://bp1.blogger.com/_mpUi75C5vC8/SBgCr-W4YOI/AAAAAAAAAXA/K3itFGYLq_4/S220/simpsonized3.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://lh5.ggpht.com/-BSAE2e3iiRw/UTtgN-zyelI/AAAAAAAAEYc/jDfN8KobDT0/s72-c/NGS%2525202013%252520Official%252520Blogger%25255B3%25255D.jpg?imgmax=800" height="72" width="72" /><thr:total>0</thr:total><feedburner:origLink>http://ancestryinsider.blogspot.com/2013/06/ngs2013-recordings-now-available.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DUYEQXwzeSp7ImA9WhFSEEw.&quot;"><id>tag:blogger.com,1999:blog-5512311610334754148.post-678572459594329852</id><published>2013-06-12T00:05:00.000-06:00</published><updated>2013-06-12T00:05:00.281-06:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2013-06-12T00:05:00.281-06:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="FamilySearch.org" /><title>FamilySearch.org Photo Frustration</title><content type="html">&lt;p align="left"&gt;&lt;a href="http://commons.wikimedia.org/wiki/File:StateLibQld_1_186667_Twin_sisters_Kate_and_Emily_Bauer,_ca_1915.jpg" target="_blank"&gt;&lt;img title="FamilySearch.org has two systems of people, tree people and photo people" style="border-top: 0px; border-right: 0px; background-image: none; border-bottom: 0px; float: right; padding-top: 0px; padding-left: 0px; border-left: 0px; display: inline; padding-right: 0px" border="0" alt="FamilySearch.org has two systems of people, tree people and photo people" align="right" src="http://lh4.ggpht.com/-J72rXKrzCX0/UbNgSiYaMmI/AAAAAAAAEqU/-xWopNu_EFM/371px-StateLibQld_1_186667_Twin_sisters_Kate_and_Emily_Bauer%25252C_ca_1915%25255B5%25255D.jpg?imgmax=800" width="204" height="327" /&gt;&lt;/a&gt;&lt;a href="http://www.ancestry.com/" target="_blank"&gt;Ancestry.com&lt;/a&gt; member trees have persons and photos. Photos can be linked to persons. Simple.&lt;/p&gt;  &lt;p&gt;The Tree section of &lt;a href="http://FamilySearch.org" target="_blank"&gt;FamilySearch&lt;/a&gt;.org has persons. The Photos section of FamilySearch.org has its own set of persons. Photos can be linked (tagged) to photo persons which can be linked (connected) to tree persons. &lt;/p&gt;  &lt;p&gt;FamilySearch Family Tree has one set of deceased tree persons. FamilySearch Photos has photo persons that are unique to each user.&lt;/p&gt;  &lt;p&gt;Two tree people can have the same name. Two photo people cannot. Each photo person must have a unique name.&lt;/p&gt;  &lt;p&gt;Tree people can be assigned facts like name, birth date, and death date. These can be used to distinguish tree people with the same name. Photo people only have a name. One way to distinguish photo persons is to add the birth and death years to the person’s name.&lt;/p&gt;  &lt;p&gt;Can a photo person have a different portrait from a tree person which can be different for each user? I’m totally confused on this point.&lt;/p&gt;  &lt;p&gt;Should the same person be mistakenly entered twice, two tree persons can be merged. For two photo persons, delete one and reattach all its photos to the surviving photo person. The Help Center describes &lt;a href="https://help.familysearch.org/publishing/509/114834_f.SAL_Public.html" target="_blank"&gt;this eight step process&lt;/a&gt;. Repeat steps 6 and 7 for each photo.&lt;/p&gt;  &lt;table cellspacing="0" cellpadding="1" width="600" border="1"&gt;&lt;tbody&gt;     &lt;tr&gt;       &lt;td valign="top" width="600"&gt;         &lt;ol&gt;           &lt;li&gt;Find the duplicate ancestors in your &lt;b&gt;People Photos&lt;/b&gt; section.              &lt;br /&gt;&lt;img title="" border="1" src="https://help.familysearch.org/publishing/images/114834_fphotos001.jpg" /&gt;&lt;/li&gt;            &lt;li&gt;Determine which ancestor appearing on the list is the duplicate that you would like to delete. Often you can tell by the default image you have selected. Usually the default image is the first tagged image that was uploaded. **Remember this image, as it will help you to know which name to untag in step 6 below.** &lt;/li&gt;            &lt;li&gt;Select the duplicate ancestor photo from the &lt;b&gt;People Photos&lt;/b&gt; section by clicking on the person's photo. &lt;/li&gt;            &lt;li&gt;Click the &lt;b&gt;View Family Tree&lt;/b&gt; link (if it is linked to an ID number in Family Tree), and click &lt;b&gt;Unlink&lt;/b&gt; to unlink it from the Family Tree.&lt;/li&gt;            &lt;li&gt;The photos tagged by the duplicate ancestor account will now be shown. (Often at this step the program will change from displaying many photos to just a couple. This is because the photos are no longer associated with the other ancestor account through the ID number that you unlinked).&lt;/li&gt;            &lt;li&gt;Click on each photo listed, and untag the incorrect duplicate account name from the photo. Use the default image to determine if it is the duplicate account name. Also, the &lt;b&gt;unlinked&lt;/b&gt; account will appear with a red exclamation point. &lt;/li&gt;            &lt;li&gt;Retag the same photo with the correct ancestor's name if it is not yet tagged. Determine this by confirming the default image associated with the ancestor's name you are typing.&amp;#160; &lt;/li&gt;            &lt;li&gt;Reload the People Photos section to confirm the second ancestor is now deleted.&lt;/li&gt;         &lt;/ol&gt;       &lt;/td&gt;     &lt;/tr&gt;   &lt;/tbody&gt;&lt;/table&gt;  &lt;p&gt;On Ancestry.com with its one set of persons, if I change a person’s name, I change it once. Likewise with birth and death years. On FamilySearch.org with its two sets of persons, I must change it twice, once for the tree person and once for the photo person. Likewise with birth and death years if they have been used to make the photo person name unique.&lt;/p&gt;  &lt;p&gt;In my opinion FamilySearch needs to unify its two systems of persons.&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;br /&gt;&lt;hr /&gt;
&lt;b&gt;Notice:&lt;/b&gt; The opinions expressed herein are those of the Ancestry Insider, not necessarily those of Ancestry.com or FamilySearch. All content is copyrighted by the Ancestry Insider unless designated otherwise. See http://ancestryinsider.blogspot.com for other important legal notices.&lt;/div&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/AncestryInsider?a=hutQpbDuOQE:eMPDdEl13HQ:2nqncYFp4_M"&gt;&lt;img src="http://feeds.feedburner.com/~ff/AncestryInsider?d=2nqncYFp4_M" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/AncestryInsider?a=hutQpbDuOQE:eMPDdEl13HQ:4cEx4HpKnUU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/AncestryInsider?i=hutQpbDuOQE:eMPDdEl13HQ:4cEx4HpKnUU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/AncestryInsider?a=hutQpbDuOQE:eMPDdEl13HQ:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/AncestryInsider?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/AncestryInsider/~4/hutQpbDuOQE" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://ancestryinsider.blogspot.com/feeds/678572459594329852/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://ancestryinsider.blogspot.com/2013/06/familysearchorg-photo-frustration.html#comment-form" title="4 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/5512311610334754148/posts/default/678572459594329852?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/5512311610334754148/posts/default/678572459594329852?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/AncestryInsider/~3/hutQpbDuOQE/familysearchorg-photo-frustration.html" title="FamilySearch.org Photo Frustration" /><author><name>The Ancestry Insider</name><uri>http://www.blogger.com/profile/02490682912125335188</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="30" src="http://bp1.blogger.com/_mpUi75C5vC8/SBgCr-W4YOI/AAAAAAAAAXA/K3itFGYLq_4/S220/simpsonized3.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://lh4.ggpht.com/-J72rXKrzCX0/UbNgSiYaMmI/AAAAAAAAEqU/-xWopNu_EFM/s72-c/371px-StateLibQld_1_186667_Twin_sisters_Kate_and_Emily_Bauer%25252C_ca_1915%25255B5%25255D.jpg?imgmax=800" height="72" width="72" /><thr:total>4</thr:total><feedburner:origLink>http://ancestryinsider.blogspot.com/2013/06/familysearchorg-photo-frustration.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CkAEQX86eyp7ImA9WhFTGU4.&quot;"><id>tag:blogger.com,1999:blog-5512311610334754148.post-7067550889835723997</id><published>2013-06-11T00:05:00.001-06:00</published><updated>2013-06-11T00:05:00.113-06:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2013-06-11T00:05:00.113-06:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="technology" /><category scheme="http://www.blogger.com/atom/ns#" term="FamilySearch" /><title>FamilySearch.org Announces GEDCOM X Progress</title><content type="html">&lt;p&gt;&lt;a href="http://www.gedcomx.org/" target="_blank"&gt;&lt;img title="GEDCOM X" style="border-top: 0px; border-right: 0px; background-image: none; border-bottom: 0px; float: right; padding-top: 0px; padding-left: 0px; border-left: 0px; display: inline; padding-right: 0px" border="0" alt="GEDCOM X" align="right" src="http://lh6.ggpht.com/-JtyxR6yq2jY/UbNxk4cX2sI/AAAAAAAAEqk/nkRTMMVYF0k/image%25255B4%25255D.png?imgmax=800" width="192" height="66" /&gt;&lt;/a&gt;In an email to developers on 4 June 2013, &lt;a href="http://FamilySearch.org" target="_blank"&gt;FamilySearch&lt;/a&gt; announced “the first stable milestone release of &lt;a href="http://www.gedcomx.org/Specifications.html" target="_blank"&gt;the core GEDCOM X specification set&lt;/a&gt;.” The announcement was repeated in a public &lt;a href="http://familysearch.github.io/gedcomx/2013/06/04/milestone-1.html" target="_blank"&gt;GEDCOM X blog post&lt;/a&gt; on the GEDCOM X website, &lt;a href="http://www.gedcomx.org" target="_blank"&gt;www.gedcomx.org&lt;/a&gt;. &lt;/p&gt;  &lt;p&gt;The email was targeted to software engineers, so it is pretty technical. Release of a specification does not mean there are any products or apps that utilize GEDCOM X yet. It doesn’t mean that anyone (besides &lt;a href="http://FamilySearch.org" target="_blank"&gt;FamilySearch&lt;/a&gt;) is or will use it.&lt;/p&gt;  &lt;p&gt;The “&lt;a href="https://github.com/FamilySearch/gedcomx/blob/master/specifications/conceptual-model-specification.md" target="_blank"&gt;GEDCOM X Conception Model&lt;/a&gt;” does mention sources, one of the key deficiencies in the current GEDCOM standard.&lt;/p&gt;  &lt;p&gt;The GEDCOM X website states that “the &lt;strong&gt;free flow&lt;/strong&gt; of genealogical data will enable every individual to:&lt;/p&gt;  &lt;ul&gt;   &lt;li&gt;Discover their family and heritage, preserve their identity, and publish their life story. &lt;/li&gt;    &lt;li&gt;Reduce duplication of sources, relationships, and identities. &lt;/li&gt;    &lt;li&gt;Identify people in photos, in documents, on gravestones, and in other sources of information. &lt;/li&gt;    &lt;li&gt;Keep track of the progress made in family research. &lt;/li&gt;    &lt;li&gt;Distribute and share genealogical information with others.” &lt;/li&gt; &lt;/ul&gt;  &lt;p&gt;A &lt;a href="https://www.google.com/search?q=site%3Afamilysearch.org+&amp;quot;GEDCOM+X&amp;quot;" target="_blank"&gt;Google site search of familysearch.org for &amp;quot;GEDCOM X&amp;quot;&lt;/a&gt; reveals &lt;a href="https://familysearch.org/developers/docs/guides/gedcom-x" target="_blank"&gt;a page&lt;/a&gt; in the &lt;a href="https://familysearch.org/developers/" target="_blank"&gt;FamilySearch Developer Center&lt;/a&gt; that states that “GEDCOM X is capable of preserving rich media content in &lt;strong&gt;a new file format&lt;/strong&gt;” (emphasis in the original). This is another of the key deficiencies in the current GEDCOM standard.&lt;/p&gt;  &lt;p&gt;The page also states that “the FamilySearch Family Tree API is built on this specification.” I interpret this to mean that &lt;a href="https://familysearch.org/products/" target="_blank"&gt;products that are Family Tree (FT) certified&lt;/a&gt; are already using the GEDCOM X specification to some degree.&lt;/p&gt;  &lt;p&gt;A &lt;a href="https://www.google.com/search?q=site%3Afamilysearch.org+&amp;quot;FHISO&amp;quot;" target="_blank"&gt;Google site search of familysearch.org for '&amp;quot;FHISO&amp;quot;&lt;/a&gt; shows two mentions on the FamilySearch.org website. &lt;a href="https://familysearch.org/developers/faq" target="_blank"&gt;One page&lt;/a&gt; encourages participation in technology communities working on family history, including “&lt;a href="http://fhiso.org/" target="_blank"&gt;FHISO&lt;/a&gt;: An international organization created to develop standards for the digital representation and sharing of family history and genealogical information.”&lt;/p&gt;  &lt;p&gt;The other leads to &lt;a href="https://familysearch.org/blog/en/office-cgo-cheif-genealogy-officer/#comment-29050" target="_blank"&gt;comments&lt;/a&gt; on &lt;a href="https://familysearch.org/blog/en/office-cgo-cheif-genealogy-officer/" target="_blank"&gt;a blog post&lt;/a&gt; about David Rencher, FamilySearch chief genealogical officer. One commenter, Michael McCormick, &lt;a href="https://familysearch.org/blog/en/office-cgo-cheif-genealogy-officer/#comment-29050" target="_blank"&gt;wrote&lt;/a&gt;, “No one at FamilySearch in PR or GEDCOMX responds to my request for a statement about FHISO relations.” Another commenter, Steve Anderson, posted &lt;a href="https://familysearch.org/blog/en/office-cgo-cheif-genealogy-officer/#comment-31121" target="_blank"&gt;this reply&lt;/a&gt;:&lt;/p&gt;  &lt;blockquote&gt;   &lt;p&gt;FamilySearch applauds and encourages industry standards that enable families to connect with their past, present and future. Where we have the need to share between different products and systems, we are looking at how we can best do so. Due to limited resources we have chosen not to participate in joint standards development at this time. If an industry standard emerges, we would seriously consider implementing it. When it is ready, we are open to submitting our own work, GEDCOMX, as the basis for a standard.&lt;/p&gt; &lt;/blockquote&gt;  

&lt;p&gt;Over the weekend FHISO, the Family History Information Standards Organisation, announced the appointment of Drew Smith as the first Chair of FHISO, effective 1 July 2013. Drew is currently the Organisational Member Representative to FHISO from the Federation of Genealogical Societies (FGS). In &lt;a href="http://fhiso.org/2013/06/drew-smith-appointed-chair-of-fhiso/" target="_blank"&gt;the press release&lt;/a&gt; announcing Smith's appointment, he is quoted as saying, "I recognize the critical importance of information standards, and as a long-time genealogist, I understand the needs of the world’s genealogy product and service vendors, repositories, societies, and individuals to collaborate and to share family history information. I look forward to leading an international effort to support the creation of these essential information standards." Smith's appointment drew support from FHISO members, Brightsolid, Ancestry.com, RootsMagic, and others. See the complete &lt;a href="http://fhiso.org/2013/06/drew-smith-appointed-chair-of-fhiso/" target="_blank"&gt;press release&lt;/a&gt; on the FHISO &lt;a href="http://fhiso.org" target="_blank"&gt;website&lt;/a&gt;.
&lt;/p&gt;

&lt;p&gt;I’m glad to see the progress of GEDCOM X and FHISO. The community has waited a long time for a successor to the current GEDCOM standard. It is encouraging to see any progress towards an updated standard.&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;br /&gt;&lt;hr /&gt;
&lt;b&gt;Notice:&lt;/b&gt; The opinions expressed herein are those of the Ancestry Insider, not necessarily those of Ancestry.com or FamilySearch. All content is copyrighted by the Ancestry Insider unless designated otherwise. See http://ancestryinsider.blogspot.com for other important legal notices.&lt;/div&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/AncestryInsider?a=wzVyT441dx4:51uOGAXNEWE:2nqncYFp4_M"&gt;&lt;img src="http://feeds.feedburner.com/~ff/AncestryInsider?d=2nqncYFp4_M" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/AncestryInsider?a=wzVyT441dx4:51uOGAXNEWE:4cEx4HpKnUU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/AncestryInsider?i=wzVyT441dx4:51uOGAXNEWE:4cEx4HpKnUU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/AncestryInsider?a=wzVyT441dx4:51uOGAXNEWE:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/AncestryInsider?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/AncestryInsider/~4/wzVyT441dx4" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://ancestryinsider.blogspot.com/feeds/7067550889835723997/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://ancestryinsider.blogspot.com/2013/06/familysearchorg-announces-gedcom-x.html#comment-form" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/5512311610334754148/posts/default/7067550889835723997?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/5512311610334754148/posts/default/7067550889835723997?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/AncestryInsider/~3/wzVyT441dx4/familysearchorg-announces-gedcom-x.html" title="FamilySearch.org Announces GEDCOM X Progress" /><author><name>The Ancestry Insider</name><uri>http://www.blogger.com/profile/02490682912125335188</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="30" src="http://bp1.blogger.com/_mpUi75C5vC8/SBgCr-W4YOI/AAAAAAAAAXA/K3itFGYLq_4/S220/simpsonized3.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://lh6.ggpht.com/-JtyxR6yq2jY/UbNxk4cX2sI/AAAAAAAAEqk/nkRTMMVYF0k/s72-c/image%25255B4%25255D.png?imgmax=800" height="72" width="72" /><thr:total>2</thr:total><feedburner:origLink>http://ancestryinsider.blogspot.com/2013/06/familysearchorg-announces-gedcom-x.html</feedburner:origLink></entry><entry gd:etag="W/&quot;D0YEQXY9fip7ImA9WhFTFUU.&quot;"><id>tag:blogger.com,1999:blog-5512311610334754148.post-3651137759355913832</id><published>2013-06-07T00:05:00.000-06:00</published><updated>2013-06-07T00:05:00.866-06:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2013-06-07T00:05:00.866-06:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Ancestry.com" /><category scheme="http://www.blogger.com/atom/ns#" term="search" /><title>Ancestry.com Revisiting Search</title><content type="html">&lt;p&gt;&lt;img title="Ancestry.com is refocusing and reinvesting in the search experience" style="border-top: 0px; border-right: 0px; background-image: none; border-bottom: 0px; float: right; padding-top: 0px; padding-left: 0px; border-left: 0px; display: inline; padding-right: 0px" border="0" alt="Ancestry.com is refocusing and reinvesting in the search experience" align="right" src="http://lh3.ggpht.com/-s0ktvju1V-s/UbFQ5YdEWnI/AAAAAAAAEp0/J1UyXYgVY98/image%25255B20%25255D.png?imgmax=800" width="250" height="161" /&gt;Ancestry.com is refocusing and reinvesting in the search experience, said Katharine Nester, director of product, and Dave Menninger, UX lead designer. Ancestry.com held private briefings with bloggers earlier this week to unveil several new search concepts. These concepts are still under investigation. Some might never see the light of day. Others might be changed from what we were shown, so we were asked not to show screen shots.&lt;/p&gt;  &lt;p&gt;For several years investment has been elsewhere: providing hints (shaky leaves), a new image viewer, and the 1940 census. Now Ancestry.com is investing again in the search experience because of the big impact it has on customer satisfaction. &lt;/p&gt;  &lt;p&gt;Part of that investment goes behind the scenes, changing infrastructure, improving performance, maintaining browser compatibility, and automating some steps in the publication process. Part of the investment will make a direct impact on users’ search experience.&lt;/p&gt;  &lt;p&gt;&lt;strong&gt;Better Use of Context&lt;/strong&gt;&lt;/p&gt;  &lt;p&gt;“Our results do not take into account records a user has already found or reviewed,” Nester said. Ancestry.com can make better use of user context. With 86% of subscribers having a member tree and at least 50% of searches specifying a person in the tree, the tree can be used to provide context and to capture context about the search for an ancestor.&lt;/p&gt;  &lt;p&gt;The search engine (system) already indicates what records in the search results you have already attached to that person. Many times a person is expected to appear in a collection only once. So if a result from, say, the 1940 census is already attached to the person in the tree, the search engine could be told to ignore that collection.&lt;/p&gt;  &lt;p&gt;Today users can review a search result and say “yes” that is my guy by attaching the record to their tree. Tomorrow users may be able to say yes, no, or maybe. A user would specify that a record is not a match for a person in their tree so that they were never shown that record again. (There would be some mechanism to see them, just not in the regular search results). If a record might be a match, they could stick it in a shoebox specific to that person.&lt;/p&gt;  &lt;p&gt;Ancestry.com is looking at better ways to facilitate comparison of the information in the record and the information in the tree. Today minimal information from the tree is shown in a box above the top of the search results. Tomorrow a fuller set of information might be shown side-by-side. Tomorrow a map might show the location indicated in the record versus other locations where the person was known to exist.&lt;/p&gt;  &lt;p&gt;&lt;strong&gt;Refining Search Results&lt;/strong&gt;&lt;/p&gt;  &lt;p&gt;Ancestry.com is considering several ways of filtering the number of search results, at the same time revealing the power of the match options currently available for each field on the advanced search page (like Soundex, exact match, adjacent county, and so forth).&lt;/p&gt;  &lt;p&gt;&lt;img title="The Google Maps magnification slider" style="border-top: 0px; border-right: 0px; background-image: none; border-bottom: 0px; float: right; padding-top: 0px; padding-left: 0px; border-left: 0px; display: inline; padding-right: 0px" border="0" alt="The Google Maps magnification slider" align="right" src="http://lh5.ggpht.com/-g2p7T3XaZao/UbFQ54mYAqI/AAAAAAAAEp8/hga3pPA2RXA/image%25255B9%25255D.png?imgmax=800" width="52" height="204" /&gt;One concept is to use sliders (like the Google Maps slider shown to the right). A slider would be provided for each search parameter, like first name, last name, location, and date. Zooming in would correspond to narrowing the number of results. &lt;/p&gt;  &lt;p&gt;Location might zoom from match on anywhere within the country, to states and adjacent states, to specified state, to county and adjacent counties, to county, or finally to exactly specified location. Date would narrow the range of matching years. Names might range from loose match including initials, to Soundex/phonetic matches, to exact match.&lt;/p&gt;  &lt;p&gt;Filtering might be provided for life stages. Users might select to show results corresponding to &lt;/p&gt;  &lt;ul&gt;   &lt;li&gt;All results&lt;/li&gt;    &lt;li&gt;Hints&lt;/li&gt;    &lt;li&gt;Records for the person as a married adult&lt;/li&gt;    &lt;li&gt;as a single adult&lt;/li&gt;    &lt;li&gt;as a child&lt;/li&gt;    &lt;li&gt;as an immigrant&lt;/li&gt;    &lt;li&gt;related to military&lt;/li&gt;    &lt;li&gt;or in a specific collection.&lt;/li&gt; &lt;/ul&gt;  &lt;p&gt;&lt;img title="Category filters on Ancestry.com" style="border-top: 0px; border-right: 0px; background-image: none; border-bottom: 0px; float: right; padding-top: 0px; padding-left: 0px; border-left: 0px; display: inline; padding-right: 0px" border="0" alt="Category filters on Ancestry.com" align="right" src="http://lh6.ggpht.com/-N0z_VexybwU/UbFQ6QtTsGI/AAAAAAAAEqE/2dF7z2B63_4/image%25255B13%25255D.png?imgmax=800" width="204" height="169" /&gt;Filters (called facets) might be provided that work a lot like online retail websites. Instead of filtering by price, manufacturer, and TV size, users would filter by location, date, and record category. Next to each facet is a number indicating the number of results in that facet. The category facet looks just like the category list today (shown to the right), except that a checkbox would be in front of each category. Users could select one or more categories, or drop out one or more, like the ever ubiquitous census results.&lt;/p&gt;  &lt;p&gt;&lt;strong&gt;Time Frame&lt;/strong&gt;&lt;/p&gt;  &lt;p&gt;Ancestry.com indicated there was no set timeframe for the release of these features. Some, the handling of attached records, could be released in the next month or two. Others could be released throughout the year. And some may not be released at all.&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;br /&gt;&lt;hr /&gt;
&lt;b&gt;Notice:&lt;/b&gt; The opinions expressed herein are those of the Ancestry Insider, not necessarily those of Ancestry.com or FamilySearch. All content is copyrighted by the Ancestry Insider unless designated otherwise. See http://ancestryinsider.blogspot.com for other important legal notices.&lt;/div&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/AncestryInsider?a=0yeL-8LL6NU:63mZkzT4sK8:2nqncYFp4_M"&gt;&lt;img src="http://feeds.feedburner.com/~ff/AncestryInsider?d=2nqncYFp4_M" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/AncestryInsider?a=0yeL-8LL6NU:63mZkzT4sK8:4cEx4HpKnUU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/AncestryInsider?i=0yeL-8LL6NU:63mZkzT4sK8:4cEx4HpKnUU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/AncestryInsider?a=0yeL-8LL6NU:63mZkzT4sK8:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/AncestryInsider?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/AncestryInsider/~4/0yeL-8LL6NU" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://ancestryinsider.blogspot.com/feeds/3651137759355913832/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://ancestryinsider.blogspot.com/2013/06/ancestrycom-revisiting-search.html#comment-form" title="5 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/5512311610334754148/posts/default/3651137759355913832?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/5512311610334754148/posts/default/3651137759355913832?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/AncestryInsider/~3/0yeL-8LL6NU/ancestrycom-revisiting-search.html" title="Ancestry.com Revisiting Search" /><author><name>The Ancestry Insider</name><uri>http://www.blogger.com/profile/02490682912125335188</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="30" src="http://bp1.blogger.com/_mpUi75C5vC8/SBgCr-W4YOI/AAAAAAAAAXA/K3itFGYLq_4/S220/simpsonized3.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://lh3.ggpht.com/-s0ktvju1V-s/UbFQ5YdEWnI/AAAAAAAAEp0/J1UyXYgVY98/s72-c/image%25255B20%25255D.png?imgmax=800" height="72" width="72" /><thr:total>5</thr:total><feedburner:origLink>http://ancestryinsider.blogspot.com/2013/06/ancestrycom-revisiting-search.html</feedburner:origLink></entry><entry gd:etag="W/&quot;AkAEQXw_fSp7ImA9WhFTFEQ.&quot;"><id>tag:blogger.com,1999:blog-5512311610334754148.post-5058156550094473503</id><published>2013-06-06T00:05:00.000-06:00</published><updated>2013-06-06T00:05:00.245-06:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2013-06-06T00:05:00.245-06:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Ancestry.com" /><category scheme="http://www.blogger.com/atom/ns#" term="search" /><title>What’s New at Ancestry.com: Home Page Changes</title><content type="html">&lt;p&gt;&lt;a href="http://www.ancestry.com/" target="_blank"&gt;Ancestry.com&lt;/a&gt; recently made changes to the search box on the home page. The changes make the form simpler, less powerful, and allows the page to load faster. &lt;/p&gt;  &lt;p&gt;&lt;a href="http://home.ancestry.com/" target="_blank"&gt;&lt;img title="New home page search form on Ancestry.com" style="border-left-width: 0px; border-right-width: 0px; background-image: none; border-bottom-width: 0px; padding-top: 0px; padding-left: 0px; display: inline; padding-right: 0px; border-top-width: 0px" border="0" alt="New home page search form on Ancestry.com" src="http://lh5.ggpht.com/-7EUC2sgrquY/UaE3X0vkhLI/AAAAAAAAEoM/M7q5xV-nYTk/image%25255B16%25255D.png?imgmax=800" width="604" height="208" /&gt;&lt;/a&gt;&lt;/p&gt;  &lt;p&gt;Previously the search form, in advanced mode, allowed specification of multiple events, multiple family members, keywords, gender, race, and collection types. It allowed fine control of matching for each field. None of these are now available except the ability to specify one place and a birth year. Oh yah, you can also limit record results to US collections (similar to the &lt;a href="http://FamilySearch.org" target="_blank"&gt;FamilySearch&lt;/a&gt; restrict feature I mentioned last week).&lt;/p&gt;  &lt;p&gt;Advanced search capabilities are still available on the Search page. Click “Show Advanced” in the search form or click Search on the menu.&lt;/p&gt;  &lt;p&gt;&lt;a href="http://www.ancestry.com/" target="_blank"&gt;&lt;img title="Location of Ancestry.com home page ads" style="border-left-width: 0px; border-right-width: 0px; background-image: none; border-bottom-width: 0px; float: right; padding-top: 0px; padding-left: 0px; display: inline; padding-right: 0px; border-top-width: 0px" border="0" alt="Location of Ancestry.com home page ads" align="right" src="http://lh6.ggpht.com/-EygT2Gy-kGs/UaE3YU3fzrI/AAAAAAAAEoU/Ne7yCWRKK0M/image%25255B17%25255D.png?imgmax=800" width="167" height="204" /&gt;&lt;/a&gt;Also on the home page, when logged in, Ancestry.com now, always, displays an advertisement to one of its own products in a banner across the top of the page. It also displays an ad, again promoting its own stuff, inside the “What’s Happening” box part-way down the page on the left side. At times it also displays an ad at the very bottom of the right-hand column.&lt;/p&gt;  &lt;p&gt;For more information, check out &lt;a href="http://www.youtube.com/watch?v=lY0FBu-R1-U&amp;amp;feature=youtu.be" target="_blank"&gt;Crista Cowan’s YouTube video&lt;/a&gt;.&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;br /&gt;&lt;hr /&gt;
&lt;b&gt;Notice:&lt;/b&gt; The opinions expressed herein are those of the Ancestry Insider, not necessarily those of Ancestry.com or FamilySearch. All content is copyrighted by the Ancestry Insider unless designated otherwise. See http://ancestryinsider.blogspot.com for other important legal notices.&lt;/div&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/AncestryInsider?a=EoxFbknl-Dw:riM9-jG7Xqw:2nqncYFp4_M"&gt;&lt;img src="http://feeds.feedburner.com/~ff/AncestryInsider?d=2nqncYFp4_M" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/AncestryInsider?a=EoxFbknl-Dw:riM9-jG7Xqw:4cEx4HpKnUU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/AncestryInsider?i=EoxFbknl-Dw:riM9-jG7Xqw:4cEx4HpKnUU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/AncestryInsider?a=EoxFbknl-Dw:riM9-jG7Xqw:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/AncestryInsider?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/AncestryInsider/~4/EoxFbknl-Dw" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://ancestryinsider.blogspot.com/feeds/5058156550094473503/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://ancestryinsider.blogspot.com/2013/06/whats-new-at-ancestrycom-home-page.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/5512311610334754148/posts/default/5058156550094473503?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/5512311610334754148/posts/default/5058156550094473503?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/AncestryInsider/~3/EoxFbknl-Dw/whats-new-at-ancestrycom-home-page.html" title="What’s New at Ancestry.com: Home Page Changes" /><author><name>The Ancestry Insider</name><uri>http://www.blogger.com/profile/02490682912125335188</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="30" src="http://bp1.blogger.com/_mpUi75C5vC8/SBgCr-W4YOI/AAAAAAAAAXA/K3itFGYLq_4/S220/simpsonized3.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://lh5.ggpht.com/-7EUC2sgrquY/UaE3X0vkhLI/AAAAAAAAEoM/M7q5xV-nYTk/s72-c/image%25255B16%25255D.png?imgmax=800" height="72" width="72" /><thr:total>0</thr:total><feedburner:origLink>http://ancestryinsider.blogspot.com/2013/06/whats-new-at-ancestrycom-home-page.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CEQEQX88fip7ImA9WhFTFEw.&quot;"><id>tag:blogger.com,1999:blog-5512311610334754148.post-7422754362432372334</id><published>2013-06-05T00:05:00.000-06:00</published><updated>2013-06-05T00:05:00.176-06:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2013-06-05T00:05:00.176-06:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="FamilySearch.org" /><category scheme="http://www.blogger.com/atom/ns#" term="search" /><title>FamilySearch.org Search Futures</title><content type="html">&lt;p&gt;Before I tell you about features coming soon to &lt;a href="http://FamilySearch.org" target="_blank"&gt;FamilySearch&lt;/a&gt;.org’s historical records search engine, let me point out a two new features.&lt;/p&gt;  &lt;p&gt;&lt;a href="https://familysearch.org/search/record/results#count=20&amp;amp;query=%2Bgivenname%3AJohn~%20%2Bsurname%3ASider~%20%2Bresidence_place%3A%22New%20*%22" target="_blank"&gt;&lt;img title="Set the number of search results on FamilySearch.org historical records" style="border-top: 0px; border-right: 0px; background-image: none; border-bottom: 0px; float: right; padding-top: 0px; padding-left: 0px; border-left: 0px; display: inline; padding-right: 0px" border="0" alt="Set the number of search results on FamilySearch.org historical records" align="right" src="http://lh5.ggpht.com/-DUUEVqt2JlY/UarAKUER26I/AAAAAAAAEpU/BMAcjO2f20E/image%25255B5%25255D.png?imgmax=800" width="420" height="220" /&gt;&lt;/a&gt;By default, FamilySearch.org shows 20 search results from historical records. Above the first result, click 20, 50, or 75 to set the number of results shown.    &lt;br clear="all" /&gt;Many websites are trying to ride the social media wave and FamilySearch.org is no exception. FamilySearch has added the ability to share a historical record on popular social media sites. Look for the Share icon on the right side of the window.&lt;/p&gt;  &lt;p&gt;&lt;a href="http://lh4.ggpht.com/-sDiEFbEsG8U/UarALnY_cJI/AAAAAAAAEpc/5fDKInwDGU0/s1600-h/image%25255B13%25255D.png"&gt;&lt;img title="image" style="border-top: 0px; border-right: 0px; background-image: none; border-bottom: 0px; padding-top: 0px; padding-left: 0px; border-left: 0px; display: inline; padding-right: 0px" border="0" alt="image" src="http://lh6.ggpht.com/-P2YjAGcDAhA/UarAM_10J8I/AAAAAAAAEpk/qL-pzptA_sw/image_thumb%25255B6%25255D.png?imgmax=800" width="604" height="354" /&gt;&lt;/a&gt;&lt;/p&gt;  &lt;p&gt;Robert Kehrer, FamilySearch product manager, has &lt;a href="https://familysearch.org/blog/en/search-stays-true-experienced-family-history-users/" target="_blank"&gt;announced&lt;/a&gt; these upcoming features:&lt;/p&gt;  &lt;p&gt;&lt;strong&gt;View a Person Record Linked to Family Tree     &lt;br /&gt;&lt;/strong&gt;When a historical record is already linked to a person in the Family Tree you will see a link that will let you go directly to the person in the Family Tree.&lt;/p&gt;  &lt;p&gt;&lt;strong&gt;Link a Person Record Directly to Family Tree&lt;/strong&gt;    &lt;br /&gt;If a historical records is not linked to Family Tree, you will be able to quickly look for them in the Family Tree and create the source in the Family Tree. FamilySearch will add the link to the source box for you, as well, so you can further organize it in the source box if you wish.&lt;/p&gt;  &lt;p&gt;&lt;strong&gt;Export Search Results to a Spreadsheet     &lt;br /&gt;&lt;/strong&gt;Logged-in researchers will be able to export the data from their search results into a spreadsheet so they can sort, label, and organize these records in their research workflows.&lt;/p&gt;  &lt;p&gt;&lt;strong&gt;Comment on a Historical Record     &lt;br /&gt;&lt;/strong&gt;Researchers will be able to leave comments on a record that is viewable by all other FamilySearch.org users. FamilySearch will allow you to flag these comments as being a correction to the transcribed data on the record. It may be a while before these changes are displayed and searched as part of the record, but for the first time you will be able to officially record errors in the record.&lt;/p&gt;  &lt;p&gt;&lt;strong&gt;Filter Catalog Titles by Location     &lt;br /&gt;&lt;/strong&gt;The FamilySearch Catalog now holds many titles from the regional libraries and even some Family History Centers. You will soon have the ability to see all the titles that are held in a specific library or center.&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;br /&gt;&lt;hr /&gt;
&lt;b&gt;Notice:&lt;/b&gt; The opinions expressed herein are those of the Ancestry Insider, not necessarily those of Ancestry.com or FamilySearch. All content is copyrighted by the Ancestry Insider unless designated otherwise. See http://ancestryinsider.blogspot.com for other important legal notices.&lt;/div&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/AncestryInsider?a=cpCjZtqFiQE:j6y2YyzeIv4:2nqncYFp4_M"&gt;&lt;img src="http://feeds.feedburner.com/~ff/AncestryInsider?d=2nqncYFp4_M" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/AncestryInsider?a=cpCjZtqFiQE:j6y2YyzeIv4:4cEx4HpKnUU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/AncestryInsider?i=cpCjZtqFiQE:j6y2YyzeIv4:4cEx4HpKnUU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/AncestryInsider?a=cpCjZtqFiQE:j6y2YyzeIv4:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/AncestryInsider?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/AncestryInsider/~4/cpCjZtqFiQE" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://ancestryinsider.blogspot.com/feeds/7422754362432372334/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://ancestryinsider.blogspot.com/2013/06/familysearchorg-search-futures.html#comment-form" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/5512311610334754148/posts/default/7422754362432372334?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/5512311610334754148/posts/default/7422754362432372334?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/AncestryInsider/~3/cpCjZtqFiQE/familysearchorg-search-futures.html" title="FamilySearch.org Search Futures" /><author><name>The Ancestry Insider</name><uri>http://www.blogger.com/profile/02490682912125335188</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="30" src="http://bp1.blogger.com/_mpUi75C5vC8/SBgCr-W4YOI/AAAAAAAAAXA/K3itFGYLq_4/S220/simpsonized3.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://lh5.ggpht.com/-DUUEVqt2JlY/UarAKUER26I/AAAAAAAAEpU/BMAcjO2f20E/s72-c/image%25255B5%25255D.png?imgmax=800" height="72" width="72" /><thr:total>1</thr:total><feedburner:origLink>http://ancestryinsider.blogspot.com/2013/06/familysearchorg-search-futures.html</feedburner:origLink></entry><entry gd:etag="W/&quot;D04EQX05fyp7ImA9WhFTE08.&quot;"><id>tag:blogger.com,1999:blog-5512311610334754148.post-8531691050824756111</id><published>2013-06-04T00:05:00.001-06:00</published><updated>2013-06-04T00:05:00.327-06:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2013-06-04T00:05:00.327-06:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Ancestry.com" /><title>Ancestry.com new Story View</title><content type="html">&lt;p&gt;Various sources are reporting that &lt;a href="http://www.ancestry.com/" target="_blank"&gt;Ancestry.com&lt;/a&gt; is testing a new feature for member trees called “Story View.” &lt;a href="http://gigaom.com/2013/05/27/how-ancestry-com-transforms-mounds-of-data-into-legible-digital-records/" target="_blank"&gt;According to Jordan Novet&lt;/a&gt; of GigaOM, Ancestry.com uses software from Narrative Science which takes facts from the documents and photographs attached to a person in a public member tree and uses a computer algorithm to construct a narrative describing their life. Novet wrote that Ancestry.com is rolling out the feature slowly, currently making it available to 10% of users.&lt;/p&gt;  &lt;p&gt;&lt;a href="http://story.sharing.ancestry.com/people/62060?h=dcf905" target="_blank"&gt;&lt;img title="Frederick Walton Seaver&amp;#39;s story view on Ancestry.com" style="border-top: 0px; border-right: 0px; background-image: none; border-bottom: 0px; float: right; padding-top: 0px; padding-left: 0px; border-left: 0px; display: inline; padding-right: 0px" border="0" alt="Frederick Walton Seaver&amp;#39;s story view on Ancestry.com" align="right" src="http://lh6.ggpht.com/-qE47cLWuC4c/UapdirYZCbI/AAAAAAAAEo0/zrvceMnDoNE/image%25255B5%25255D.png?imgmax=800" width="304" height="242" /&gt;&lt;/a&gt;Randy Seaver is one of those with access to the feature and reviewed it in his blog last Friday. (See “&lt;a href="http://www.geneamusings.com/2013/05/first-look-at-ancestrycoms-story-view.html" target="_blank"&gt;First Look at Ancestry.com’s Story View&lt;/a&gt;.”) He clicked a green button on a person page to generate a Story View of that person (shown to the right). &lt;/p&gt;  &lt;p&gt;The top of the page consists of the principal photograph of the person and a paragraph constructed by computer that gives a short biography of the person.&lt;/p&gt;  &lt;p&gt;Underneath this Ancestry.com constructs a timeline using the images associated with that person. Next to each image is a date and description, which can be edited and reordered.&lt;/p&gt;  &lt;p&gt;The resulting story can be shared with the general public. To see Seaver’s, &lt;a href="http://story.sharing.ancestry.com/people/62060?h=dcf905" target="_blank"&gt;click here&lt;/a&gt;.&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;br /&gt;&lt;hr /&gt;
&lt;b&gt;Notice:&lt;/b&gt; The opinions expressed herein are those of the Ancestry Insider, not necessarily those of Ancestry.com or FamilySearch. All content is copyrighted by the Ancestry Insider unless designated otherwise. See http://ancestryinsider.blogspot.com for other important legal notices.&lt;/div&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/AncestryInsider?a=bQQ7CJU7aFk:GIS8G3cvTHE:2nqncYFp4_M"&gt;&lt;img src="http://feeds.feedburner.com/~ff/AncestryInsider?d=2nqncYFp4_M" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/AncestryInsider?a=bQQ7CJU7aFk:GIS8G3cvTHE:4cEx4HpKnUU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/AncestryInsider?i=bQQ7CJU7aFk:GIS8G3cvTHE:4cEx4HpKnUU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/AncestryInsider?a=bQQ7CJU7aFk:GIS8G3cvTHE:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/AncestryInsider?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/AncestryInsider/~4/bQQ7CJU7aFk" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://ancestryinsider.blogspot.com/feeds/8531691050824756111/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://ancestryinsider.blogspot.com/2013/06/ancestrycom-new-story-view.html#comment-form" title="4 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/5512311610334754148/posts/default/8531691050824756111?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/5512311610334754148/posts/default/8531691050824756111?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/AncestryInsider/~3/bQQ7CJU7aFk/ancestrycom-new-story-view.html" title="Ancestry.com new Story View" /><author><name>The Ancestry Insider</name><uri>http://www.blogger.com/profile/02490682912125335188</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="30" src="http://bp1.blogger.com/_mpUi75C5vC8/SBgCr-W4YOI/AAAAAAAAAXA/K3itFGYLq_4/S220/simpsonized3.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://lh6.ggpht.com/-qE47cLWuC4c/UapdirYZCbI/AAAAAAAAEo0/zrvceMnDoNE/s72-c/image%25255B5%25255D.png?imgmax=800" height="72" width="72" /><thr:total>4</thr:total><feedburner:origLink>http://ancestryinsider.blogspot.com/2013/06/ancestrycom-new-story-view.html</feedburner:origLink></entry><entry gd:etag="W/&quot;A0IEQX86fCp7ImA9WhFTEk4.&quot;"><id>tag:blogger.com,1999:blog-5512311610334754148.post-6589950302659898037</id><published>2013-06-03T00:05:00.000-06:00</published><updated>2013-06-03T00:05:00.114-06:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2013-06-03T00:05:00.114-06:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Ancestry.com" /><category scheme="http://www.blogger.com/atom/ns#" term="records" /><category scheme="http://www.blogger.com/atom/ns#" term="FamilySearch" /><title>Monday Mailbox: FamilySearch vs. Ancestry.com Record Acquisition</title><content type="html">&lt;p&gt;&lt;img title="The Ancestry Insider&amp;#39;s Monday Mailbox" alt="The Ancestry Insider&amp;#39;s Monday Mailbox" align="right" src="http://lh5.ggpht.com/-APPONy4CQu8/USAiyzrNeFI/AAAAAAAAESE/bnD36sCu0V4/Mailbox%252520from%252520W%252520300_thumb%25255B2%25255D.png?imgmax=800" /&gt;Dear Ancestry Insider,&lt;/p&gt;  &lt;blockquote&gt;   &lt;p&gt;Two questions.&lt;/p&gt;    &lt;p&gt;1) Does FamilySearch have the same records as Ancestry.com because there are two teams of people photographing the same materials? Or, do the different entities keep each area with some propriety, so that there are fewer duplicates?&lt;/p&gt;    &lt;p&gt;2) Are there any plans to go back to some of the older records, for example, in Italy, where the first microfiche records are so poor? &lt;/p&gt;    &lt;p&gt;Signed,     &lt;br /&gt;bldgdiva&lt;/p&gt; &lt;/blockquote&gt;  &lt;p&gt;Dear bldgdiva,&lt;/p&gt;  &lt;p&gt;&lt;a href="http://www.ancestry.com/" target="_blank"&gt;Ancestry.com&lt;/a&gt; and &lt;a href="http://FamilySearch.org" target="_blank"&gt;FamilySearch&lt;/a&gt; have been known to swap records. That would explain why some collections are present on both websites. &lt;/p&gt;  &lt;p&gt;For example, &lt;a href="https://www.familysearch.org/learn/wiki/en/Nevada,_Marriage_Index_%28FamilySearch_Historical_Records%29" target="_blank"&gt;according to the FamilySearch Wiki&lt;/a&gt;, FamilySearch obtained the “&lt;a href="https://www.familysearch.org/search/collection/1949338" target="_blank"&gt;Nevada, Marriage Index, 1956-2005&lt;/a&gt;” record collection from Ancestry.com. And according to the Ancestry.com website, Ancestry.com obtained the “&lt;a href="http://search.ancestry.com/search/db.aspx?dbid=2547" target="_blank"&gt;Iowa, Births and Christenings Index, 1857-1947&lt;/a&gt;” collection from FamilySearch. According to an Ancestry.com &lt;a href="http://corporate.ancestry.com/press/press-releases/2008/07/familysearch-and-ancestry.com-team-to-publish-new-images-and-enhanced-indexes-to-the-u.s.-censuses/" target="_blank"&gt;press release&lt;/a&gt;, FamilySearch and Ancestry.com traded some U.S. census images and indexes. &lt;/p&gt;  &lt;p&gt;Sometimes the two organizations work together on a project. At RootsTech this year, Ancestry.com’s Tim Sullivan &lt;a href="http://ancestryinsider.blogspot.com/2013/03/from-rootstech-ancestrycom-partnering.html" target="_blank"&gt;announced&lt;/a&gt; “our largest and most ambitious collaboration with FamilySearch, ever.” The two will work together to digitize, index, and publish U.S. probate records.&lt;/p&gt;  &lt;p&gt;Some records are present on both websites because both organizations have digitized the same microfilm. I think NARA microfilm M1509 is an example. It is published as “&lt;a href="http://search.ancestry.com/search/db.aspx?dbid=6482" target="_blank"&gt;U.S., World War I Draft Registration Cards, 1917-1918&lt;/a&gt;” on Ancestry.com and as “&lt;a href="https://www.familysearch.org/search/collection/1968530" target="_blank"&gt;United States, World War I Draft Registration Cards, 1917-1918&lt;/a&gt;” on FamilySearch.org.&lt;/p&gt;  &lt;p&gt;Both companies have their own digitization teams out imaging records. (Nearly two years ago I published &lt;a href="http://ancestryinsider.blogspot.com/2011/10/awesome-maps.html" target="_blank"&gt;maps&lt;/a&gt; showing the locations of each organization’s digitization teams at the time. Click on the maps to enlarge.) I suppose duplication could occur, but typically archives won’t allow it. Handling records causes deterioration so archives don’t like two entities both photographing the same records.&lt;/p&gt;  &lt;p&gt;As to going back to retake photographs of records already on film or fiche: I suppose it could happen, but I think these organizations get more return on their investment by going after new records. &lt;/p&gt;  &lt;p&gt;That said, I know that &lt;a href="http://FamilySearch.org" target="_blank"&gt;FamilySearch&lt;/a&gt; is digitizing more than 115 million images of Italian birth, marriage, and death certificates. (See “&lt;a href="https://familysearch.org/italian-ancestors/" target="_blank"&gt;Italian Ancestors: Making Italy Civil Registration Records Freely Searchable Online&lt;/a&gt;.”) Perhaps they will get the records you need. If you can read Italian records, I’m sure they would be happy if you would help out.&lt;/p&gt;  &lt;p&gt;&lt;a href="https://familysearch.org/italian-ancestors/" target="_blank"&gt;&lt;img title="FamilySearch Italian Ancestors project" style="border-top: 0px; border-right: 0px; background-image: none; border-bottom: 0px; padding-top: 0px; padding-left: 0px; border-left: 0px; display: inline; padding-right: 0px" border="0" alt="FamilySearch Italian Ancestors project" src="http://lh4.ggpht.com/-Twsn0oySifU/Uap3H_g-h6I/AAAAAAAAEpE/0wMtjl68Xwc/image%25255B4%25255D.png?imgmax=800" width="604" height="324" /&gt;&lt;/a&gt;&lt;/p&gt;  &lt;p&gt;Signed,   &lt;br /&gt;&lt;a href="http://ancestryinsider.blogspot.com"&gt;The Ancestry Insider&lt;/a&gt;&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;br /&gt;&lt;hr /&gt;
&lt;b&gt;Notice:&lt;/b&gt; The opinions expressed herein are those of the Ancestry Insider, not necessarily those of Ancestry.com or FamilySearch. All content is copyrighted by the Ancestry Insider unless designated otherwise. See http://ancestryinsider.blogspot.com for other important legal notices.&lt;/div&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/AncestryInsider?a=Lz591GLrwxI:m0MrhS0qFzk:2nqncYFp4_M"&gt;&lt;img src="http://feeds.feedburner.com/~ff/AncestryInsider?d=2nqncYFp4_M" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/AncestryInsider?a=Lz591GLrwxI:m0MrhS0qFzk:4cEx4HpKnUU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/AncestryInsider?i=Lz591GLrwxI:m0MrhS0qFzk:4cEx4HpKnUU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/AncestryInsider?a=Lz591GLrwxI:m0MrhS0qFzk:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/AncestryInsider?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/AncestryInsider/~4/Lz591GLrwxI" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://ancestryinsider.blogspot.com/feeds/6589950302659898037/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://ancestryinsider.blogspot.com/2013/06/monday-mailbox-familysearch-vs.html#comment-form" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/5512311610334754148/posts/default/6589950302659898037?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/5512311610334754148/posts/default/6589950302659898037?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/AncestryInsider/~3/Lz591GLrwxI/monday-mailbox-familysearch-vs.html" title="Monday Mailbox: FamilySearch vs. Ancestry.com Record Acquisition" /><author><name>The Ancestry Insider</name><uri>http://www.blogger.com/profile/02490682912125335188</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="30" src="http://bp1.blogger.com/_mpUi75C5vC8/SBgCr-W4YOI/AAAAAAAAAXA/K3itFGYLq_4/S220/simpsonized3.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://lh5.ggpht.com/-APPONy4CQu8/USAiyzrNeFI/AAAAAAAAESE/bnD36sCu0V4/s72-c/Mailbox%252520from%252520W%252520300_thumb%25255B2%25255D.png?imgmax=800" height="72" width="72" /><thr:total>2</thr:total><feedburner:origLink>http://ancestryinsider.blogspot.com/2013/06/monday-mailbox-familysearch-vs.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DEIFSX8-cCp7ImA9WhFTEUw.&quot;"><id>tag:blogger.com,1999:blog-5512311610334754148.post-7339420239802103095</id><published>2013-06-01T13:55:00.001-06:00</published><updated>2013-06-01T13:55:18.158-06:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2013-06-01T13:55:18.158-06:00</app:edited><title>Breaking News: Family History Library Security Concern Saturday</title><content type="html">&lt;p&gt;A couple in my neighborhood reported earlier today (Saturday afternoon) that they were turned away at the &lt;a href="http://FamilySearch.org" target="_blank"&gt;FamilySearch&lt;/a&gt; Family History Library for “a security concern.”&lt;/p&gt;  &lt;p&gt;Michael John Neill reported on his Facebook page a couple of hours ago that “The Family History Library in Salt Lake is closed today, unexpectedly for unspecified reasons.”&lt;/p&gt;  &lt;p&gt;I will let you know when I know more.&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;br /&gt;&lt;hr /&gt;
&lt;b&gt;Notice:&lt;/b&gt; The opinions expressed herein are those of the Ancestry Insider, not necessarily those of Ancestry.com or FamilySearch. All content is copyrighted by the Ancestry Insider unless designated otherwise. See http://ancestryinsider.blogspot.com for other important legal notices.&lt;/div&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/AncestryInsider?a=z2N_uV68UGQ:l3OVT3d9Xq0:2nqncYFp4_M"&gt;&lt;img src="http://feeds.feedburner.com/~ff/AncestryInsider?d=2nqncYFp4_M" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/AncestryInsider?a=z2N_uV68UGQ:l3OVT3d9Xq0:4cEx4HpKnUU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/AncestryInsider?i=z2N_uV68UGQ:l3OVT3d9Xq0:4cEx4HpKnUU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/AncestryInsider?a=z2N_uV68UGQ:l3OVT3d9Xq0:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/AncestryInsider?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/AncestryInsider/~4/z2N_uV68UGQ" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://ancestryinsider.blogspot.com/feeds/7339420239802103095/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://ancestryinsider.blogspot.com/2013/06/breaking-news-family-history-library.html#comment-form" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/5512311610334754148/posts/default/7339420239802103095?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/5512311610334754148/posts/default/7339420239802103095?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/AncestryInsider/~3/z2N_uV68UGQ/breaking-news-family-history-library.html" title="Breaking News: Family History Library Security Concern Saturday" /><author><name>The Ancestry Insider</name><uri>http://www.blogger.com/profile/02490682912125335188</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="30" src="http://bp1.blogger.com/_mpUi75C5vC8/SBgCr-W4YOI/AAAAAAAAAXA/K3itFGYLq_4/S220/simpsonized3.jpg" /></author><thr:total>2</thr:total><feedburner:origLink>http://ancestryinsider.blogspot.com/2013/06/breaking-news-family-history-library.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CkQEQX44eip7ImA9WhBaGUU.&quot;"><id>tag:blogger.com,1999:blog-5512311610334754148.post-1169835226100957350</id><published>2013-05-31T00:05:00.000-06:00</published><updated>2013-05-31T00:05:00.032-06:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2013-05-31T00:05:00.032-06:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="serendipity" /><title>Serendipity in Carpooling</title><content type="html">&lt;p&gt;Calvin Knight of Kaysville, Utah used to drive Bryan Wise to work each day because of Bryan’s health. Bryan was Calvin’s brother-in-law and a good friend.&lt;sup&gt;1&lt;/sup&gt;&lt;/p&gt;  &lt;p&gt;Bryan passed away on 27 May 2010 from an aneurysm.&lt;sup&gt;2&lt;/sup&gt;&lt;/p&gt;  &lt;blockquote&gt;   &lt;p&gt;Those who knew Bryan loved his keen sense of humor, his lively stories, and his positive outlook on life, despite serious health challenges for the past three years. Even in his final hours, he made family members and caregivers laugh and feel better themselves.&lt;sup&gt;3&lt;/sup&gt;&lt;/p&gt; &lt;/blockquote&gt;  &lt;p&gt;One day Calvin was reading some of the journal of his 3rd great-grandfather, Miner G. Atwood. &lt;/p&gt;  &lt;p&gt;Miner led an immigrant company of Mormons to Utah in 1865.&lt;sup&gt;4&lt;/sup&gt;&lt;/p&gt;  &lt;blockquote&gt;   &lt;p&gt;Wednesday, August 16. Last evening the cattle were very restless, some straying away, but they were all found. Started at 9 a. m; traveled five miles and camped on Beaver Creek, one and a half miles from Nebraska. (The southern boundary of the State of Nebraska.) Here a sister [Phoebe Hatton Wise] came to me and begged to be taken on to the [Salt Lake] Valley with her husband and son; I had room made for them in different wagons and brought them along. Brother Thos. Wise, the husband, gave me six dollars towards their provisions..&lt;sup&gt;5&lt;/sup&gt;&lt;/p&gt; &lt;/blockquote&gt;  &lt;p&gt;Calvin was intrigued by the common surname between his friend, Bryan Wise, and his ancestor’s acquaintance, Thomas Wise. He opened up &lt;a href="http://FamilySearch.org" target="_blank"&gt;FamilySearch&lt;/a&gt; Family Tree and found the connection.&lt;/p&gt;  &lt;p&gt;&lt;a href="https://familysearch.org/tree/#view=tree&amp;amp;person=KW8X-QSH&amp;amp;section=pedigree" target="_blank"&gt;&lt;img title="Pedigree of Wallace Keith Wise" style="border-top: 0px; border-right: 0px; background-image: none; border-bottom: 0px; padding-top: 0px; padding-left: 0px; border-left: 0px; display: inline; padding-right: 0px" border="0" alt="Pedigree of Wallace Keith Wise" src="http://lh3.ggpht.com/-MqdWoWGukDk/UagN2bZlckI/AAAAAAAAEok/tqaO2USGCZk/image%25255B9%25255D.png?imgmax=800" width="504" height="268" /&gt;&lt;/a&gt;&lt;/p&gt;  &lt;p&gt;One hundred forty-five years before Calvin was driving his friend Bryan to work, Calvin’s 3rd great grandfather arranged a ride for Bryan’s 3rd great grandfather, not just to work, but across the great plains to a new life in the Utah Territory.&lt;/p&gt;  &lt;p&gt;That is called &lt;em&gt;serendipity in genealogy&lt;/em&gt;.&lt;/p&gt;  &lt;p&gt;   &lt;hr /&gt;&lt;strong&gt;Sources&lt;/strong&gt;&lt;/p&gt;  &lt;p&gt;&amp;#160;&amp;#160;&amp;#160;&amp;#160; 1. Calvin Knight, “&lt;a href="http://www.ldschurchnews.com/articles/63587/Family-history-moments-Meeting-on-the-trail.html" target="_blank"&gt;Family History Moments: Meeting on the Trail&lt;/a&gt;,” &lt;em&gt;Church News, &lt;/em&gt;&lt;em&gt;The Church&lt;/em&gt;&lt;em&gt; of &lt;/em&gt;&lt;em&gt;Jesus Christ&lt;/em&gt;&lt;em&gt; of Letter-day Saints,&lt;/em&gt; online edition (&lt;a href="http://www.ldschurchnews.com" target="_blank"&gt;www.ldschurchnews.com&lt;/a&gt; : accessed 30 May 2013); print edition, 26 May 2013, p. 16, col. 3. This is the source for my entire article except as otherwise noted.&lt;/p&gt;  &lt;p&gt;&amp;#160;&amp;#160;&amp;#160;&amp;#160; 2. “&lt;a href="http://www.legacy.com/obituaries/deseretnews/obituary.aspx?n=bryan-wise&amp;amp;pid=143212899#fbLoggedOut" target="_blank"&gt;Bryan Wise Obituary&lt;/a&gt;,” &lt;em&gt;Deseret News [Obituaries]&lt;/em&gt; (&lt;a title="http://www.legacy.com/obituaries/deseretnews/" href="http://www.legacy.com/obituaries/deseretnews/" target="_blank"&gt;http://www.legacy.com/obituaries/deseretnews/&lt;/a&gt; : Legacy.com, accessed 30 May 2013); citing print edition, &lt;em&gt;Deseret News &lt;em&gt;(Salt Lake City, Utah)&lt;/em&gt;&lt;/em&gt;, 30 May 2010.&lt;/p&gt;  &lt;p&gt;&amp;#160;&amp;#160;&amp;#160;&amp;#160; 3. Ibid.&lt;/p&gt;  &lt;p&gt;&amp;#160;&amp;#160;&amp;#160;&amp;#160; 4. Church History Department, “&lt;a href="http://history.lds.org/overlandtravels/" target="_blank"&gt;Mormon Pioneer Overland Travel&lt;/a&gt;,” database, &lt;em&gt;The Church of Jesus Christ of Latter-day Saints [Church History website]&lt;/em&gt; (&lt;a href="http://history.lds.org"&gt;http://history.lds.org&lt;/a&gt; : accessed 30 May 2013), Miner G. Atwood Company, &lt;a href="http://history.lds.org/overlandtravels/trailExcerptMulti?lang=eng&amp;amp;companyId=57&amp;amp;sourceId=4780" target="_blank"&gt;trail excerpt&lt;/a&gt; citing “Atwood, Miner G., [Journal], in Journal History of The Church of Jesus Christ of Latter-day Saints, 8 Nov. 1865, 8-22.”&lt;/p&gt;  &lt;p&gt;&amp;#160;&amp;#160;&amp;#160;&amp;#160; 5. Ibid.&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;br /&gt;&lt;hr /&gt;
&lt;b&gt;Notice:&lt;/b&gt; The opinions expressed herein are those of the Ancestry Insider, not necessarily those of Ancestry.com or FamilySearch. All content is copyrighted by the Ancestry Insider unless designated otherwise. See http://ancestryinsider.blogspot.com for other important legal notices.&lt;/div&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/AncestryInsider?a=OCYZpJhmHyg:lEPGtEx82KU:2nqncYFp4_M"&gt;&lt;img src="http://feeds.feedburner.com/~ff/AncestryInsider?d=2nqncYFp4_M" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/AncestryInsider?a=OCYZpJhmHyg:lEPGtEx82KU:4cEx4HpKnUU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/AncestryInsider?i=OCYZpJhmHyg:lEPGtEx82KU:4cEx4HpKnUU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/AncestryInsider?a=OCYZpJhmHyg:lEPGtEx82KU:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/AncestryInsider?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/AncestryInsider/~4/OCYZpJhmHyg" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://ancestryinsider.blogspot.com/feeds/1169835226100957350/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://ancestryinsider.blogspot.com/2013/05/serendipity-in-carpooling.html#comment-form" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/5512311610334754148/posts/default/1169835226100957350?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/5512311610334754148/posts/default/1169835226100957350?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/AncestryInsider/~3/OCYZpJhmHyg/serendipity-in-carpooling.html" title="Serendipity in Carpooling" /><author><name>The Ancestry Insider</name><uri>http://www.blogger.com/profile/02490682912125335188</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="30" src="http://bp1.blogger.com/_mpUi75C5vC8/SBgCr-W4YOI/AAAAAAAAAXA/K3itFGYLq_4/S220/simpsonized3.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://lh3.ggpht.com/-MqdWoWGukDk/UagN2bZlckI/AAAAAAAAEok/tqaO2USGCZk/s72-c/image%25255B9%25255D.png?imgmax=800" height="72" width="72" /><thr:total>2</thr:total><feedburner:origLink>http://ancestryinsider.blogspot.com/2013/05/serendipity-in-carpooling.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CU4EQXw8cSp7ImA9WhBaGEQ.&quot;"><id>tag:blogger.com,1999:blog-5512311610334754148.post-2078199719851682254</id><published>2013-05-30T00:05:00.000-06:00</published><updated>2013-05-30T00:05:00.279-06:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2013-05-30T00:05:00.279-06:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="records" /><category scheme="http://www.blogger.com/atom/ns#" term="FamilySearch" /><title>FamilySearch World Wide Camera Operations</title><content type="html">&lt;div style="font-size: 85%; float: right; text-align: center; margin: 0px 0px 10px 10px; line-height: 110%"&gt;&lt;img title="" border="0" alt="" src="http://image.familysearch.ldschurch.org/lib/fe6315707166057a711d/m/1/Indexing2A.jpg" /&gt;    &lt;br /&gt;Image Credit: FamilySearch    &lt;br /&gt;© 2013 by Intellectual Reserve, Inc.     &lt;br /&gt;All rights reserved.&lt;/div&gt;  &lt;p&gt;In a 17 May 2013 email to partners, affiliates, bloggers, and members of the press, &lt;a href="http://FamilySearch.org" target="_blank"&gt;FamilySearch&lt;/a&gt; disclosed (or reiterated) information about its world-wide records acquisition efforts.&lt;/p&gt;  &lt;blockquote&gt;   &lt;p&gt;There are more than 1. 5 million images captured each week. Who makes this possible? Records preservation missionaries, contractors, FamilySearch employees, archive employees, and many volunteers are responsible for capturing millions of images each year.&lt;/p&gt;    &lt;p&gt;…&lt;/p&gt; &lt;/blockquote&gt;  &lt;blockquote&gt;   &lt;p&gt;There are about 222 cameras located all over the world; 92 cameras in the Western Hemisphere, and 130 in the Eastern Hemisphere. These industrial cameras can each take millions of images ranging from 16 to 50 megapixels. Computer software is used to calibrate the camera, capture the image, manage the project, and capture metadata or information about the records. Clamps and foam wedges are used to keep the book level and the image in focus. All images are saved on an external hard drive [which] at the end of each week [is] placed in a protective case, and sent to Salt Lake City, Utah. Once the hard drive arrives in Salt Lake, it is sent through an auditing process where rejected images are sent back for rework and approved images are processed and published.&lt;/p&gt; &lt;/blockquote&gt;  &lt;p&gt;At NGS 2013 FamilySearch disclosed that it plans to significantly increase the number of cameras. It plans to do so using record preservation missionaries to operate the cameras. (&lt;a href="https://www.lds.org/topics/service/family-history/records-preservation-digital-image-capture?lang=eng" target="_blank"&gt;Record Preservation missionaries&lt;/a&gt; are members of &lt;a href="http://mormon.org/" target="_blank"&gt;the Church&lt;/a&gt; of &lt;a href="http://jesuschrist.lds.org" target="_blank"&gt;Jesus Christ&lt;/a&gt; of Latter-day Saints, generally retired, who volunteer 18 to 24 months of their time to operate FamilySearch cameras.)&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;br /&gt;&lt;hr /&gt;
&lt;b&gt;Notice:&lt;/b&gt; The opinions expressed herein are those of the Ancestry Insider, not necessarily those of Ancestry.com or FamilySearch. All content is copyrighted by the Ancestry Insider unless designated otherwise. See http://ancestryinsider.blogspot.com for other important legal notices.&lt;/div&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/AncestryInsider?a=01xM9aWFmmI:CQzrh7MZqK0:2nqncYFp4_M"&gt;&lt;img src="http://feeds.feedburner.com/~ff/AncestryInsider?d=2nqncYFp4_M" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/AncestryInsider?a=01xM9aWFmmI:CQzrh7MZqK0:4cEx4HpKnUU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/AncestryInsider?i=01xM9aWFmmI:CQzrh7MZqK0:4cEx4HpKnUU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/AncestryInsider?a=01xM9aWFmmI:CQzrh7MZqK0:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/AncestryInsider?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/AncestryInsider/~4/01xM9aWFmmI" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://ancestryinsider.blogspot.com/feeds/2078199719851682254/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://ancestryinsider.blogspot.com/2013/05/familysearch-world-wide-camera.html#comment-form" title="4 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/5512311610334754148/posts/default/2078199719851682254?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/5512311610334754148/posts/default/2078199719851682254?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/AncestryInsider/~3/01xM9aWFmmI/familysearch-world-wide-camera.html" title="FamilySearch World Wide Camera Operations" /><author><name>The Ancestry Insider</name><uri>http://www.blogger.com/profile/02490682912125335188</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="30" src="http://bp1.blogger.com/_mpUi75C5vC8/SBgCr-W4YOI/AAAAAAAAAXA/K3itFGYLq_4/S220/simpsonized3.jpg" /></author><thr:total>4</thr:total><feedburner:origLink>http://ancestryinsider.blogspot.com/2013/05/familysearch-world-wide-camera.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DUIEQX0-eyp7ImA9WhBaGE0.&quot;"><id>tag:blogger.com,1999:blog-5512311610334754148.post-3523338966772553312</id><published>2013-05-29T00:05:00.000-06:00</published><updated>2013-05-29T00:05:00.353-06:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2013-05-29T00:05:00.353-06:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Ancestry.com" /><title>Providing Feedback to Ancestry.com Product Managers</title><content type="html">&lt;p&gt;&lt;a href="http://commons.wikimedia.org/wiki/File:ModInductivo.jpg" target="_blank"&gt;&lt;img title="Providing Feedback to Ancestry.com" style="border-left-width: 0px; border-right-width: 0px; background-image: none; border-bottom-width: 0px; float: right; padding-top: 0px; padding-left: 0px; display: inline; padding-right: 0px; border-top-width: 0px" border="0" alt="Providing Feedback to Ancestry.com" align="right" src="http://lh6.ggpht.com/-V3naESgYAeQ/UaE2uDk499I/AAAAAAAAEn8/2nyF3GD-g8w/image%25255B3%25255D.png?imgmax=800" width="204" height="170" /&gt;&lt;/a&gt;&lt;a href="http://www.ancestry.com/" target="_blank"&gt;Ancestry.com&lt;/a&gt; has a mechanism allowing you to send feedback to the decision makers of the different features of their products.&lt;/p&gt;  &lt;p&gt;Click “Get Help” in the upper-right corner of the website and search for “Feedback” in the online help. Select “&lt;a href="http://ancestry.custhelp.com/app/answers/detail/a_id/970/kw/feedback" target="_blank"&gt;Providing feedback about Ancestry&lt;/a&gt;.” This will lead you to the &lt;a href="http://community.ancestry.com/feedback.aspx?cat=Other&amp;amp;kurl=http%3a%2f%2fcommunity.ancestry.com%2fDefault.aspx" target="_blank"&gt;Feedback Form&lt;/a&gt; where you can specify website feature and type of feedback, whether bug report, feature suggestion, or success story.&lt;/p&gt;  &lt;p&gt;The &lt;a href="http://blogs.ancestry.com/ancestry/" target="_blank"&gt;Ancestry.com blog&lt;/a&gt; is another good place to leave feedback. When a post is made about a particular website feature, decision makers follow the comments. &lt;/p&gt;  &lt;p&gt;For Family Tree Maker, fill out the form at &lt;a title="http://ancestry.qualtrics.com/SE/?SID=SV_er4cyPjj5BJKIZf" href="http://ancestry.qualtrics.com/SE/?SID=SV_er4cyPjj5BJKIZf"&gt;http://ancestry.qualtrics.com/SE/?SID=SV_er4cyPjj5BJKIZf&lt;/a&gt;.&lt;/p&gt;  &lt;p&gt;For corporate matters, the Ancestry.com corporate website includes &lt;a href="http://corporate.ancestry.com/contact-us/" target="_blank"&gt;contact information&lt;/a&gt; for key departments.&lt;/p&gt;  &lt;p&gt;Don’t try to use any of these contact points to ask for help or other assistance. For that, you still need to &lt;a href="http://c.ancestry.com/Affiliate/Knowledgebase/contact/contact.html" target="_blank"&gt;contact Ancestry.com’s support people&lt;/a&gt; or use the &lt;a href="http://c.ancestry.com/Affiliate/Knowledgebase/contact/contact.html" target="_blank"&gt;online resources&lt;/a&gt; Ancestry.com has posted.&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;br /&gt;&lt;hr /&gt;
&lt;b&gt;Notice:&lt;/b&gt; The opinions expressed herein are those of the Ancestry Insider, not necessarily those of Ancestry.com or FamilySearch. All content is copyrighted by the Ancestry Insider unless designated otherwise. See http://ancestryinsider.blogspot.com for other important legal notices.&lt;/div&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/AncestryInsider?a=bFT02f6BjNU:z2mFFisIqLk:2nqncYFp4_M"&gt;&lt;img src="http://feeds.feedburner.com/~ff/AncestryInsider?d=2nqncYFp4_M" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/AncestryInsider?a=bFT02f6BjNU:z2mFFisIqLk:4cEx4HpKnUU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/AncestryInsider?i=bFT02f6BjNU:z2mFFisIqLk:4cEx4HpKnUU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/AncestryInsider?a=bFT02f6BjNU:z2mFFisIqLk:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/AncestryInsider?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/AncestryInsider/~4/bFT02f6BjNU" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://ancestryinsider.blogspot.com/feeds/3523338966772553312/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://ancestryinsider.blogspot.com/2013/05/providing-feedback-to-ancestrycom.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/5512311610334754148/posts/default/3523338966772553312?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/5512311610334754148/posts/default/3523338966772553312?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/AncestryInsider/~3/bFT02f6BjNU/providing-feedback-to-ancestrycom.html" title="Providing Feedback to Ancestry.com Product Managers" /><author><name>The Ancestry Insider</name><uri>http://www.blogger.com/profile/02490682912125335188</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="30" src="http://bp1.blogger.com/_mpUi75C5vC8/SBgCr-W4YOI/AAAAAAAAAXA/K3itFGYLq_4/S220/simpsonized3.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://lh6.ggpht.com/-V3naESgYAeQ/UaE2uDk499I/AAAAAAAAEn8/2nyF3GD-g8w/s72-c/image%25255B3%25255D.png?imgmax=800" height="72" width="72" /><thr:total>0</thr:total><feedburner:origLink>http://ancestryinsider.blogspot.com/2013/05/providing-feedback-to-ancestrycom.html</feedburner:origLink></entry><entry gd:etag="W/&quot;C0YEQXo-eip7ImA9WhBaF08.&quot;"><id>tag:blogger.com,1999:blog-5512311610334754148.post-4801936274608125559</id><published>2013-05-28T00:05:00.000-06:00</published><updated>2013-05-28T00:05:00.452-06:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2013-05-28T00:05:00.452-06:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Ancestry.com" /><title>WDYTYA Comes to TLC</title><content type="html">&lt;p&gt;   &lt;div style="font-size: 85%; float: right; text-align: center; margin: 0px 0px 10px 10px; line-height: 110%"&gt;&lt;a href="http://www.tlc.com/" target="_blank"&gt;&lt;img title="image" style="border-top: 0px; border-right: 0px; background-image: none; border-bottom: 0px; padding-top: 0px; padding-left: 0px; border-left: 0px; display: inline; padding-right: 0px" border="0" alt="image" src="http://lh3.ggpht.com/-XoT3_UB5R6w/UaEadGMZW2I/AAAAAAAAEnw/PqPf-U5UmoM/image%25255B7%25255D.png?imgmax=800" width="126" height="72" /&gt;&lt;/a&gt;       &lt;br /&gt;Click to go to the TLC website.&lt;/div&gt; The upcoming season of “Who Do You Think You Are?” is moving to cable. It premiers on TLC on 23 July 2013. The &lt;a href="http://www.ancestry.com/" target="_blank"&gt;Ancestry.com&lt;/a&gt; press release reads in part,&lt;/p&gt;  &lt;blockquote&gt;   &lt;p&gt;“Who Do You Think You Are?” explores the roots of celebrities who embark on an intense personal journey to discover their family’s past. Some of the celebrities to be featured in these all-new episodes include Christina Applegate, Cindy Crawford, and Zooey Deschanel. Each of the 8 hour-long episodes reveal the real person behind the celebrity as they come to understand the lives their ancestors lived that helped shape the person they are today.&lt;/p&gt; &lt;/blockquote&gt;  &lt;p&gt;The show was cancelled by NBC after three seasons. In its new home on cable, Ancestry.com will continue to be a major sponsor.&lt;/p&gt;  &lt;p&gt;See &lt;a href="http://corporate.ancestry.com/press/press-releases/2013/05/ancestry.com-and-tlc-team-up-for-new-season-of-who-do-you-think-you-are/" target="_blank"&gt;the complete Ancestry.com press release&lt;/a&gt; on the Ancestry.com corporate website.&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;br /&gt;&lt;hr /&gt;
&lt;b&gt;Notice:&lt;/b&gt; The opinions expressed herein are those of the Ancestry Insider, not necessarily those of Ancestry.com or FamilySearch. All content is copyrighted by the Ancestry Insider unless designated otherwise. See http://ancestryinsider.blogspot.com for other important legal notices.&lt;/div&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/AncestryInsider?a=QTEpAul7tf0:tFcpLQ4qln0:2nqncYFp4_M"&gt;&lt;img src="http://feeds.feedburner.com/~ff/AncestryInsider?d=2nqncYFp4_M" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/AncestryInsider?a=QTEpAul7tf0:tFcpLQ4qln0:4cEx4HpKnUU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/AncestryInsider?i=QTEpAul7tf0:tFcpLQ4qln0:4cEx4HpKnUU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/AncestryInsider?a=QTEpAul7tf0:tFcpLQ4qln0:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/AncestryInsider?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/AncestryInsider/~4/QTEpAul7tf0" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://ancestryinsider.blogspot.com/feeds/4801936274608125559/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://ancestryinsider.blogspot.com/2013/05/wdytya-comes-to-tlc.html#comment-form" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/5512311610334754148/posts/default/4801936274608125559?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/5512311610334754148/posts/default/4801936274608125559?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/AncestryInsider/~3/QTEpAul7tf0/wdytya-comes-to-tlc.html" title="WDYTYA Comes to TLC" /><author><name>The Ancestry Insider</name><uri>http://www.blogger.com/profile/02490682912125335188</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="30" src="http://bp1.blogger.com/_mpUi75C5vC8/SBgCr-W4YOI/AAAAAAAAAXA/K3itFGYLq_4/S220/simpsonized3.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://lh3.ggpht.com/-XoT3_UB5R6w/UaEadGMZW2I/AAAAAAAAEnw/PqPf-U5UmoM/s72-c/image%25255B7%25255D.png?imgmax=800" height="72" width="72" /><thr:total>1</thr:total><feedburner:origLink>http://ancestryinsider.blogspot.com/2013/05/wdytya-comes-to-tlc.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DkAEQXY-fyp7ImA9WhBaFk4.&quot;"><id>tag:blogger.com,1999:blog-5512311610334754148.post-7472061614699417230</id><published>2013-05-27T00:05:00.000-06:00</published><updated>2013-05-27T00:05:00.857-06:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2013-05-27T00:05:00.857-06:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="FamilySearch.org" /><category scheme="http://www.blogger.com/atom/ns#" term="search" /><title>Mailbox Monday: FamilySearch Irrelevant Results</title><content type="html">&lt;p&gt;&lt;img title="The Ancestry Insider&amp;#39;s Monday Mailbox" style="float: right; display: inline" alt="The Ancestry Insider&amp;#39;s Monday Mailbox" align="right" src="http://lh5.ggpht.com/-APPONy4CQu8/USAiyzrNeFI/AAAAAAAAESE/bnD36sCu0V4/Mailbox%252520from%252520W%252520300_thumb%25255B2%25255D.png?imgmax=800" /&gt;I got lots of great responses to the question, “Do you have a fix that you’d like to see on &lt;a href="http://FamilySearch.org" target="_blank"&gt;FamilySearch&lt;/a&gt;.com or &lt;a href="http://www.ancestry.com/" target="_blank"&gt;Ancestry.com&lt;/a&gt;?” (See &lt;a href="http://ancestryinsider.blogspot.com/2013/05/ngs2013-future-of-family.html#comments" target="_blank"&gt;all the responses&lt;/a&gt; at “&lt;a href="http://ancestryinsider.blogspot.com/2013/05/ngs2013-future-of-family.html" target="_blank"&gt;The Future of Family History—According to You!&lt;/a&gt;”) There were several threads of common thought. Here was one of them:&lt;/p&gt;  &lt;p&gt;Dear Ancestry Insider&lt;/p&gt;  &lt;blockquote&gt;   &lt;p&gt;I would really like FamilySearch to stop giving totally irrelevant results, like other countries when I've specified one UK county, census when I've specified christenings. If I wanted these I'd leave that field blank. &lt;/p&gt;    &lt;p&gt;Signed,     &lt;br /&gt;Unknown&lt;/p&gt; &lt;/blockquote&gt;  &lt;p&gt;Dear Ancestry Insider,&lt;/p&gt;  &lt;blockquote&gt;   &lt;p&gt;I agree with Unknown. My comment is in response to your second bullet point, “Return search results in the same century specified.” It should also include “same country and year range specified.”&lt;/p&gt;    &lt;p&gt;Signed,      &lt;br /&gt;Marianne in MD&lt;/p&gt; &lt;/blockquote&gt;  &lt;p&gt;Dear Ancestry Insider,&lt;/p&gt;  &lt;blockquote&gt;   &lt;p&gt;It urks me when I ask specifically to search a certain year, place, and name, and 1,000 different years, places, and names turn up. You can do better than that, FamilySearch!&lt;/p&gt;    &lt;p&gt;Signed,     &lt;br /&gt;Brownie’s Points&lt;/p&gt; &lt;/blockquote&gt;  &lt;p&gt;Dear Unknown, Marianne, and Brownie,&lt;/p&gt;  &lt;p&gt;I understand your consternation. If I search for the birth record of my cousin, Lucy Sider (or Side), who was born in London, England between 1891 and 1893, I get matches in U.S. Censuses and in Ohio marriage records.&lt;/p&gt;  &lt;p&gt;I think you’ll be happy to hear about &lt;a href="http://FamilySearch.org" target="_blank"&gt;FamilySearch&lt;/a&gt;’s “Restrict records by” feature. You can find it (currently) underneath the first and last names boxes:&lt;/p&gt;  &lt;p&gt;&lt;a href="https://familysearch.org/search" target="_blank"&gt;&lt;img title="Options to restrict records by location, type, and batch numbers on FamilySearch" style="border-top: 0px; border-right: 0px; background-image: none; border-bottom: 0px; padding-top: 0px; padding-left: 0px; border-left: 0px; display: inline; padding-right: 0px" border="0" alt="Options to restrict records by location, type, and batch numbers on FamilySearch" src="http://lh4.ggpht.com/-NRBRzQ-XXi4/UaETUAVWyzI/AAAAAAAAEnk/NzNHH68N3eE/image%25255B13%25255D.png?imgmax=800" width="504" height="362" /&gt;&lt;/a&gt;&lt;/p&gt;  &lt;p&gt;There are three options: “Location | Type | Batch Number.” If the country box is not visible, click “Location.” If the record type options are not visible, click “Type.”&lt;/p&gt;    &lt;p&gt;Enter “England” in the country box and you will receive matches restricted to records created in England or created about primary events in England. (If a birth record documents a birth in England, it doesn’t matter where the record was created.) In the case of my cousin Lucy, restricting the country to England cuts the matches down to four English census records.&lt;/p&gt;  &lt;p&gt;For the United States, England, Canada, and Australia, you can restrict the location further. When you enter the country, &lt;a href="http://FamilySearch.org" target="_blank"&gt;FamilySearch&lt;/a&gt; provides a dropdown list from which you can select state, province, or English county. In the case of Lucy, restricting the location to London, England restricts the matches down to two census records.&lt;/p&gt;  &lt;p&gt;The second restrict by option is record type. Where I was looking for Lucy’s birth record, I might have restricted the record type to “Birth, Baptism, and Christenings” and quickly learned that FamilySearch had no matching birth records.&lt;/p&gt;  &lt;p&gt;As to restricting to a particular date range, I don’t know of any way to do that. Matching terms exactly does not work. However, FamilySearch.org does list the matching records first.&lt;/p&gt;  &lt;p&gt;If anyone knows how to restrict to a particular date range, chime in.&lt;/p&gt;  &lt;p&gt;Signed,   &lt;br /&gt;&lt;a href="http://ancestryinsider.blogspot.com"&gt;The Ancestry Insider&lt;/a&gt;&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;br /&gt;&lt;hr /&gt;
&lt;b&gt;Notice:&lt;/b&gt; The opinions expressed herein are those of the Ancestry Insider, not necessarily those of Ancestry.com or FamilySearch. All content is copyrighted by the Ancestry Insider unless designated otherwise. See http://ancestryinsider.blogspot.com for other important legal notices.&lt;/div&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/AncestryInsider?a=QGKVsS8aRZc:VmHXPI1CWRM:2nqncYFp4_M"&gt;&lt;img src="http://feeds.feedburner.com/~ff/AncestryInsider?d=2nqncYFp4_M" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/AncestryInsider?a=QGKVsS8aRZc:VmHXPI1CWRM:4cEx4HpKnUU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/AncestryInsider?i=QGKVsS8aRZc:VmHXPI1CWRM:4cEx4HpKnUU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/AncestryInsider?a=QGKVsS8aRZc:VmHXPI1CWRM:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/AncestryInsider?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/AncestryInsider/~4/QGKVsS8aRZc" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://ancestryinsider.blogspot.com/feeds/7472061614699417230/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://ancestryinsider.blogspot.com/2013/05/mailbox-monday-familysearch-irrelevant.html#comment-form" title="3 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/5512311610334754148/posts/default/7472061614699417230?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/5512311610334754148/posts/default/7472061614699417230?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/AncestryInsider/~3/QGKVsS8aRZc/mailbox-monday-familysearch-irrelevant.html" title="Mailbox Monday: FamilySearch Irrelevant Results" /><author><name>The Ancestry Insider</name><uri>http://www.blogger.com/profile/02490682912125335188</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="30" src="http://bp1.blogger.com/_mpUi75C5vC8/SBgCr-W4YOI/AAAAAAAAAXA/K3itFGYLq_4/S220/simpsonized3.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://lh5.ggpht.com/-APPONy4CQu8/USAiyzrNeFI/AAAAAAAAESE/bnD36sCu0V4/s72-c/Mailbox%252520from%252520W%252520300_thumb%25255B2%25255D.png?imgmax=800" height="72" width="72" /><thr:total>3</thr:total><feedburner:origLink>http://ancestryinsider.blogspot.com/2013/05/mailbox-monday-familysearch-irrelevant.html</feedburner:origLink></entry><entry gd:etag="W/&quot;A0YEQX88cSp7ImA9WhBaEkU.&quot;"><id>tag:blogger.com,1999:blog-5512311610334754148.post-6369895733439491481</id><published>2013-05-23T00:05:00.000-06:00</published><updated>2013-05-23T00:05:00.179-06:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2013-05-23T00:05:00.179-06:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Ancestry.com" /><category scheme="http://www.blogger.com/atom/ns#" term="FamilySearch" /><category scheme="http://www.blogger.com/atom/ns#" term="conferences" /><title>#NGS2013 – The Future of Family History—According to You!</title><content type="html"> &lt;div style="float: right; text-align: center; margin: 0px 0px 10px 10px; line-height: 110%"&gt;&lt;a href="http://commons.wikimedia.org/wiki/File:Birthday-wish.jpg" target="_blank"&gt;&lt;img title="What fix or feature do you wish Ancestry.com or FamilySearch would provide?" alt="What fix or feature do you wish Ancestry.com or FamilySearch would provide?" src="http://upload.wikimedia.org/wikipedia/commons/thumb/7/78/Birthday-wish.jpg/800px-Birthday-wish.jpg" width="300" height="226"&gt;&lt;/a&gt;&lt;br&gt;What fix or feature do you wish &lt;br&gt;Ancestry.com or FamilySearch &lt;br&gt;would provide?&lt;/div&gt;At the 2013 annual conference of the &lt;a href="http://www.ngsgenealogy.org" target="_blank"&gt;National Genealogical Society&lt;/a&gt;, some guy did a luncheon presentation titled, “The Future of Family History—According to You!” As part of the presentation he asked audience members, “If you could see &lt;a href="http://www.ancestry.com/" target="_blank"&gt;Ancestry.com&lt;/a&gt; or &lt;a href="https://www.familysearch.org/about" target="_blank"&gt;FamilySearch&lt;/a&gt; fix just one thing during the next year, what would it be?” Hopefully representatives of both organizations were present taking notes. But just in case, I offer these brief notes taken by a kind attendee.  &lt;ul&gt; &lt;li&gt;Stability—keep the website the same; don’t keep changing it.&lt;u&gt;&lt;/u&gt;&lt;u&gt;&lt;/u&gt;  &lt;li&gt;Return search results in the same century specified.&lt;u&gt;&lt;/u&gt;&lt;u&gt;&lt;/u&gt;  &lt;li&gt;Bring back Old Search on the Ancestry.com Library Edition.&lt;u&gt;&lt;/u&gt;&lt;u&gt;&lt;/u&gt;  &lt;li&gt;NEVER get rid of old search.&lt;u&gt;&lt;/u&gt;&lt;u&gt;&lt;/u&gt;  &lt;li&gt;I’d like to be able to download search results.&lt;u&gt;&lt;/u&gt;&lt;u&gt;&lt;/u&gt;  &lt;li&gt;Fix others’ bad trees.&lt;u&gt;&lt;/u&gt;&lt;u&gt;&lt;/u&gt;  &lt;li&gt;Fix automatic-logout.  &lt;li&gt;The ability to split a tree on Ancestry&lt;u&gt;&lt;/u&gt;&lt;u&gt;&lt;/u&gt;  &lt;li&gt;Exact search: It would be nice if it was.&lt;u&gt;&lt;/u&gt;&lt;u&gt;&lt;/u&gt;  &lt;li&gt;Put a big red X on bad trees&lt;u&gt;&lt;/u&gt;&lt;u&gt;&lt;/u&gt;  &lt;li&gt;Computer won’t upload a tree until you’ve documented it.&lt;u&gt;&lt;/u&gt;&lt;u&gt;&lt;/u&gt;  &lt;li&gt;On Ancestry.com it would be nice to be able to go back to where you were after you’ve followed a set of links.&lt;u&gt;&lt;/u&gt;&lt;u&gt;&lt;/u&gt;  &lt;li&gt;For Old Search: visual indications that you’ve already looked at certain lists or parts of it&lt;u&gt;&lt;/u&gt;&lt;u&gt;&lt;/u&gt;  &lt;li&gt;Ancestry—record only once&lt;u&gt;&lt;/u&gt;&lt;u&gt;&lt;/u&gt;  &lt;li&gt;Shakey leaves: documentation problems, temporary tree&lt;u&gt;&lt;/u&gt;&lt;u&gt;&lt;/u&gt;  &lt;li&gt;FamilySearch: get to the catalog with one-click&lt;u&gt;&lt;/u&gt;&lt;u&gt;&lt;/u&gt;&lt;/li&gt;&lt;/ul&gt; &lt;p&gt;We also did more long-term wish list. Here are just a few of those:&lt;u&gt;&lt;/u&gt;&lt;u&gt;&lt;/u&gt;&lt;/p&gt; &lt;ul&gt; &lt;li&gt;Map pop-up with surrounding counties&lt;u&gt;&lt;/u&gt;&lt;u&gt;&lt;/u&gt;  &lt;li&gt;Ancestry.com do a Family Tree—Wikipedia model&lt;u&gt;&lt;/u&gt;&lt;u&gt;&lt;/u&gt;  &lt;li&gt;Tag cloud of FamilySearch Pod  &lt;li&gt;Map s as existed at time of event&lt;u&gt;&lt;/u&gt;&lt;u&gt;&lt;/u&gt;  &lt;li&gt;Citations written out the way they should be—in the various programs  &lt;li&gt;Film numbers and lists of all family history centers and libraries where they are at&lt;/li&gt;&lt;/ul&gt; &lt;p&gt;There was lots more. It was impossible to capture it all.&lt;/p&gt; &lt;p&gt;What about you? Do you have a fix you’d like to see in the next year or a feature you’d like to see in the next five? Leave a comment at &lt;a href="http://AncestryInsider.blogspot.com"&gt;http://AncestryInsider.blogspot.com&lt;/a&gt;. &lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;br /&gt;&lt;hr /&gt;
&lt;b&gt;Notice:&lt;/b&gt; The opinions expressed herein are those of the Ancestry Insider, not necessarily those of Ancestry.com or FamilySearch. All content is copyrighted by the Ancestry Insider unless designated otherwise. See http://ancestryinsider.blogspot.com for other important legal notices.&lt;/div&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/AncestryInsider?a=j0-QasiO7aE:Bjx8x-c1Ueo:2nqncYFp4_M"&gt;&lt;img src="http://feeds.feedburner.com/~ff/AncestryInsider?d=2nqncYFp4_M" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/AncestryInsider?a=j0-QasiO7aE:Bjx8x-c1Ueo:4cEx4HpKnUU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/AncestryInsider?i=j0-QasiO7aE:Bjx8x-c1Ueo:4cEx4HpKnUU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/AncestryInsider?a=j0-QasiO7aE:Bjx8x-c1Ueo:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/AncestryInsider?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/AncestryInsider/~4/j0-QasiO7aE" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://ancestryinsider.blogspot.com/feeds/6369895733439491481/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://ancestryinsider.blogspot.com/2013/05/ngs2013-future-of-family.html#comment-form" title="27 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/5512311610334754148/posts/default/6369895733439491481?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/5512311610334754148/posts/default/6369895733439491481?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/AncestryInsider/~3/j0-QasiO7aE/ngs2013-future-of-family.html" title="#NGS2013 – The Future of Family History—According to You!" /><author><name>The Ancestry Insider</name><uri>http://www.blogger.com/profile/02490682912125335188</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="30" src="http://bp1.blogger.com/_mpUi75C5vC8/SBgCr-W4YOI/AAAAAAAAAXA/K3itFGYLq_4/S220/simpsonized3.jpg" /></author><thr:total>27</thr:total><feedburner:origLink>http://ancestryinsider.blogspot.com/2013/05/ngs2013-future-of-family.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CEAEQX85cSp7ImA9WhBaEk0.&quot;"><id>tag:blogger.com,1999:blog-5512311610334754148.post-8638984543565243847</id><published>2013-05-22T00:05:00.000-06:00</published><updated>2013-05-22T00:05:00.129-06:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2013-05-22T00:05:00.129-06:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Ancestry.com" /><category scheme="http://www.blogger.com/atom/ns#" term="conferences" /><title>#NGS2013 – TRON, Mr. Spock, and Willie Wonka</title><content type="html">&lt;p&gt;&lt;a href="http://commons.wikimedia.org/wiki/File:Photographer1850s.png" target="_blank"&gt;&lt;img title="The easiest equipment for digitizing documents is a digital camera" style="border-top: 0px; border-right: 0px; background-image: none; border-bottom: 0px; float: right; padding-top: 0px; padding-left: 0px; border-left: 0px; display: inline; padding-right: 0px" border="0" alt="The easiest equipment for digitizing documents is a digital camera" align="right" src="http://lh6.ggpht.com/-gXG7Yir1ov4/UZieK5S2dzI/AAAAAAAAEnQ/l2Eghf9bkmk/image%25255B3%25255D.png?imgmax=800" width="183" height="204"&gt;&lt;/a&gt;I don’t seem to be able to take notes at conference luncheons. That was certainly the case at the luncheon presented by Ancestry.com’s Sabrina Petersen at the 2013 annual conference of the &lt;a href="http://www.ngsgenealogy.org" target="_blank"&gt;National Genealogical Society&lt;/a&gt;. She titled her presentation “TRON, Mr. Spock, and Willie Wonka: If They Can Digitize So Can You.” Petersen is director of global imaging for &lt;a href="http://www.ancestry.com/" target="_blank"&gt;Ancestry.com&lt;/a&gt;. Unlike TRON, Mr. Spock, and Willie Wonka, we won’t be digitizing and transporting people anytime soon, but we can digitize photographs and documents.&lt;/p&gt; &lt;p&gt;Petersen presented some great suggestions, and in the absence of notes she was kind enough to send me some:&lt;/p&gt; &lt;div&gt; &lt;blockquote&gt; &lt;p&gt;1. Think like an Archive.&lt;/p&gt; &lt;p&gt;Archives think about how to preserve records and photographs for their patrons and posterity within a budget.&amp;nbsp; For the most important and their most used copies they make digital surrogates, and put the record in a secure location so that it doesn’t have to be handled all the time, and store it in a dark safe place.&amp;nbsp; Digitization allows for multiple copies of the original that can be shared as well as stored.&lt;/p&gt; &lt;p&gt;2. Think about how you are going to find a particular picture/document in the future.&lt;/p&gt; &lt;p&gt;Putting metadata within the name of the image itself is the easiest way to find it in the future.&amp;nbsp; You might put “Aunt Nancy Family Reunion 1982 picnic” as the name of the picture.&amp;nbsp; Or “Death Certificate Benjamin Franklin Blansett 1912”.&amp;nbsp; By making the name the basic information you can then easily search and find it again.&amp;nbsp; Then you can further organize the files by putting them in folder by event, family surname or by type of record.&amp;nbsp; All of these will help make the retrieval of this easier in the future.&lt;/p&gt; &lt;p&gt;3. Digitize your records.&amp;nbsp; &lt;/p&gt; &lt;p&gt;This can be done by using a whole slew of different types of equipment, but probably the easiest is a digital camera for most documents, besides which cameras are easy to carry with you when you are visiting relatives, or maybe even at an archive.&amp;nbsp; Make sure you capture the document or picture as straight as possible when you take the picture.&amp;nbsp; While it might be easy to straighten a photo after you take it, it will produce some digital artifacts that are not yet visible.&amp;nbsp; If you copy these files many times, depending on the format, these artifacts become more apparent to the naked eye.&amp;nbsp; The easiest way to help avoid these is simply take a straight picture to begin with.&lt;/p&gt; &lt;p&gt;4. Which brings us to formats to save your images.&amp;nbsp; &lt;/p&gt; &lt;p&gt;There are a lot of formats to choose from.&amp;nbsp; JPEG and TIFF are the most common.&amp;nbsp; Whichever you choose, make sure that you have the original copy someplace safe and then make a second copy which is the one you play with, send to others, or upload for safe keeping to your family tree on Ancestry.&amp;nbsp; This second copy can be any file format you choose, including a PDF.&amp;nbsp; This makes it easy to share, easy to send, and easy to upload.&lt;/p&gt; &lt;p&gt;5. Lastly remember that anything you do now is better than nothing.&lt;/p&gt;&lt;/blockquote&gt; &lt;p&gt;Thanks, Sabrina. Now everyone. Get out there and get digitizing.&lt;/p&gt;&lt;/div&gt;  &lt;div class="blogger-post-footer"&gt;&lt;br /&gt;&lt;hr /&gt;
&lt;b&gt;Notice:&lt;/b&gt; The opinions expressed herein are those of the Ancestry Insider, not necessarily those of Ancestry.com or FamilySearch. All content is copyrighted by the Ancestry Insider unless designated otherwise. See http://ancestryinsider.blogspot.com for other important legal notices.&lt;/div&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/AncestryInsider?a=K-lH95mgmVo:S1t_FHxNi6k:2nqncYFp4_M"&gt;&lt;img src="http://feeds.feedburner.com/~ff/AncestryInsider?d=2nqncYFp4_M" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/AncestryInsider?a=K-lH95mgmVo:S1t_FHxNi6k:4cEx4HpKnUU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/AncestryInsider?i=K-lH95mgmVo:S1t_FHxNi6k:4cEx4HpKnUU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/AncestryInsider?a=K-lH95mgmVo:S1t_FHxNi6k:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/AncestryInsider?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/AncestryInsider/~4/K-lH95mgmVo" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://ancestryinsider.blogspot.com/feeds/8638984543565243847/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://ancestryinsider.blogspot.com/2013/05/ngs2013-tron-mr-spock-and-willie-wonka.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/5512311610334754148/posts/default/8638984543565243847?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/5512311610334754148/posts/default/8638984543565243847?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/AncestryInsider/~3/K-lH95mgmVo/ngs2013-tron-mr-spock-and-willie-wonka.html" title="#NGS2013 – TRON, Mr. Spock, and Willie Wonka" /><author><name>The Ancestry Insider</name><uri>http://www.blogger.com/profile/02490682912125335188</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="30" src="http://bp1.blogger.com/_mpUi75C5vC8/SBgCr-W4YOI/AAAAAAAAAXA/K3itFGYLq_4/S220/simpsonized3.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://lh6.ggpht.com/-gXG7Yir1ov4/UZieK5S2dzI/AAAAAAAAEnQ/l2Eghf9bkmk/s72-c/image%25255B3%25255D.png?imgmax=800" height="72" width="72" /><thr:total>0</thr:total><feedburner:origLink>http://ancestryinsider.blogspot.com/2013/05/ngs2013-tron-mr-spock-and-willie-wonka.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DEQEQXg5cSp7ImA9WhBaEUw.&quot;"><id>tag:blogger.com,1999:blog-5512311610334754148.post-1738243680864903101</id><published>2013-05-21T00:05:00.000-06:00</published><updated>2013-05-21T00:05:00.629-06:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2013-05-21T00:05:00.629-06:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Ancestry.com" /><category scheme="http://www.blogger.com/atom/ns#" term="conferences" /><title>#NGS2013 - Ancestry.com’s Mobile App</title><content type="html"> &lt;div style="font-size: 85%; float: right; text-align: center; margin: 0px 0px 10px 10px; line-height: 110%"&gt;&lt;img title="The Ancestry Insider listening to Aaron Orr" style="border-top: 0px; border-right: 0px; background-image: none; border-bottom: 0px; padding-top: 0px; padding-left: 0px; border-left: 0px; display: inline; padding-right: 0px" border="0" alt="The Ancestry Insider listening to Aaron Orr" src="http://lh4.ggpht.com/-lTShLcw8aCk/UZMJwdGvM9I/AAAAAAAAEmc/qMhrrkJjmrM/image%25255B32%25255D.png?imgmax=800" width="304" height="171"&gt;&lt;br&gt;&lt;i&gt;(C) 2013 by the National Genealogical Society, Inc. &lt;br&gt;Used by permission of the National Genealogical &lt;br&gt;Society and the photographer, Scott Stewart. &lt;br&gt;Scott inadvertently caught me listening to Aaron. &lt;br&gt;Can you tell which one is me?&lt;/i&gt;&lt;/div&gt;&lt;a href="http://www.ancestry.com/" target="_blank"&gt;Ancestry.com&lt;/a&gt; didn’t have any presenters do regular sessions at the 2013 annual conference of the &lt;a href="http://www.ngsgenealogy.org" target="_blank"&gt;National Genealogical Society&lt;/a&gt;, so I had a challenge writing about Ancestry.com. I would have attended their “Ancestry Day” sessions Saturday, but I was too wound up in my own presentations. As an alternative, I attended a couple of their in-booth presentations.  &lt;p&gt;Aaron Orr is the product manager for Ancestry.com’s mobile product. It is available for both iOS and Android although the Android app lags the iOS version a little bit.&lt;/p&gt; &lt;p&gt;The Ancestry app is free and easy to use. Login using your Ancestry.com account. Or simply start entering your tree.&lt;/p&gt; &lt;p&gt;You can see all your trees on your device. Download a tree to your app and as long as you don’t log out, it will stay on the device. If you want to make changes, you must be connected. As you make changes either on the web or on the app, changes are reflected on the other.&lt;/p&gt; &lt;p&gt;You can choose either a pedigree view or a tree view.&lt;/p&gt; &lt;p&gt;&lt;img title="Ancestry app Pedigree View" style="border-left-width: 0px; border-right-width: 0px; background-image: none; border-bottom-width: 0px; padding-top: 0px; padding-left: 0px; display: inline; padding-right: 0px; border-top-width: 0px" border="0" alt="Ancestry app Pedigree View" src="http://lh6.ggpht.com/-VCLpWdqDLLc/UZMJxW-NBFI/AAAAAAAAEmk/ALygi-wd1oE/2013-05-14%25252019.13.35%252520Pedigree%252520View%25255B4%25255D.png?imgmax=800" width="304" height="229"&gt;&amp;nbsp; &lt;img title="Ancestry app Tree View" style="border-left-width: 0px; border-right-width: 0px; background-image: none; border-bottom-width: 0px; padding-top: 0px; padding-left: 0px; display: inline; padding-right: 0px; border-top-width: 0px" border="0" alt="Ancestry app Tree View" src="http://lh6.ggpht.com/-Ybcue3i3BNI/UZMJyp04xMI/AAAAAAAAEms/xzyN2NG57do/2013-05-14%25252019.15.22%252520Tree%252520view%25255B4%25255D.png?imgmax=800" width="304" height="229"&gt;&lt;/p&gt; &lt;p&gt;Click on a person or swipe the right edge of the screen to view details about a person. Along the bottom you can select three tabs: info, family, and gallery. &lt;/p&gt; &lt;p&gt;&lt;img title="The bottom of the person flyout" style="border-left-width: 0px; border-right-width: 0px; background-image: none; border-bottom-width: 0px; padding-top: 0px; padding-left: 0px; display: inline; padding-right: 0px; border-top-width: 0px" border="0" alt="The bottom of the person flyout" src="http://lh6.ggpht.com/-_N5XlHsRPSc/UZMJzgj8JsI/AAAAAAAAEm0/69aqlWVRDl8/image%25255B21%25255D.png?imgmax=800" width="304" height="224"&gt;&lt;/p&gt; &lt;p&gt;On the Info tab you can see life events and add more. You can view hints. You can view the person’s relationship to yourself. You can add notes here. “Notes are super great while out in a library or archive,” said Orr.&lt;/p&gt; &lt;p&gt;On the Family tab you can see family members: parents, spouse, children, and siblings. You can add new ones.&lt;/p&gt; &lt;p&gt;On the Gallery tab you can see photos, attached Ancestry.com records, and sources. You can add more photos.&lt;/p&gt; &lt;p&gt;The top left corner of the screen has a list button that lists all the people in your tree. Or filter the list to just direct ancestors, end-of-line people, living relatives, people with hints, or people with recent hints. Or search by name.&lt;/p&gt; &lt;p&gt;&lt;img title="The top left of the Ancestry app" style="border-left-width: 0px; border-right-width: 0px; background-image: none; border-bottom-width: 0px; padding-top: 0px; padding-left: 0px; display: inline; padding-right: 0px; border-top-width: 0px" border="0" alt="The top left of the Ancestry app" src="http://lh3.ggpht.com/-__3oEoxHl5M/UZMJ14r4RHI/AAAAAAAAEm8/slr_Cg5f19A/image%25255B20%25255D.png?imgmax=800" width="500" height="145"&gt;&lt;/p&gt; &lt;p&gt;The center button at the top lists your user trees. It shows which ones have been downloaded. You can change the tree settings from there.&lt;/p&gt; &lt;p&gt;While difficult to see, some person cards have a shadow. (All of the persons in the illustration above have one.) Click the person to reveal more of that person’s tree.&lt;/p&gt; &lt;p&gt;There are two types of hints: photos (iOS only) and records (shakey leaves). There was a way to share but I can’t remember how. You can share via Facebook, Twitter, or email. It sends a cool email that contains the image and context about the person. It looked pretty cool but I could not find how to do it. Why don’t iPad apps have help files? I tried to search help on Ancestry.com,&amp;nbsp; but Advanced Search had never heard of the Ancestry app. Frustrating.&lt;/p&gt; &lt;p&gt;I only experienced one other hiccup while I prepared this article. One time I clicked the screen and it went all scrambled. After about 5 seconds I was suddenly back on the iOS desktop. I restarted the Ancestry app and found myself on some random person. Hopefully nothing was lost in the episode.&lt;/p&gt; &lt;p&gt;Because Family Tree Maker can synchronize with Ancestry.com public member trees, and because the Ancestry App can synchronize with Ancestry.com public member trees, it is possible to synchronize your tree across all your devices and environments.&lt;/p&gt; &lt;p&gt;Thanks, Aaron, for the demo.&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;br /&gt;&lt;hr /&gt;
&lt;b&gt;Notice:&lt;/b&gt; The opinions expressed herein are those of the Ancestry Insider, not necessarily those of Ancestry.com or FamilySearch. All content is copyrighted by the Ancestry Insider unless designated otherwise. See http://ancestryinsider.blogspot.com for other important legal notices.&lt;/div&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/AncestryInsider?a=H6STT7BcCj0:pA1La5kuFOU:2nqncYFp4_M"&gt;&lt;img src="http://feeds.feedburner.com/~ff/AncestryInsider?d=2nqncYFp4_M" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/AncestryInsider?a=H6STT7BcCj0:pA1La5kuFOU:4cEx4HpKnUU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/AncestryInsider?i=H6STT7BcCj0:pA1La5kuFOU:4cEx4HpKnUU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/AncestryInsider?a=H6STT7BcCj0:pA1La5kuFOU:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/AncestryInsider?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/AncestryInsider/~4/H6STT7BcCj0" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://ancestryinsider.blogspot.com/feeds/1738243680864903101/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://ancestryinsider.blogspot.com/2013/05/ngs2013-ancestrycoms-mobile-app.html#comment-form" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/5512311610334754148/posts/default/1738243680864903101?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/5512311610334754148/posts/default/1738243680864903101?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/AncestryInsider/~3/H6STT7BcCj0/ngs2013-ancestrycoms-mobile-app.html" title="#NGS2013 - Ancestry.com’s Mobile App" /><author><name>The Ancestry Insider</name><uri>http://www.blogger.com/profile/02490682912125335188</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="30" src="http://bp1.blogger.com/_mpUi75C5vC8/SBgCr-W4YOI/AAAAAAAAAXA/K3itFGYLq_4/S220/simpsonized3.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://lh4.ggpht.com/-lTShLcw8aCk/UZMJwdGvM9I/AAAAAAAAEmc/qMhrrkJjmrM/s72-c/image%25255B32%25255D.png?imgmax=800" height="72" width="72" /><thr:total>1</thr:total><feedburner:origLink>http://ancestryinsider.blogspot.com/2013/05/ngs2013-ancestrycoms-mobile-app.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CE8NSH04eSp7ImA9WhBbGEw.&quot;"><id>tag:blogger.com,1999:blog-5512311610334754148.post-8026083482368612135</id><published>2013-05-17T00:05:00.000-06:00</published><updated>2013-05-17T11:48:19.331-06:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2013-05-17T11:48:19.331-06:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="FamilySearch.org" /><category scheme="http://www.blogger.com/atom/ns#" term="conferences" /><title>#NGS2013 – Futures for FamilySearch Family Tree</title><content type="html">&lt;p&gt;&lt;img title="Ron Tanner of FamilySearch" style="float: right; display: inline" alt="Ron Tanner of FamilySearch" align="right" src="http://lh4.ggpht.com/-k0t3UzZuk7Q/UQQrEecKNdI/AAAAAAAAEJ0/670gstmJpvs/image%25255B3%25255D.png?imgmax=800"&gt;Whenever possible, I attend sessions presented by product managers so I can report on the future plans that they often reveal. (Too bad &lt;a href="http://www.ancestry.com/" target="_blank"&gt;Ancestry.com&lt;/a&gt; product managers rarely present such sessions.) In this regard Ron Tanner’s presentation at the 2013 annual conference of the &lt;a href="http://www.ngsgenealogy.org" target="_blank"&gt;National Genealogical Society&lt;/a&gt; did not disappoint. &lt;/p&gt; &lt;p&gt;For the most part, he didn’t give too much guidance on when these features might be seen. “Sooner or later, or later than that,” he said. &lt;/p&gt; &lt;p&gt;Family Tree will soon have printable family group sheets and pedigree charts. When? The release is being held up by translation into 10 languages. Product managers are considering not waiting, releasing English sooner.&lt;/p&gt; &lt;p&gt;In a few weeks or so they’ll add the ability to take any photograph and make a source out of it.&lt;/p&gt; &lt;p&gt;Family Tree is currently in a transition phase with synchronization occurring between Family Tree and NFS. “Today, if a combine is not allowed in NFS, then we are not allowing a merge in Family Tree,” said Tanner. “Once we can separate the two, then you’ll be able to do the merge.”&lt;/p&gt; &lt;p&gt;Family Tree will soon support notes on ancestors and the notes over in NFS will be copied over. The notes will support up to 10,000 characters, allowing long proof statements.&lt;/p&gt; &lt;p&gt;FamilySearch is going to bring over all your sources from NFS. Tanner later said something I partially missed, so I’m not certain I understood it correctly. I thought he said FamilySearch is going to send a survey to those with sources in NFS asking if they want their sources migrated. If they so indicate, the sources will be placed in their source box.&lt;/p&gt; &lt;p&gt;Family Tree doesn’t support attaching sources or reasons to living persons. They are not yet full-fledged citizens of Family Tree, residing exclusively in NFS. Consequently, these new features of Family Tree will not be supported for living persons until they are fully implemented.&lt;/p&gt; &lt;p&gt;Tanner wants to add quality indicators to Family Tree. These would flag basic pedigree errors like&lt;/p&gt; &lt;ul&gt; &lt;li&gt;birth after death  &lt;li&gt;death after burial  &lt;li&gt;person died young and has spouse  &lt;li&gt;birth before mother/father birth  &lt;li&gt;birth before mother/father was 12  &lt;li&gt;birth after mother died  &lt;li&gt;death before marriage date  &lt;li&gt;marriage date before person is 12&lt;/li&gt;&lt;/ul&gt; &lt;p&gt;FamilySearch will match records in historical record collections to ancestors in the tree.&lt;/p&gt; &lt;p&gt;They are going to add a report abuse button that allows you to report someone who keeps reverting changes and won’t read notes and won’t discuss. “If they won’t cooperate we will delete their account.”&lt;/p&gt; &lt;p&gt;They are working on the watch notification timing. They may allow change notification to occur in as little as 5 minutes.&lt;/p&gt; &lt;p&gt;They are adding Helper capability to Family Tree. It allows someone to sign in as someone else—with their permission—without that other person disclosing their password.&lt;/p&gt; &lt;p&gt;He is thinking about implementing toggle war detection. If a value gets changed back and forth too many times the system would automatically lock it for some time, say two weeks. It would tell the combatants to let their emotions cool down and to enter into a discussion as to what is the right value.&lt;/p&gt; &lt;p&gt;He is thinking about implementing an “Is Accurate” designation that could be applied to an ancestor once he was largely complete and unanimously regarded as accurate. The designation would make it harder to change information about that ancestor.&lt;/p&gt; &lt;p&gt;FamilySearch is working on a way to help attach census records to an entire family and minimize the amount of work required.&lt;/p&gt; &lt;p&gt;They are also discussing what to do to support DNA results.&lt;/p&gt; &lt;p&gt;Not every Family Tree user has chosen to make their email address visible. Tanner would like an internal messaging system built so people can send messages to them and everyone else.&lt;/p&gt; &lt;p&gt;I look forward to seeing these features, no matter how many months or years it takes. Thanks, Ron.&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;br /&gt;&lt;hr /&gt;
&lt;b&gt;Notice:&lt;/b&gt; The opinions expressed herein are those of the Ancestry Insider, not necessarily those of Ancestry.com or FamilySearch. All content is copyrighted by the Ancestry Insider unless designated otherwise. See http://ancestryinsider.blogspot.com for other important legal notices.&lt;/div&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/AncestryInsider?a=kZv3LyrQS2M:EGaFoh8SePg:2nqncYFp4_M"&gt;&lt;img src="http://feeds.feedburner.com/~ff/AncestryInsider?d=2nqncYFp4_M" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/AncestryInsider?a=kZv3LyrQS2M:EGaFoh8SePg:4cEx4HpKnUU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/AncestryInsider?i=kZv3LyrQS2M:EGaFoh8SePg:4cEx4HpKnUU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/AncestryInsider?a=kZv3LyrQS2M:EGaFoh8SePg:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/AncestryInsider?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/AncestryInsider/~4/kZv3LyrQS2M" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://ancestryinsider.blogspot.com/feeds/8026083482368612135/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://ancestryinsider.blogspot.com/2013/05/ngs2013-futures-for-familysearch-family.html#comment-form" title="7 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/5512311610334754148/posts/default/8026083482368612135?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/5512311610334754148/posts/default/8026083482368612135?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/AncestryInsider/~3/kZv3LyrQS2M/ngs2013-futures-for-familysearch-family.html" title="#NGS2013 – Futures for FamilySearch Family Tree" /><author><name>The Ancestry Insider</name><uri>http://www.blogger.com/profile/02490682912125335188</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="30" src="http://bp1.blogger.com/_mpUi75C5vC8/SBgCr-W4YOI/AAAAAAAAAXA/K3itFGYLq_4/S220/simpsonized3.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://lh4.ggpht.com/-k0t3UzZuk7Q/UQQrEecKNdI/AAAAAAAAEJ0/670gstmJpvs/s72-c/image%25255B3%25255D.png?imgmax=800" height="72" width="72" /><thr:total>7</thr:total><feedburner:origLink>http://ancestryinsider.blogspot.com/2013/05/ngs2013-futures-for-familysearch-family.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DkQEQXc6fyp7ImA9WhBbFkU.&quot;"><id>tag:blogger.com,1999:blog-5512311610334754148.post-6525424217584884057</id><published>2013-05-16T00:05:00.000-06:00</published><updated>2013-05-16T00:05:00.917-06:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2013-05-16T00:05:00.917-06:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="FamilySearch.org" /><category scheme="http://www.blogger.com/atom/ns#" term="conferences" /><title>#NGS2013 – FamilySearch Family Tree, An Item or Two</title><content type="html">&lt;p&gt;&lt;img title="Ron Tanner of FamilySearch" style="float: right; display: inline" alt="Ron Tanner of FamilySearch" align="right" src="http://lh4.ggpht.com/-k0t3UzZuk7Q/UQQrEecKNdI/AAAAAAAAEJ0/670gstmJpvs/image%25255B3%25255D.png?imgmax=800"&gt;A lot of expert, accredited, certified genealogists present at the annual conference of the &lt;a href="http://www.ngsgenealogy.org" target="_blank"&gt;National Genealogical Society&lt;/a&gt;. I learn a lot. &lt;/p&gt; &lt;p&gt;Not to be left out of the initialism crowd, Ron Tanner, product manager at &lt;a href="https://www.familysearch.org/about" target="_blank"&gt;FamilySearch&lt;/a&gt;, added some of his own. He is “Ron Tanner, POFT, OAG, F4:1.” He explained that these stand for Product Owner of Family Tree, Observer of All Genealogists, and Father of 4 with 1 grandchild.&lt;/p&gt; &lt;p&gt;In his session, “FamilySearch FamilyTree: Documenting the World’s Genealogy,” Tanner made a case for a unified, shared, world tree. Without one, there is a lot of duplication of research. It is difficult to continually compare your tree with all the other pedigrees out on several websites. “What will happen to your online tree when you are gone?” he asked. “Who will take over your work?” FamilySearch is expert in preservation. With Family Tree, your work is preserved in the vault.&lt;/p&gt; &lt;p&gt;I’ve already written about much of what Tanner presented. Here’s an item or two that may be new to you.&lt;/p&gt; &lt;p&gt;The history list keeps track of the last 50 people you have worked on. You can quickly jump to any one of them by selecting their name.&lt;/p&gt; &lt;p&gt;The pedigree is a little bit different because it shows couples together, This allows more people to be shown on the screen.&lt;/p&gt; &lt;p&gt;&lt;a href="https://familysearch.org/tree/#view=tree&amp;amp;person=KWC2-8DC&amp;amp;section=pedigree" target="_blank"&gt;&lt;img title="FamilySearch Family Tree pedigree shows couples together" style="border-left-width: 0px; border-right-width: 0px; background-image: none; border-bottom-width: 0px; padding-top: 0px; padding-left: 0px; display: inline; padding-right: 0px; border-top-width: 0px" border="0" alt="FamilySearch Family Tree pedigree shows couples together" src="http://lh4.ggpht.com/-Vgrma4tDSlw/UZLLn7a6xPI/AAAAAAAAEmM/D0LjZgie040/image%25255B4%25255D.png?imgmax=800" width="604" height="503"&gt;&lt;/a&gt;&lt;/p&gt; &lt;p&gt;“Our goal is to make it easier to change data back, than what it takes to change it,” said Tanner. Family Tree allows undoing changes with the click of a button. This addresses the problem in New FamilySearch (NFS) where cleaning up problems took hours and reverting to the erroneous state took seconds.&lt;/p&gt; &lt;p&gt;An original design goal of Family Tree was that every change required an explanation. But some users wanted to edit the explanation associated with the previous change. “[We asked ourselves,] ‘Do we make people add a new reason or let them edit the last reason?’” said Tanner. “We decided to let you edit the last reason.” In my mind this essentially changes the objective from explaining the change to explaining the value. That’s OK, though.&lt;/p&gt; &lt;p&gt;Tomorrow I’ll talk about the future plans for Family Tree.&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;br /&gt;&lt;hr /&gt;
&lt;b&gt;Notice:&lt;/b&gt; The opinions expressed herein are those of the Ancestry Insider, not necessarily those of Ancestry.com or FamilySearch. All content is copyrighted by the Ancestry Insider unless designated otherwise. See http://ancestryinsider.blogspot.com for other important legal notices.&lt;/div&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/AncestryInsider?a=8VJf3_LjX3M:gK1OtNaZcbk:2nqncYFp4_M"&gt;&lt;img src="http://feeds.feedburner.com/~ff/AncestryInsider?d=2nqncYFp4_M" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/AncestryInsider?a=8VJf3_LjX3M:gK1OtNaZcbk:4cEx4HpKnUU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/AncestryInsider?i=8VJf3_LjX3M:gK1OtNaZcbk:4cEx4HpKnUU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/AncestryInsider?a=8VJf3_LjX3M:gK1OtNaZcbk:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/AncestryInsider?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/AncestryInsider/~4/8VJf3_LjX3M" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://ancestryinsider.blogspot.com/feeds/6525424217584884057/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://ancestryinsider.blogspot.com/2013/05/ngs2013-familysearch-family-tree-item.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/5512311610334754148/posts/default/6525424217584884057?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/5512311610334754148/posts/default/6525424217584884057?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/AncestryInsider/~3/8VJf3_LjX3M/ngs2013-familysearch-family-tree-item.html" title="#NGS2013 – FamilySearch Family Tree, An Item or Two" /><author><name>The Ancestry Insider</name><uri>http://www.blogger.com/profile/02490682912125335188</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="30" src="http://bp1.blogger.com/_mpUi75C5vC8/SBgCr-W4YOI/AAAAAAAAAXA/K3itFGYLq_4/S220/simpsonized3.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://lh4.ggpht.com/-k0t3UzZuk7Q/UQQrEecKNdI/AAAAAAAAEJ0/670gstmJpvs/s72-c/image%25255B3%25255D.png?imgmax=800" height="72" width="72" /><thr:total>0</thr:total><feedburner:origLink>http://ancestryinsider.blogspot.com/2013/05/ngs2013-familysearch-family-tree-item.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DU4EQXY8fSp7ImA9WhBbFUQ.&quot;"><id>tag:blogger.com,1999:blog-5512311610334754148.post-99986847503794779</id><published>2013-05-15T00:05:00.000-06:00</published><updated>2013-05-15T00:05:00.875-06:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2013-05-15T00:05:00.875-06:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="Ancestry.com" /><category scheme="http://www.blogger.com/atom/ns#" term="conferences" /><title>#NGS2013 – Stump the Genealogist</title><content type="html">&lt;p&gt;&lt;img title="Crista Cowan" style="border-left-width: 0px; border-right-width: 0px; background-image: none; border-bottom-width: 0px; float: right; padding-top: 0px; padding-left: 0px; display: inline; padding-right: 0px; border-top-width: 0px" border="0" alt="Crista Cowan" align="right" src="http://lh6.ggpht.com/-K8Ejz62w0gw/UZF3OBbkKoI/AAAAAAAAEl8/pHKc9NHkb1o/image5.png?imgmax=800" width="304" height="229"&gt;Friday I attended a presentation in the &lt;a href="http://www.ancestry.com/" target="_blank"&gt;Ancestry.com&lt;/a&gt; booth titled “Stump the Genealogist.” Crista Cowan fielded questions from the audience about their genealogy or about Ancestry.com. The following should not be taken as quotes. I’ve taken some liberties in rewording questions and answers.&lt;/p&gt; &lt;p&gt;Q. Blah, blah, … can’t determine when he might have died… blah, blah… appeared in this census and was gone the next. &lt;/p&gt; &lt;p&gt;A. Have you checked city directories to see when he stopped appearing? The census was taken every 10 years. City directories fill in the gap in between. When they disappear, that’s a clue that they died or moved out of the area. Sometimes the city directory will even give a death date, or list a wife as a widow. &lt;/p&gt; &lt;p&gt;We now have more than 1 billion records in the U.S. city directories database.&lt;/p&gt; &lt;p&gt;To find it, use the card catalog. Point to Search and click on Card Catalog. Filter by “Schools, Directories &amp;amp; Church Histories.” The U.S. City Directories database then appears at the top of the list of databases.&lt;/p&gt; &lt;p&gt;Q. Some directories are not complete. Are you planning on fixing them?&lt;/p&gt; &lt;p&gt;A. We digitized these from microfilm so all we have is what is on the microfilm. &lt;/p&gt; &lt;p&gt;Q. Are you going to get the 1890 census?&lt;/p&gt; &lt;p&gt;A. It was destroyed in a fire.&lt;/p&gt; &lt;p&gt;Q. I can not find my great grandfather. Blah, blah. In 1860 he was 9. Blah, blah.&lt;/p&gt; &lt;p&gt;A. Did he serve in the Civil War? That is where I would focus. Point at Search and click on Military. Down the right-hand column in the More Help section click on Civil War. This will search all our Civil War collections.&lt;/p&gt; &lt;p&gt;Q. I’m looking for the death record of my blah-blah. He blah, blah in New Jersey between 1905 and 1909. And blah blah.&lt;/p&gt; &lt;p&gt;A. Where have you looked for her death record? Here’s one of the things I want you to think about. Every time you do a global search, that’s great. But if I’m looking for something really specific I’ll look to see what records Ancestry.com has. Use the card catalog. Point at Search and click on Card Catalog. &lt;/p&gt; &lt;p&gt;For your blah-blah, you can click on the Birth, Marriage &amp;amp; Death filter to show just vital records. Then click on Death…. Filter by USA and then New Jersey. You could even filter down to the 1910s. You can see we have a database of New Jersey Deaths. I would search just that collection.&lt;/p&gt; &lt;p&gt;Think about what you’re looking for and then see if we have a database that might contain it.&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;br /&gt;&lt;hr /&gt;
&lt;b&gt;Notice:&lt;/b&gt; The opinions expressed herein are those of the Ancestry Insider, not necessarily those of Ancestry.com or FamilySearch. All content is copyrighted by the Ancestry Insider unless designated otherwise. See http://ancestryinsider.blogspot.com for other important legal notices.&lt;/div&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/AncestryInsider?a=FBwpPhAlQSU:Ihuph17lHbc:2nqncYFp4_M"&gt;&lt;img src="http://feeds.feedburner.com/~ff/AncestryInsider?d=2nqncYFp4_M" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/AncestryInsider?a=FBwpPhAlQSU:Ihuph17lHbc:4cEx4HpKnUU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/AncestryInsider?i=FBwpPhAlQSU:Ihuph17lHbc:4cEx4HpKnUU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/AncestryInsider?a=FBwpPhAlQSU:Ihuph17lHbc:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/AncestryInsider?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/AncestryInsider/~4/FBwpPhAlQSU" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://ancestryinsider.blogspot.com/feeds/99986847503794779/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://ancestryinsider.blogspot.com/2013/05/ngs2013-stump-genealogist.html#comment-form" title="3 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/5512311610334754148/posts/default/99986847503794779?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/5512311610334754148/posts/default/99986847503794779?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/AncestryInsider/~3/FBwpPhAlQSU/ngs2013-stump-genealogist.html" title="#NGS2013 – Stump the Genealogist" /><author><name>The Ancestry Insider</name><uri>http://www.blogger.com/profile/02490682912125335188</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="30" src="http://bp1.blogger.com/_mpUi75C5vC8/SBgCr-W4YOI/AAAAAAAAAXA/K3itFGYLq_4/S220/simpsonized3.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://lh6.ggpht.com/-K8Ejz62w0gw/UZF3OBbkKoI/AAAAAAAAEl8/pHKc9NHkb1o/s72-c/image5.png?imgmax=800" height="72" width="72" /><thr:total>3</thr:total><feedburner:origLink>http://ancestryinsider.blogspot.com/2013/05/ngs2013-stump-genealogist.html</feedburner:origLink></entry><entry gd:etag="W/&quot;D0YEQX05eip7ImA9WhBbFUw.&quot;"><id>tag:blogger.com,1999:blog-5512311610334754148.post-4087490080654413316</id><published>2013-05-14T01:05:00.000-06:00</published><updated>2013-05-14T01:05:00.322-06:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2013-05-14T01:05:00.322-06:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="no category" /><title>Family Tree Magazine Honors the Ancestry Insider</title><content type="html">&lt;p&gt;&lt;a href="http://lh4.ggpht.com/-WH63kPIJo5Q/UY_CULxEqzI/AAAAAAAAElk/jUY0QE3xhrw/s1600-h/40bestblogs_13-rgb%25255B8%25255D.png"&gt;&lt;img title="40bestblogs_13-rgb" style="border-top: 0px; border-right: 0px; background-image: none; border-bottom: 0px; float: right; padding-top: 0px; padding-left: 0px; border-left: 0px; display: inline; padding-right: 0px" border="0" alt="40bestblogs_13-rgb" align="right" src="http://lh4.ggpht.com/-kRNcj2dbZ9A/UY_Cg8nJbWI/AAAAAAAAEls/J8zLlDyqSk8/40bestblogs_13-rgb_thumb%25255B4%25255D.png?imgmax=800" width="255" height="142"&gt;&lt;/a&gt;I am humbled to learn that &lt;em&gt;Family Tree Magazine &lt;/em&gt;has honored the &lt;em&gt;Ancestry Insider&lt;/em&gt; blog as a Family Tree Magazine 40 Best Genealogy Blogs in its May/June 2013 issue.&lt;/p&gt; &lt;p&gt;“Let’s tip our collective hats to those bloggers who stick with it and keep sharing their wit, wisdom and family history finds with us,” said contributing editor David A. Fryxell. “We love blogs packed with information, but we also adore those brimming with the blogger’s personality.” &lt;/p&gt; &lt;p&gt;The &lt;em&gt;Ancestry Insider&lt;/em&gt; was honored in the “Tech Support” category. Of the &lt;em&gt;Ancestry Insider&lt;/em&gt;, Fryxell said &lt;/p&gt; &lt;blockquote&gt; &lt;p&gt;That author remains anonymous, though the blog notes with tongue in cheek, “He has been an insider at both the two big genealogy organizations, FamilySearch and Ancestry.com. He was &lt;em&gt;Time&lt;/em&gt; magazine Man of the Year in both &lt;a href="http://www.time.com/time/magazine/article/0,9171,843150,00.html" target="_blank"&gt;1966&lt;/a&gt; and &lt;a href="http://www.time.com/time/magazine/article/0,9171,1569514,00.html" target="_blank"&gt;2006&lt;/a&gt;. And he really is descended from an Indian princess.”&lt;/p&gt;&lt;/blockquote&gt; &lt;p&gt;David, David, David. I really &lt;u&gt;am&lt;/u&gt; &lt;em&gt;Time&lt;/em&gt; magazine Man (Person) of the Year in both 1966 and 2006. And I really &lt;u&gt;am&lt;/u&gt; descended from an Indian princess. &amp;lt;sly-smile&amp;gt;&lt;/p&gt; &lt;p&gt;For the complete list, see “&lt;a href="http://familytreemagazine.com/article/Top-40-Genealogy-Blogs-2013" target="_blank"&gt;Top 40 Genealogy Blogs in 2013&lt;/a&gt;.”&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;br /&gt;&lt;hr /&gt;
&lt;b&gt;Notice:&lt;/b&gt; The opinions expressed herein are those of the Ancestry Insider, not necessarily those of Ancestry.com or FamilySearch. All content is copyrighted by the Ancestry Insider unless designated otherwise. See http://ancestryinsider.blogspot.com for other important legal notices.&lt;/div&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/AncestryInsider?a=_UaTivDWfDQ:ftsFSV08om0:2nqncYFp4_M"&gt;&lt;img src="http://feeds.feedburner.com/~ff/AncestryInsider?d=2nqncYFp4_M" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/AncestryInsider?a=_UaTivDWfDQ:ftsFSV08om0:4cEx4HpKnUU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/AncestryInsider?i=_UaTivDWfDQ:ftsFSV08om0:4cEx4HpKnUU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/AncestryInsider?a=_UaTivDWfDQ:ftsFSV08om0:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/AncestryInsider?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/AncestryInsider/~4/_UaTivDWfDQ" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://ancestryinsider.blogspot.com/feeds/4087490080654413316/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://ancestryinsider.blogspot.com/2013/05/family-tree-magazine-honors-ancestry.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/5512311610334754148/posts/default/4087490080654413316?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/5512311610334754148/posts/default/4087490080654413316?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/AncestryInsider/~3/_UaTivDWfDQ/family-tree-magazine-honors-ancestry.html" title="Family Tree Magazine Honors the Ancestry Insider" /><author><name>The Ancestry Insider</name><uri>http://www.blogger.com/profile/02490682912125335188</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="30" src="http://bp1.blogger.com/_mpUi75C5vC8/SBgCr-W4YOI/AAAAAAAAAXA/K3itFGYLq_4/S220/simpsonized3.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://lh4.ggpht.com/-kRNcj2dbZ9A/UY_Cg8nJbWI/AAAAAAAAEls/J8zLlDyqSk8/s72-c/40bestblogs_13-rgb_thumb%25255B4%25255D.png?imgmax=800" height="72" width="72" /><thr:total>0</thr:total><feedburner:origLink>http://ancestryinsider.blogspot.com/2013/05/family-tree-magazine-honors-ancestry.html</feedburner:origLink></entry><entry gd:etag="W/&quot;AkAEQXk4eip7ImA9WhBbFE8.&quot;"><id>tag:blogger.com,1999:blog-5512311610334754148.post-2606261635662733939</id><published>2013-05-13T01:05:00.000-06:00</published><updated>2013-05-13T01:05:00.732-06:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2013-05-13T01:05:00.732-06:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="conferences" /><title>#NGS2013 – Cutting Through the Confusion: Research in Upstate New York</title><content type="html">&lt;p&gt;At the 2013 annual conference of the &lt;a href="http://www.ngsgenealogy.org" target="_blank"&gt;National Genealogical Society&lt;/a&gt;, Karen Mauer Green presented a session titled &lt;a href="http://app.core-apps.com/ngs2013/speakers/be382acd90f3d098fb38f868ce41bdac" target="_blank"&gt;&lt;img title="Karen Mauer Green" style="border-top: 0px; border-right: 0px; background-image: none; border-bottom: 0px; float: right; padding-top: 0px; padding-left: 0px; border-left: 0px; display: inline; padding-right: 0px" border="0" alt="Karen Mauer Green" align="right" src="http://lh3.ggpht.com/-V2lCC3Ju5Lw/UY00R5RqBpI/AAAAAAAAElI/JpX0m7T5uMo/image%25255B3%25255D.png?imgmax=800" width="136" height="204"&gt;&lt;/a&gt;“Cutting Through the Confusion: Research in Upstate New York.” Green is an editor, author, lecturer, and professional genealogist. She co-edits the NYGB Record. She has served on the boards of APG and FGS.&lt;/p&gt; &lt;p&gt;“This is a huge subject, upstate new york,” she said. “We can’t cover it all in one hour.”&lt;/p&gt; &lt;p&gt;“I want to give you some guidelines and tips and also warn you about some pitfalls,” she said.&lt;/p&gt; &lt;p&gt;The definition of “upstate” differs by person and situation. For purpose of the lecture, Green defined upstate New York as everything but the five boroughs of New York City. She focused on the time span 1780-1850.&lt;/p&gt; &lt;p&gt;One confusion experienced by researchers in New York state is town versus township. In New York, the concepts are equivalent. In my recent research, I found records giving the living place of an individual alternately as Dugway and Albion. Both are true because Dugway is a place (hamlet?) within the Town of Albion in Oswego County.&lt;/p&gt; &lt;p&gt;“You’re used to having records in certain places and that is not always the case. It leads to blinders.” There is no real consistency among counties. Counties differ in “what information is recorded, what the record is called, how and where the record is preserved, and how the record is accessed.”&lt;/p&gt; &lt;p&gt;“This has all been very negative, but I have more bad news,” Green said. In the focus time period there are no New England style town vital records, A state law to keep them was passed in 1881, but consistent records were not kept until 1908. Further, there were no county marriage records.&lt;/p&gt; &lt;p&gt;Substitutes for vital records are worth looking for. Some are newspapers, justice of the peace records, minister’s records, and church records.&lt;/p&gt; &lt;p&gt;Green discussed other records useful for doing research in the time period, which I won’t mention.&lt;/p&gt; &lt;p&gt;“I know I have been discouraging to you, but the good news is that people do break through [brick walls],” she said. Back up. Start over. Apply cluster methodology (Elizabeth Shown Mills’s FAN club—Friends, Associates, and Neighbors). &lt;/p&gt; &lt;p&gt;“You will almost always find a gate,” she said&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;br /&gt;&lt;hr /&gt;
&lt;b&gt;Notice:&lt;/b&gt; The opinions expressed herein are those of the Ancestry Insider, not necessarily those of Ancestry.com or FamilySearch. All content is copyrighted by the Ancestry Insider unless designated otherwise. See http://ancestryinsider.blogspot.com for other important legal notices.&lt;/div&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/AncestryInsider?a=GKiUjB-G5RE:jlSzrO_jcFA:2nqncYFp4_M"&gt;&lt;img src="http://feeds.feedburner.com/~ff/AncestryInsider?d=2nqncYFp4_M" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/AncestryInsider?a=GKiUjB-G5RE:jlSzrO_jcFA:4cEx4HpKnUU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/AncestryInsider?i=GKiUjB-G5RE:jlSzrO_jcFA:4cEx4HpKnUU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/AncestryInsider?a=GKiUjB-G5RE:jlSzrO_jcFA:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/AncestryInsider?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/AncestryInsider/~4/GKiUjB-G5RE" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://ancestryinsider.blogspot.com/feeds/2606261635662733939/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://ancestryinsider.blogspot.com/2013/05/ngs2013-cutting-through-confusion.html#comment-form" title="3 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/5512311610334754148/posts/default/2606261635662733939?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/5512311610334754148/posts/default/2606261635662733939?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/AncestryInsider/~3/GKiUjB-G5RE/ngs2013-cutting-through-confusion.html" title="#NGS2013 – Cutting Through the Confusion: Research in Upstate New York" /><author><name>The Ancestry Insider</name><uri>http://www.blogger.com/profile/02490682912125335188</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="30" src="http://bp1.blogger.com/_mpUi75C5vC8/SBgCr-W4YOI/AAAAAAAAAXA/K3itFGYLq_4/S220/simpsonized3.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://lh3.ggpht.com/-V2lCC3Ju5Lw/UY00R5RqBpI/AAAAAAAAElI/JpX0m7T5uMo/s72-c/image%25255B3%25255D.png?imgmax=800" height="72" width="72" /><thr:total>3</thr:total><feedburner:origLink>http://ancestryinsider.blogspot.com/2013/05/ngs2013-cutting-through-confusion.html</feedburner:origLink></entry><entry gd:etag="W/&quot;A0cFQXw7fCp7ImA9WhBbEU4.&quot;"><id>tag:blogger.com,1999:blog-5512311610334754148.post-6128441489133107835</id><published>2013-05-09T16:36:00.001-06:00</published><updated>2013-05-09T16:36:50.204-06:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2013-05-09T16:36:50.204-06:00</app:edited><title>#NGS2013 - Online Tools for Genealogists</title><content type="html">&lt;p&gt;&lt;a href="http://lh5.ggpht.com/-FP53_RTE_Cg/UYwk-T7PMzI/AAAAAAAAEkw/2NGDge5W1Sc/s1600-h/image%25255B2%25255D.png"&gt;&lt;img title="Barbara Ann Renick" style="border-top: 0px; border-right: 0px; background-image: none; border-bottom: 0px; float: right; padding-top: 0px; padding-left: 0px; border-left: 0px; display: inline; padding-right: 0px" border="0" alt="Barbara Ann Renick" align="right" src="http://lh5.ggpht.com/-EdMKMFh-izI/UYwk_1BV4dI/AAAAAAAAEk4/eBeTLGHlfyQ/image_thumb.png?imgmax=800" width="204" height="204"&gt;&lt;/a&gt;Barbara Ann Renick presented “Online Tools for Genealogists” at the 2013 annual conference of the &lt;a href="http://www.ngsgenealogy.org" target="_blank"&gt;National Genealogical Society&lt;/a&gt; (NGS). &lt;/p&gt; &lt;p&gt;Renick is secretary for the NGS board of directors and authored &lt;em&gt;Genealogy 101: How to Trace Your Family’s History and Heritage&lt;/em&gt;.&lt;/p&gt; &lt;p&gt;In her session titled “Online Tools for Genealogists” she spoke on “seven types of online tools genealogists find helpful: language and handwriting, time and calendar, geographic and map, history and background information, help and educational, utilities, and locator tools.”&lt;/p&gt; &lt;p&gt;One of the tools she mentioned was the &lt;a href="http://geonames.usgs.gov/pls/gnispublic/f?p=132:1:553203805442538" target="_blank"&gt;Geographic Names Information System&lt;/a&gt; (GNIS), a national gazetteer. &lt;/p&gt; &lt;p&gt;“All of you pay your taxes and you deserve to get something back,” she said. GNIS is produced by the United States Geological Survey (USGS)&lt;/p&gt; &lt;p&gt;GNIS includes not just current place names but historic names as well. I used this capability recently. I wanted to visit the Happy Valley Cemetery in Oswego County, New York. I couldn’t find it on any map (and I didn’t think to use Find-A-Grave.) I searched on GNIS and found it easily. With an additional click I had it plotted on a map.&lt;/p&gt; &lt;p&gt;Renick has published links to the online tools on her Z Links page, &lt;a href="http://www.zroots.com/links.htm" target="_blank"&gt;www.zroots.com/links.htm&lt;/a&gt;.&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;br /&gt;&lt;hr /&gt;
&lt;b&gt;Notice:&lt;/b&gt; The opinions expressed herein are those of the Ancestry Insider, not necessarily those of Ancestry.com or FamilySearch. All content is copyrighted by the Ancestry Insider unless designated otherwise. See http://ancestryinsider.blogspot.com for other important legal notices.&lt;/div&gt;&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/AncestryInsider?a=VBBf_LvBsWI:NM9vHnzyi90:2nqncYFp4_M"&gt;&lt;img src="http://feeds.feedburner.com/~ff/AncestryInsider?d=2nqncYFp4_M" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/AncestryInsider?a=VBBf_LvBsWI:NM9vHnzyi90:4cEx4HpKnUU"&gt;&lt;img src="http://feeds.feedburner.com/~ff/AncestryInsider?i=VBBf_LvBsWI:NM9vHnzyi90:4cEx4HpKnUU" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/AncestryInsider?a=VBBf_LvBsWI:NM9vHnzyi90:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/AncestryInsider?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/AncestryInsider/~4/VBBf_LvBsWI" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://ancestryinsider.blogspot.com/feeds/6128441489133107835/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://ancestryinsider.blogspot.com/2013/05/ngs2013-online-tools-for-genealogists.html#comment-form" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/5512311610334754148/posts/default/6128441489133107835?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/5512311610334754148/posts/default/6128441489133107835?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/AncestryInsider/~3/VBBf_LvBsWI/ngs2013-online-tools-for-genealogists.html" title="#NGS2013 - Online Tools for Genealogists" /><author><name>The Ancestry Insider</name><uri>http://www.blogger.com/profile/02490682912125335188</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="30" src="http://bp1.blogger.com/_mpUi75C5vC8/SBgCr-W4YOI/AAAAAAAAAXA/K3itFGYLq_4/S220/simpsonized3.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://lh5.ggpht.com/-EdMKMFh-izI/UYwk_1BV4dI/AAAAAAAAEk4/eBeTLGHlfyQ/s72-c/image_thumb.png?imgmax=800" height="72" width="72" /><thr:total>1</thr:total><feedburner:origLink>http://ancestryinsider.blogspot.com/2013/05/ngs2013-online-tools-for-genealogists.html</feedburner:origLink></entry></feed>
