Looping into CETs from Recents
When I open the FamilySearch Tree to do some work, I usually go to the Recents to see where I left off working. I went to the list and clicked on the person I was working on. That took me to the person who had a warning notice that a GEDCOM file had errors. I began to think through the issue of someone adding a current GEDCOM to the FamilySearch Family Tree and clicked on the huge list of errors. I finally realized after returning to the FamilySearch Family Tree three or four times that I was going directly from the Recents to the CETs. I had gone to the person I was working on to make sure all the information was in the CETs. However, there was nothing telling me I had jumped to the CET unless I noticed the link in the left hand corner. In addition, the huge list of GEDCOM errors is about the most disincentive to use the CET that I can imagine. The "Errors" seem to be differences between the GEDCOM file and the FamilySearch Family Tree. So, do I spend hours and hours making sure the data is the same between my Ancestry.com GEDCOM file and the FamilySearch Family Tree or do I give up and ignore the CET for a while? I had to go through the loop about three or four times before I even realized what was happening. One option is to ignore the GEDCOM error list until and deal with the differences when there is a way to sync between the two trees. Just some observations. Apparently, the only way I can get to my recent person without jumping to the CET is by putting his ID number into the FIND option.
Kommentare
-
Added comment, when I try to go to the person using his ID # I automatically get sent to the CET anyway. I guess the only way to get to my most recent person now in the FamilySearch Tree is to click back until I reach this person.
0 -
Another comment, since the CETs doesn't yet show relationships, I can't use the person I am trying to reach to tell me how to click back six or seven generations and then down six or seven generations to find him. Fortunately, another family member of that remote relation was in the Recents and I could solve the issue. This makes the Recents function almost useless unless I stay in on version of the Family Tree and don't go back and forth.
0 -
@James Tanner - We made improvement to the stability of switching between trees. Are you seeing any improvements with this?
0
