Can I upload a gedcom file?
Answers
-
chances are very high - most of the people in your GEDCOM are already in FamilySearch Family Tree - you simply need to establish a few links from you to them.
see: https://community.familysearch.org/s/feed/0D53A00004skwTTSAY
0 -
@Gates/Adams/Williams Gates/Adams/Williams
.
You can; but ...
.
Please DO NOT upload a GEDCOM File in "Family Tree" of 'FamilySearch'.
.
Upload GEDCOM File 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") 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 most probably ALREADY exist in "Family Tree" of 'FamilySearch'.
.
Only one or two of one's generations of "Living" Family members (and, perhaps one or two of one's generations of "Deceased" Family members) may be required to be entered/input in "Family Tree" of 'FamilySearch'; before, some of the "Deceased" individuals/persons from Ancestral lines ALREADY existing in "Family Tree" of 'FamilySearch', are discovered.
.
Use the "Find" facility/function/feature to Search "Family Tree" of 'FamilySearch', you 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'.
.
Of course, IF, one has looked in "Family Tree" of 'FamilySearch' and NONE of one's Ancestral lines are in "Family Tree" of 'FamilySearch'; THEN, the upload of a GEDCOM File would be the way to go - BUT, ONLY if one has looked in "Family Tree" of 'FamilySearch' and NONE of one's Ancestral lines are in "Family Tree" of 'FamilySearch'
.
I hope this puts things into perspective.
.
Brett
.
0
