Why has family search deleted my grandmother?
I am in despair at what has happened through uploading my tree from ancestry to Family Search.
I have just wasted 3 hours adding people singly at your request but have looked at the tree to find it a half empty fragmented mess
My own grandmother has been deleted Amy Jackson
There are not enough clear instructions as to how to reduce a large tree to something digestible for Family Search I know it was a risk uploading 5,900 names but no comprehensible alternative was offered.
Then I am abandoned to old discussions which do not address the problem. Why no chat or phone help for most Europeans? Britain has virtually no support that I can find.
I accept that there were errors in 450 cases and that these names should be rejected until rectified ...but there was no facility offered for editing these.
Then I am faced with 3500 manual additions to be part of this community ...harsh ! and not realistic. There may be something I am missing in all of this.
For starters, I need a person please to tell me what happened to my well documtened Granny!
Julia Szent-Györgyi ✭✭✭✭✭
@cynthiagrannon1, it sounds like to me that in your efforts to transfer your work between sites, you missed an extremely crucial detail:
FamilySearch's communal Family Tree is nothing like the individual trees on Ancestry.
It's a completely different mindset: instead of each person entering a new tree, with other people maybe able to look at it or copy from it, on FamilySearch it's all one tree, and nobody can claim ownership of any profiles for deceased people. It's all a collaborative effort.
The other thing that you need to understand is less well-known, except to us regulars on FS's forums: the GEDCOM import process on FamilySearch is ...disfunctional. Even when it looks to the user like it's functioning, what it dumps into Family Tree is a chaotic mess, and it constantly asks the user to make decisions based on incomplete information. In my experience, it fails equally badly regardless of the size of the file, but limiting the size makes it easier for the user to assess and fix the failures. That is, limiting the number of people in your import doesn't change much on the computer end, but it helps greatly on the human end of the problem.
My suggestion is to skip FS's import process entirely. You can upload your file (or leave it uploaded), but do not use the "add to tree" function. Your file will be searchable and viewable in the Genealogies section, so you and all your cousins can access your work, but nobody will be able to change anything in it (except that you can delete your file and/or upload a new one at any time).
Instead of FS's process, I suggest you try one of the offline genealogy programs that can fully interface with FamilySearch. Legacy, Ancestral Quest, and Roots Magic are the three that I remember, but check the Solutions Gallery. The three I mentioned all have free versions. (Last I checked, Legacy still didn't support Unicode, so if you have relatives any further east than France, I would avoid it, because it will mangle characters like ő (not ö) and č.)0
In looking at the ID G7K5-BBQ for Amy Jackson I see that her parents are Albert William James Foster and Elizabeth Sleep. This would indicate that Amy's maiden name is Foster. Her married name is Jackson from her second marriage. I see a possible duplicate for Amy Foster LD4Z-BGM that probably needs to be merged with G7K5-BBQ see this link https://www.ancestry.co.uk/family-tree/person/tree/64761167/person/44127880186/facts
Please review all the sources for Amy, her parents and her husbands and children. I think that if you do good detective work you will be able to resolve this issue. As a reminder The women need to be listed with their maiden name. Try changing Amy's last name to Foster in FamilySearch and you will probably receive some additional information.
Hopefully this will help.0
Just uploading your Family Tree from Ancestry.com does not copy your information into the FamilySearch Family Tree. To avoid creating duplicate records for individuals who are already part of Family Tree, you must compare and then review each name in your GEDCOM submission that is not a living person. You can copy any new information into Family Tree as described in the knowledge article we have provided below. Living people cannot be added through a GEDCOM but must be added manually.
Please review each step of the process described in the article so you can simply copy new records of deceased individuals.
We believe you may find many of your ancestors are already part of Family Tree which will help to minimize extra work.1
Related recent posts ...
[ 1 ]
"Q and A" Section
'Category' = FamilySearch Community
Home > Help Center Categories > FamilySearch Community
Uploading of my family tree only partial.
[ 2 ]
"Ideas" (ie. 'Feeback') Section
'Topic' = General User Interface
Home > Ideas > General User Interface
Uploading a gedcom should populate the family tree on a user's account
I am faced with adding 3500 names one by one after the site has accepted 2400. I'm not sure that I can face this! What a shame. I love the site but it has not made allowances for this kind of volume. Pity :(
. <<You can copy any new information into Family Tree as described in the knowledge article we have provided below.>>
Whichever away I read it looks like I have to do this 3,500 times since 2,500 have been accepted as already in the FS tree0
Thanks for taking the time to look at this for me. I am beginning to adust. I do now use the maiden name for wives, but my grandmother's entry was an early one. I am currently going through my Ancestry .co.uk tree and majorly tidying up and merging duplicates. It being a large tree I had forgotten how much less I knew when I began.4,500 entries ago.
Once done I will try to apply the tree in sections using Roots Magic as interface/intermediary.
What in heaven's name has happened to the best ancestor site ever? Little works now! Is FS in the process of redesigning the features? I keep most of my common search targets bookmarked. Now nothing works. I am boomfuzzled.0