GEDCOM UPLOADS - BAD IDEA BEYOND 4 GENERATIONS - TOO MANY DUPLICATIONS
When I originally uploaded my GEDCOM file, only a few "private" generations were allowed to be uploaded. Now it is a free for all. A GEDCOM file of only 4 generations should be allowed to be uploaded.
The amount of duplicates is getting worse. Incorrect information, last names, marriages, dates, etc.. are being uploaded with various dates and incorrect marriages or children and are creating very confusing duplications without primary sources attached to confirm and or to remove the incorrect information.
What a mess... and a waste of time for others.
While I understand that manually entering beyond 4 to 5 generations can seem to be time consuming, if the names are entered CORRECTLY, then a match will hopefully pop up.
This problem has gotten worse as more users sign on. It is especially prevalent in profiles from countries where a woman does not take on a husbands last name and last names are the child's father's primary last name and child's mothers last name... As in mine as an an example. Sainz is my father's, Wilson is my mother's. If one does not have to proper understanding of how to enter and of how these names are used including Baptismal names vs. Given names, it makes it extremely difficult to find family members when in fact they have been uploaded 20 times but incorrectly. This includes, Spain, Mexico, South American countries and many other additional countries of non non Spanish descendant.
Also this problem occurs in Welch and Scandinavian names where Verch/Ferch or "sson" or "dotter" is used. Because many are not familiar with how this was done, incorrect or correct duplications are being created. It's a mess!
Comments
-
I absolutely agree. I liked your use of "free for all." It has two meanings. It feels the not good way.
I research mostly Danish Records research which has Patronymic names. (Last name of child is the father's first name with sen or datter added. It is a method still used around the world and not just in Europe. ) I fix errors in family trees that are not my own, which I find from doing "project research". Recently, I worked on a Danish Family (not my own) that had a Gedcom which had so many errors starting at crossing and immigration. It had also been downloaded so many times that each person had up to 21 merges for each one. The family immigrating had 12 kids and each gen. above had high amounts too. And, each erroneous connection had to be fixed as well. I spent almost 2 months on the one family tree. Then went back and had to fix all the errors in the sources that had started to be connected. It started with them not understanding names.
I educate as I go and the family learned some good practices of putting in reason statements, and then adding them to the vitals. Unfortunately, everyone in well meaning when they upload their gedcom. But often there is also the same exact one loaded by the same person over and over too. There has to be a way to prevent that also.
Many mistakes could be prevented if everyone would use reason statements and create a life sketch, or even at minimum, put a critical vital record into it. This will alert to time, place, parents etc. But with Gedcom, or even picking up data from other sites and pulling it in, it brings lots of junk. Currently, the life sketch automatically opens partially and carries over in a merge. Even a record can alert there is a problem.
Limiting to 4 generations would at least make some of these problems smaller.
0 -
@Diana Raquel Sainz Wilson ( & @Anne888 )
Diana & Anne
'No', NOT even x4 Generations ...
Better still ...
I really wish 'FamilySearch' would ...
Just STOP allowing the "Upload" of GEDCOM Files into "Family Tree" of 'FamilySearch' altogether ...
There is just NO need to "Upload" of GEDCOM File into "Family Tree" of 'FamilySearch' ...
[ Under ANY circumstance, even if one's "Ancestral" Lines are NOT already in "Family Tree" of 'FamilySearch' ]
As I always 'say', to Users/Patrons, who mention the upload of GEDCOM Files into "Family Tree" of 'FamilySearch' ...
------------------
You can; but ...
Please DO NOT Upload a GEDCOM File into "Family Tree" of 'FamilySearch'.
Upload the GEDCOM Files in the "Genealogies" Part of 'FamilySearch', that is fine; but, please NOT into "Family Tree" of 'FamilySearch'.
Some of the reasons that Users/Patrons (like myself) DO NOT want the ability to upload a GEDCOM File into "Family Tree" of 'FamilySearch' are:
(1) It is most likely that individuals/persons in a GEDCOM File are ALREADY in "Family Tree" of 'FamilySearch'; and, most Users/Patrons DO NOT even take the time to look to see if any one 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 "Family Tree" 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 "Family Tree" of "FamilySearch", there is NO need to up 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 their 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, "Weeks") 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 "Family Tree" 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 "Family Tree" 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 "Family Tree" of 'FamilySearch"; BEFORE, some of the "Deceased" individuals/persons, from one's Ancestral Lines, ALREADY existing in "Family Tree" of 'FamilySearch', are discovered.
Use the "Find" facility/function/feature to Search "Family Tree" 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 "Family Tree" of 'FamilySearch' have been RUINED, by the upload, a GEDCOM File, into "Family Tree" of 'FamilySearch'.
I hope this puts things into perspective.
------------------
Just my thoughts.
Brett
2
