Allow user to enter ID of person in family tree when comparing GEDCOM person to FT person
Comments
-
This "Feedback" seems like a good idea to myself. I have an ancestor that has been in the FamilySearch "Family Tree" since day one, and now in my comparing GEDCOM process it wants me to add her to the "Family Tree" just because of one day difference in her death. See the screen shots below.
0 -
Don
Not so much in relation the the suggested enhancement ..
As an aside ...
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 User/Patrons, who mention the "Upload" of GEDCOM File 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, "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 "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
0 -
I agree with you Brett.
I had entered a file to GENEALOGIES in 2019. I did not compare the GEDCOM file in 2019. Wanting to be more obedient in complying to FamilySearch demands, I decided to hit on the GEDCOM compare process. BIG MISTAKE, because I added a person to the "Family Tree" only to find out later that the person did not need to be added, but her husband needed to be merged with a duplicate. Disobedient or not, I am going to hold off on the compare GEDCOM process in Genealogies.
0 -
Don
Sounds good.
Yep ...
As I already advised ...
I really wish, 'FamilySearch', would just STOP allowing, the "Upload" of GEDCOM Files, into "Family Tree" of 'FamilySearch' altogether, there is just NO need whatsoever.
There HAS been (in the past); and, there STILL is (currently); and, there will be (in the future), far too much, DAMAGE, being done to the EXISTING individuals/persons, in "Family Tree" of 'FamilySearch', with the "Upload" of GEDCOM Files, into "Family Tree" of 'FamilySearch'.
But ...
That Said ...
Such DOES NOT appear, to be considered, as such, by 'FamilySearch'.
There have been, COUNTLESS requests, by Participants (ie. Users/Patrons), to STOP allowing, the "Upload" of GEDCOM Files, into "Family Tree" of 'FamilySearch' altogether.
[ As, you will well be aware; even, from the OLD "GetSatisfaction" Days ]
The requests, by Participants (ie. Users/Patrons), to STOP allowing, the "Upload" of GEDCOM Files, into "Family Tree" of 'FamilySearch' altogether, just seem to be 'falling on deaf ears' ... a real shame.
Brett
0
