Stopping errors being added to an existing tree
I have a tree that has had a number of incorrect additions made by somebody or something. Genealogy is a fact based study of our ancestors, and allowing others to make changes by adding something like a mother who died a year before the child was born, would have been 63 years old, and lived in the US while the birth in 1823 took place in Germany. Makes me really p/o'd that I made the mistake of sharing my GEDcom on FamilySearch.
Comments
-
Gary, you appear to have missed a rather crucial fact: the Family Tree on FamilySearch is a single, communal, open-edit endeavor, intended to eventually have one and only one profile per deceased person. There will always be clueless people who assume that anyone with the same name must be the same person, but preventing their errors would also equally prevent your corrections.
There are communal trees online that have some degree of curation or content control, but they're far smaller than FamilySearch's tree, so the problems they experience because of their "locks" can be dealt with by a mostly-volunteer staff (and a lot of patience). I don't believe that any of the alternate models I've seen would translate at all workably to a tree the size of FamilySearch's.
0 -
I agree with Gary.
Julia is correct, but, Family search should be sensitive to clearly erroneous data / facts. I use FamilyRoots 7 / 8 and, if I enter a fact as Gary suggests where a mother died a year before a child's birth, the software instantly flags it. Family search should do the same and not allow the person to make the entry.
0 -
Gary & John
I am just another 'lowly' User/Patron ...
Just in passing ...
You are not alone ...
MANY; Many; many, of us, ... have been there ...
Many of us have had 'wayward' "Changes" made to our "Ancestral" Lines ...
Now ...
That Said ...
Please be aware, that technically, one DOES NOT, have a "Tree", in "Family Tree", of 'FamilySearch' ...
Please let me explain ...
Technically, there is no way, to STOP, another User/Patron, working along the SAME 'Ancestral" Lines.
Unfortunately, such CANNOT be prevented.
As, basically, we are all related.
One's "Ancestral" Lines, are most likely ALSO another User's/Patron's "Ancestral" Lines, in fact, probably, that of quite a few other Users/Patrons.
Now ...
That Said ...
Basically, we DO NOT have, a "Tree", in "Family Tree", of 'FamilySearch', than is common misconception.
And, OTHER Users/Patrons, DO NOT need/require, our (ie. one's) "Permission", to "Change" the information/details of "Deceased" individuals/persons, in "Family Tree", of 'FamilySearch'.
Here an old 'standby' of mine, that I have previously proffered on occasion ...
------------------
Most new (and, some old) Users/Patrons, DO NOT, understand, the basic 'nature' and 'premise', of the "Family Tree" Part, of 'FamilySearch', when they join in.
We do not have our OWN "Tree", in the "Family Tree" Part, of 'FamilySearch'.
We ONLY have "Branches" (ie. Ancestral" lines), that are interconnected, in this SINGLE "One" World "Tree", for all of us, that is the "Family Tree" Part, of 'FamilySearch'.
The "Family Tree" Part, of 'FamilySearch', is NOT like 'On-Line' "Websites" (eg. "Ancestry_com"; or "MyHeritage_com"; or, the like); and/or, 'standalone' personal (computer) programmes (eg, the OLD, now no longer supported, "PAF"; or, "Ancestral Quest"; or, the like).
We DO NOT have "Private"/"Personal" 'Trees', in the "Family Tree" Part, of 'FamilySearch', like other 'On-Line' "Websites"; and/or, 'standalone' personal (computer) programmes.
We do not even, own; or, manage; and, are NOT even responsible for, the "Deceased" individuals/persons, in "Family Tree" Part, of 'FamilySearch'.
And, most importantly ...
We DO NOT even, own; or, manage; and, are NOT even responsible for, Our OWN "Deceased" Ancestors/Family/Relatives, in the "Family Tree" Part, of 'FamilySearch'.
The "Family Tree" Part, of 'FamilySearch', is built on a "Open Edit" Platform - hence, why any "Registered" User/Patron can "Edit" (ie. Add, Delete; and/or, Change) ANY "Deceased" individual/person, in the "Family Tree" Part, of 'FamilySearch'.
------------------
In other words ... "Collaboration" ...
Of course ... often ... easier said, than done ...
[ Sometimes, no matter how hard one tries, "Collaboration", does not work ... such is life ... ]
We ALL make MISTAKES ...
NONE of US are PREFECT ...
None of us want to have our "Ancestral" Lines 'messed up'; but, unfortunately, it happens.
I know, that this certainly does not help/assist; but, I hope, that this may provide you with, some additional, insight; and, perspective.
Brett
0 -
Gary & John
Furthermore ...
Just in passing ...
FIRSTLY ...
That is exactly why, many Users/Patrons, ALSO maintain their own PRIVATE "Database(s)" (ie. Copies) of their "Ancestral" Lines , on 'On-Line' "Websites" (eg. "Ancestry_com"; or "MyHeritage_com"; or, the like); and/or, 'standalone' personal (computer) programmes (eg, the OLD, now no longer supported, "PAF"; or, "Ancestral Quest"; or, the like).
And ...
SECONDLY ...
All that one can really do, is 'Monitor', one's "Ancestral" Lines, for 'wayward' CHANGES, by OTHER Users/Patrons.
Nothing more, nothing less ...
As an aside ...
IF, you were not already aware; THEN, ...
In "Family Tree", of "FamilySearch' ...
We have the ability to "Watch" (Oops, sorry, 'old school', "Follow"), up to a MAXIMUM of x4000 individuals/persons, at any given time.
Basically ...
It is a matter, of "Following", one's MOST important Ancestors.
Just to keep on top, of any 'wayward' CHANGES.
I check, the "Changes" to those that I "Follow", on a "Daily" Basis; so that, I can keep on top of things.
More often that not, nothing needs to be done; but, at least, I have the opportunity, to be abreast of things; as, they happen/transpire/unfold.
Just my thoughts.
Brett
0 -
@Brett . Thanks for your info. I am a very experienced genealogist and know Family Search quite well and very much understand how the 'Family Tree' works.
In my previous answer, I am suggesting that the website software should 'trap' obvious errors and remind the patron entering the data / fact, that they are in error.
I am suggesting this because errors pointed out by Gary cause a lot of extra work to check & deal with, work that the patron entering the data should have done themselves.
1 -
John
I 'hear' you ...
But ...
That Said ...
Just in passing ...
The "System" (ie. "Family Tree" Part, of 'FamilySearch') ALREADY does "Indicate" (ie. 'Trap') the obvious ERRORS
ie. The "System" (ie. "Family Tree" Part, of 'FamilySearch') ALREADY does Warn/Remind/Advise/etc ...
The Problem/Issue is, that MANY Users/Patrons, DON'T, act upon; or, action, them, when they are PRESENTED
ie. Unfortunately, MANY Users/Patrons, simply just, DO NOT, "Heed", the Warnings/Reminders/Advice/etc ...
As, a Programmer, once said to me ...
[ And, NOT, from 'FamilySearch' ... ]
You CANNOT, make a "System" FOOLPROOF; as, FOOLS, are so INGENIOUS ...
That is so true ...
[ Not to forget to mention, in many cases, 'Inexperienced'; and/or, 'Lack of Attention to Detail' ... ]
And ...
'Yes', the ERRORS, by OTHER Users/Patrons, DO "... cause a lot of extra work to check & deal with, work that the patron entering the data should have done themselves ..."
That is a 'Given' ...
Just my thoughts.
Brett
ps: We just, DO NOT, need, the "Family Tree" Part, of 'FamilySearch', to be, too "Restrictive" (or, onerous) ...
pps: Plus, we should NOT, have to WAIT, for OTHER Users/Patrons, to "Respond"; BEFORE, making a "Change"
.
2 -
@JohnSoppet, how does the software you use deal with corrections? Can you only do them in a specific way in order to not get trapped by an error flag? For example, if an ancestor has a birthdate of 1870 and a marriage date of 1888, but I discover that both of those are wrong, and should be 1880 and 1898, respectively, will I have to correct the marriage before I can correct the birth?
A "hard trap" on data discrepancies will inevitably result in such "you can't get there from here" problems, and is therefore to be very carefully avoided.
1 -
@Julia Szent-Györgyi I use FamilyRoots8. I have not tested your example. Will do soon. (presently dealing with a computer issue) FR8 simply flags that the person is too young to be married. I think you should be able to correct either date first. I will return to this issue in about a week.
0 -
Dear Gary Engle.
I understand your frustrating experiences with FS Familytree. I have been there too, but still love to work in this tree.
These are the two most important things I do to avoid that frustration and deal with the mistakes of others (and hope others do the same to deal with mine):
1) I add to each individual profile as many records and other sources as possible to prove that the tree information is correct. Adding sources is crucial.
2) I follow my ancestors and get a weekly notification of absolutely all changes if any. This makes it possible to address the problem fairly soon, either by correcting the mistake or by sending a message to the person who made the mistake. Sometimes I do both.
Kindly,
Anne-Kathrine Henriksen
0
