tag:blogger.com,1999:blog-5512311610334754148.post6840753353872440547..comments2023-04-20T12:46:11.858-06:00Comments on The Ancestry Insider: Genealogy Life Blood at Kendall Hulet #RootsTech LuncheonThe Ancestry Insiderhttp://www.blogger.com/profile/02490682912125335188noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-5512311610334754148.post-68892381513288197662016-02-20T12:27:56.253-07:002016-02-20T12:27:56.253-07:00While bad hints are a pain in the neck to be sure,...While bad hints are a pain in the neck to be sure, I wish they would teach their computers NOT to give me hints of things that are already IN my tree. <br /><br />The system is certainly capable, with some programming corrections, NOT to show HINTS that are already IN your tree and attached to the very person these HINTS show up for! <br /><br />I have one cousin who cannot seem to figure out how to use the ancestry FTM properly and she will copy a hint or photo 10 times--OFTEN THESE ARE FROM MY TREE AND I AM THE ORIGINATOR OF THE DOCUMENT WHICH IS ALREADY IN MY TREE--then I get 10 hints on a person for a photo or document that I added to begin with...It is a waste of my time to have to go look at these and delete--not to mention I think "aha ancestry has found some info for me" only to see it is something that is not only in my tree, but the hint is the same thing 10 times! <br /><br />I also wish they would stop calling the "family data" SOURCES--they are not sources, they are amalgamations of what various other people have put on their trees-and are often incorrect although sometimes useful to look at to see if any of it is correct BUT they are not and never will be SOURCES. <br /><br />I do glance at other trees that show up in hints BUT I only look at trees that have sources---I don't know how many times I have seen a tree that SUPPOSEDLY has 20 sources--only to find out that person has added the Family Data "sources" many times over...a waste of my time to look at that stuff...<br /><br />PLEASE ancestry stop calling these things sources, they are not. Find something else to call them, and find a different way to index them into the system so they do not show up when looking at "tree hints" as a source! They are not and never will be sources and it is misleading to call them such. <br /><br />Those of us who have been around a while know enough to ignore these but new users really think of them as sources...so that is misleading for them, but it is especially annoying to look at other family trees, thinking they have a ton of sources, only to find out they have attached these databases (often several times) that are not SOURCES at all.<br /><br />Joyce wrdsrushttps://www.blogger.com/profile/03979538866342575847noreply@blogger.comtag:blogger.com,1999:blog-5512311610334754148.post-68765991761133147132016-02-17T14:28:34.678-07:002016-02-17T14:28:34.678-07:00But since hints are only as good as the transcript...But since hints are only as good as the transcriptions, I shudder to think of any narrowing based on Ancestry transcriptions. However, I agree that having hints that are decades--and even whole countries!--off from any possible involvement by the person seem as if they could readily be fixed. I am so sick of getting US Revolutionary War hints for female relatives born in Canada in the 1920's, seemingly based on something like a middle initial.JudyBGhttps://www.blogger.com/profile/11481961917093120257noreply@blogger.comtag:blogger.com,1999:blog-5512311610334754148.post-44172581991121415162016-02-17T05:18:12.468-07:002016-02-17T05:18:12.468-07:001) Ancestry should substitute the word "relat...1) Ancestry should substitute the word "relative" for "ancestor" in search boxes and narratives about using search engines.<br /><br />2) Simple logic indicates that my ancestor born in 1859 could not have served in the Revolutionary War or the US Civil War. Yet for years the search engine comes up with such ridiculous search results. Can they not teach the machines to do the math?<br /><br />3) They still have not fixed the drop-down place lists for pre-1870 US Census enumerations to show the presently-in-WV Counties in VA through 1860. They have known about this glitch for years. It needs to be fixed.<br />Geoloverhttps://www.blogger.com/profile/12050268303916428230noreply@blogger.com