GEDCOM or similar dumping by people is frustrating
I have done extensive research and data entry on my ancestory tree including a trip to Europe to find records which I have uploaded. It is very frustrating that anyone can overwrite a person in my tree with no sources and no documentation or image uploads simply by using their GEDCOM file or citing another genealogical service as a "source". When they create someone already in the FS database who is in my tree, it effectively wipes out all the work I have manually done. Does the FS program place higher priority on the date created but not the amount or strength of the data? It seems like it does but I can't be sure. If so, that should be reprogrammed.
Also, simply using a geneological data file without cross checking the data is destructive and disregards those of us who put in hard research and verification source work. GEDCOM and similar files are often filled with errors due to program compilation glitches. Something as minor as a misplaced number in a date or an extra comma can cause, for example, a grandfather to show his son as his father or a daughter that also becomes her mother. I respectfully request F.S. try to make an option to lock an family tree from being changed by others like this so easily. There should be a way to keep your work safe and individualized if you want to. Perhaps offering different account types? I would be willing to pay a one time donation or one time fee for any feature or option that keeps people from eradicating my work, uploads, photos and basically messing with my tree
Comments
-
I forgot to mention that yes I know I can remove people or merge them to fix this type of problem, but after doing that fix so much, it has really become a time sync. There should be a better way to maintain and protect a well researched and correct family tree
0 -
FYI
Welcome to the "Community.FamilySearch" Forum.
I am just another 'lowly' User/Patron ...
Just in passing ...
You are not alone ...
MANY of us, share you frustration ...
MANY of us, over the MANY Years, have Requested/Begged/Pleaded/(even) Demanded that 'FamilySearch', simply STOP allowing, the "Upload", of GEDCOM Files, into the "Family Tree" Part, of 'FamilySearch', altogether - to NO avail.
There is just NO need, to "Upload", a GEDCOM File, into the "Family Tree" Part, of 'FamilySearch' under ANY circumstance; even, if one's "Ancestral" Lines, are NOT already, in the "Family Tree" Part, of 'FamilySearch'.
As I always 'say', to User/Patrons, who mention, the "Upload", of GEDCOM File, into the "Family Tree" Part, of 'FamilySearch' ...
------------------
You can; but ...
Please, DO NOT, "Upload", a GEDCOM File, into the "Family Tree" Part, of 'FamilySearch'.
Upload, the GEDCOM Files, in the "Genealogies" Part, of 'FamilySearch', that is fine; but, please NOT, into the "Family Tree" Part, of 'FamilySearch'.
Some of the reasons, that Users/Patrons (like myself), DO NOT, want the ability, to upload, a GEDCOM File, into the "Family Tree" Part, of 'FamilySearch' are:
(1) It is most likely, that individuals/persons in a GEDCOM File, are ALREADY, in the "Family Tree" Part, of 'FamilySearch'; and, most Users/Patrons, DO NOT; even, take the time to 'look', to 'see', if anyone in their GEDCOM File, is already in "Family Tree", in some instances, negating the need to even upload the GEDCOM File.
(2) There has been (many) cases; where, Users/Patrons, using the "Compare" process (of the upload), have "Dismissed", a "Possible" Match, with an individual/person already, in "Family Tree"; so that, THEIR "Record", from their GEDCOM File, is loaded into "Family Tree", regardless; just so that, their "Record" appears in "Family Tree" (and, in some instances, for Members of the Church, so they can do the "Temple" Work, despite the fact, that the "Temple" Work, is ALREADY done, with the "Possible" Match, with the individual/person already, in "Family Tree").
(3) Even with the "Compare" process (of the upload), there has been (many) cases; where, Users/Patrons, have uploaded, THEIR version of an individual/person, in their GEDCOM File, on top of (ie. Over) an individual/person ALREADY, in the "Family Tree" Part, of "FamilySearch", that has been there for MANY years and is well documented and "Sources" - in many instances obliterating all of the documentation and "Sources".
(4) If an individual/person, is ALREADY, in the "Family Tree" Part, of "FamilySearch", there is NO need, to uploaded one's version of an individual/person, from one's own GEDCOM File - just take note of the the 'FamilySearch Person Identifier' (PID) of the individual/person, that is ALREADY, in "Family Tree"; and, one can go back later, to ensure what information/detail, is recorded and attached, for that individual/person. Just, DO NOT, uploaded one's version of an individual/person, in one's GEDCOM File, on top of (ie. Over) an individual/person ALREADY, in "Family Tree" - obliterating, all of the documentation and "Sources", ALREADY in place/on record.
(5) The "Hours" (sometimes "Days"; or, even, "Weekes") of work, by other Users/Patrons, that can be needed to CORRECT the DAMAGE, done by the "Upload", of a GEDCOM File, can be disheartening.
I am sorry ... 'off my soap box' ...
Enter (ie. 'Create') the individuals/persons, in the "Family Tree" Part, of 'FamilySearch', one at a time - on a one by one basis.
Many of the individuals/persons in a GEDCOM File, most probably, ALREADY exist in, the "Family Tree" Part, of 'FamilySearch'.
Only one or two generations of the "Living" individuals/persons; and, perhaps, maybe, only one or two generations of the "Deceased" individuals/persons, may be required to be entered/input, into the "Family Tree" Part, of 'FamilySearch"; BEFORE, some of the "Deceased" individuals/persons, from one's Ancestral Lines, ALREADY existing, in the "Family Tree" Part, of 'FamilySearch', are discovered.
Use the "Find" facility/function/feature to Search, the "Family Tree" Part, of 'FamilySearch', one may be surprised to find some (if not, many) of them already there.
Many well established and documented (eg. "Sourced") individuals/person, in the "Family Tree" Part, of 'FamilySearch', have been RUINED, by the "Upload", of a GEDCOM File, into the "Family Tree" Part, of 'FamilySearch'.
I hope, that this puts things into perspective.
------------------
Furthermore ...
Here are just some very recent posts ...
Suggest An Idea
HOME > SUGGEST AN IDEA
[ 1 ]
STOP 🛑 allowing Gedcoms to be uploaded to the main tree
[ 2 ]
Gedcoms
https://community.familysearch.org/en/discussion/119229/gedcoms
[ 3 ]
Do a sanity check on GEDCOM, before allowing input to Family Tree
Now ...
That Said ...
GECOM Files, are NOT the only culprit ...
The "Synchronising", by some, of the "Third Party" Applications, that are "Certified" to work with the "Family Tree" Part, of 'FamilySearch', HAVE also caused many problems/issues, in the past.
One, notable, recent, example, is the occurrence(s) of such problems/issues, by/through "MyHeritage_com".
But ...
That Said ...
Over these MANY Years, without a doubt, the "Upload", of GEDCOM Files, into the "Family Tree" Part, of 'FamilySearch', is by far, seems to be the MOST "Destructive".
Oh; and, I agree, the ORIGINAL (ie. OLDEST) Record (ie. of an individual/person), in the "Family Tree" Part, of 'FamilySearch', SHOULD, be RETAINED; as, the "Surviving" record (ie. individual/person), in a "Merge"/"Combine".
Regardless, of how "Detailed", such Record (ie. of an individual/person) may be ...
ALL "Later"/"Subsequent" versions, SHOULD be SUBORDINATE, to the ORIGINAL (ie. OLDEST) Record (ie. of an individual/person).
Just my thoughts.
I know, that this certainly does not help/assist; but, I just want to let you know, that you are not alone.
Brett
2 -
There should be a way to keep your work safe and individualized if you want to.
That is the business model of Ancestry.com.
1 -
thank you @Brett .
0 -
😀
0
