Ancestry Public Trees versus Private - a new debate

I was about to give your post a 'Like' icon, but thought it deserved more of a 'BRAVO' as it comes close to expressing my own viewpoint. Nice one Pauline and I even got your name right (an old story).

 

Quite a profound comment Bryman with hidden depth. Well said,

 

Yes, mea culpa of course you were referring to the Forum but my comment still stands about ONLY being advised to change my photo. As for the reading the registration page, sorry I have no memory of that at all. Reading instructions - like user manuals and flat pack instructions - is not my strong point. I know that is the bane of your life, but it is what it is.

 

Looking back I came across your post about your Grandfather being in the USA. It immediately reminded me that once -and only once (after receiving numerous similar Hints assigning ancestors to far off place , particularly the USA which were nonsensical) - one such hint - (relating to a female ancestor in the early 20th Century being resident in the USA) turned out to be factual. But not before it was nearly kicked into touch as 'barmy'' because all her siblings (a fair few) were resident in the UK.

However before so doing as I knew another researcher (a cousin of sorts, I forget which) had much better information on that side of the family so I made contact. To my extreme surprise I was told her Aunt had indeed 'upsticked' after some disagreement or other with the family and emigrated to the USA. She married out there are had a quite extensive family. This just goes to show that occasionally, perhaps very occasionally, some of the more fanciful hints may just be worth pursuing.

 

I agree in spirit but please excuse my being a pedant. All hints from Ancestry, FMP or wherever, are all facts but only potentially relevant to that particular tree. It is up to the appropriate researcher to determine if the fact fits. Many don't.

I also had a somewhat similar experience which I nearly didn't follow up. There appeared to be a record of someone with the same name as my aunt, passing from Canada to USA towards the end of WWII. I 'knew' that my aunt was working as a cypher clerk at the Foreign Office in London during the war so nearly dismissed it as a coincidence. However, I passed the information on to my cousin, who lived near her mother, and we were both shocked to learn that the record in Ancestry was for my aunt's trip to attend a secret conference in California. This all happened before my aunt was married and my cousin was born and I don't think that anyone had been told about that until my discovery. Apparently, the trip came as a very welcome break from the difficulties surrounding life in London at that time. Without the prompt, my cousin may never have found out about that aspect of her mother's life.

 

Yes another example showing we just do not know what is around the corner when researching.

The extensive search algorithms used by Ancestry/FMP & others are far removed in complexity (and therefore accuracy) from those used by 'Google'. At best they relate to a surname (with a few 'soundexes' thrown in), combined with first names (ditto). If luck is on your side other people (like Parents/Spouse/Siblings) and even 'Keywords' may help the result as will Location...hopefully the same county and country. But the final arbiter is often the date range -taken into consideration with names and places. Only then can you determine if the result is real or fanciful.

I suppose, being fair, Ancestry et al get it right often enough for their Hints NOT to be dismissed out of hand. And when they get it 'really right' then -to coin an old phrase - you are in Clover! If not move on to the next Hint.

 

That is just a subset of hints and, yes, errors are the result of carelessness by the "tree builder" (I cannot bring myself to use "researcher"). However, the reason many of the trees are inaccurate is that the hints Ancestry give wrt records are often wildly wrong - hints for a baptism in Lancashire implying that my recorded baptism in Wiltshire is incorrect, for example.

For one Wiltshire person in my tree, Ancestry suggested three events over a few weeks starting with a birth in the Derbyshire area, a baptism shortly after in East Anglia followed by an event in Wiltshire - none were correct. For anyone not familiar with the country that may not seem "unusual".

Admittedly, I do not help Ancestry as I do not always use their "database" place names, but giving hints for a town in USA because I add "UK" at the end of a place name is definitely odd!

I shall refrain from comment on the final sentence!

Phil

 

Yes Tim, that observation is right on the ball. I would however question whether it can be said that Ancestry's data base contains errors per se. After all everything they have has to relate to someone somewhere, but as Eric Morecombe said to Andre Previn in the famous Morecombe & Wise piano playing sketch about the sequence of notes played being - "not necessarily in the right order." So they are errors of misplacement.

That is why I also agree with your statement:

- providing of course the sources fits your facts.

Peter often refers to 'Fake News' and that is indeed what we are getting via Ancestry Hints. I can relate to almost everything posted by others about getting information that just does not and cannot apply to your ancestor - give or take the odd time when it just might...perhaps!

It means we have to be on our toes and separate the Good from the Bad, which is something we all have to do all of the time.

 

God heavens Phil, you are surely asking for trouble, no wonder the poor algorithm picking up the 'U' offered USA as one of its choices. It reminds when we had a dog how it would pick up the 'W' in the word "Walkies" before we ever finished the word, so we could not between us (my wife and I) even ask whose turn it was for the 'W'.

 

You don't ask for much in life do you Tim... 'only viewable with a shared ancestor' So, no (jigsaw) edge pieces or look-a-like shapes for you, you want the real thing, that just slots into place; not unlike the poker player seeking a royal flush. Life just 'ain't' like that I'm afraid, and sometimes the thrill of the chase gives more satisfaction. Still one can dream of course.

 

Fully agree with that and as Phil already admits has contributed to his own problem as Ancestry never uses ' UK'. They always finish off a location with the country, England..etc.

That should of course have been picked up as an error by Ancestry on the Tree that originated the fact. So clearly error checking not high on Ancestry's list. As you say, other software can be used to check for errors, as can FTA of course.
(Which reminds haven't used that in a while must resurrect the latest version, and is Alexander still about? Used to be a regular poster in the early days of the Forum?)

That sounds like a work around that might afford an easy life for Private Tree owners, so couldn't possibly comment.

 

My next update should ensure that ", UK" no longer appears - most have already been corrected. [rhetorical]However, for someone born in 1835 should I use Bettws, as shewn on the 1831 OS map, or Betws as shown on the latest OS map?[/rhetorical]

That's enough "off topic" from me - it's supposed to be private vs public trees!

Phil

 

You have just reminded me that I too had that intention (directs only) but got carried away I'm afraid....I think a little editing is required!

 

As often happens with ‘for’ and ‘against debates, there comes a time when there is a lull when arguments tend to be repetitious. So here is my summation of the state of play.

The arguments supporting Public or Private Trees is NOT new. Not only aired previously in this Forum but ongoing for years in every nook and cranny where Family History holds sway.

I provided a link to Crista Cowan’s (Barefoot Genealogist) YouTube video of 2012 who, although undoubtedly supporting the Ancestry cause, makes reasonable arguments to support both types of Tree. If you prefer to read Blogs on the subject I suggest you try the one begun by Jannine Adams which you will find here: Ancestry Blog She began this in 2014 and it was still running through 2017 & beyond. It received numerous responses supporting both sides of the spectrum. And, if you have a spare hour or two, try Roots Chat and search for “Errors in Trees -letting off steam” which will certainly find favour with those for whom this subject raises hackles.

Despite all the ‘for’ and ‘against’ arguments presented, I doubt few will change sides! However, it is just possible the arguments to have both Public & Private – for different reasons – could win support. We know Peter and one or two others have opted for a Public Tree for analysing DNA results (albeit tailored to show only direct ancestors) but it is a start.

It may also surprise some to know I can now see when it might be advantageous to make some Trees Private, although I have to say up front this does not apply to my main Trees. I have already mentioned making an experimental Tree Private/Unsearchable, but I have just changed another -started about a year ago for a new (by marriage) connection to a Bermudan family - which has some sensitive family information which I believe is best contained within a Private/Searchable Tree.

So, if I can be persuaded to adapt my previously immutable stance of advocating only Ancestry Public Trees – even though the ‘public’ principle is still very dear to my heart - then it is not beyond reason for others to reconsider where they stand on the matter, even if - like me - only to accept there may be a need to consider both types of Tree

 

I totally agree. I once found a public tree of a distant cousin (related to my mother) which had my father in completely the wrong family, but to be fair the tree owner corrected the mistake immediately after I contacted them and pointed out the error. I now try to keep an eye on where my close relatives appear in public trees. The main reason I keep my own tree private (but searchable) is to avoid any mistakes I make being perpetuated by others in public trees. Though I suppose if it was public, others might point out if I've got things wrong for their close relatives. Now I am torn...

 

This sounds like a good idea, but it would not help in some common situations. I have made contact with several DNA cousins - at the 3rd-4th cousin level - who would not have made the connection with such a tree, as they'd hit a brick wall before reaching our common ancestors. Typically their grandparent or great-grandparent had emigrated from England to the US or Australia, and I recognised the person from a branch of my tree, but they wouldn't appear in a 'direct ancestor only' tree (even the surname wouldn't match if the connection was on a female line). I guess a combination of approaches is always required.

 

Well said - I agree entirely. A quick look at the Ancestry 'hints' from public trees - many of which contradict each other - shows how much misinformation is out there.