Acceleration of the process when we add a gedcom to the family tree (detail in French)

LegacyUser

TEMPLE1 said: Lors de l'opération d'un Gedcom,nous arrivons "à comparer votre fichier Gedcom avec l'arbre familial".
La première opération "correspondances Possibles" se fait manuellement... ce qui est normal...
Toutefois la deuxième opération "Ajouter à l'arbre familial" devrait pouvoir se faire automatiquement et non manuellement.
Serait-il possible de programmer cette opération afin d'accélérer le processus.

LegacyUser

Jeff Wiseman said: Hello TEMPLE1, Welcome to the forum!

All postings here are read by FS employees, although they may or may not respond to them. Note that I am not an employee.

Although it would be possible to do what you suggest, in general it would not be desirable since it can introduce a lot of problems. Some examples:

1. The Possible matches function is not real solid and can miss possible duplicates. In general, automating this insertion of records from a GEDCOM file will create many duplicates in the system. For some examples see:
https://getsatisfaction.com/familysea...

2. If a person manually enters a single new record, the "possible matches" engine can pick up on that and find other possible matches on related records that it couldn't find previously. Automating the insertion of unmatched records would totally miss this new information.

3. In general, the GEDCOM compare tool is a significant problem. Many people would prefer for it to be removed from the system entirely due to the severe problems that it causes forcing other persons to have to fix many previously correct records. For a detailed discussion on this see:
https://getsatisfaction.com/familysea...

FS has informed us that due to problems with GEDCOMS, the current version of the GEDCOM compare tool has been specifically designed to try and "slow down" the transfer of data from a GEDCOM file into the Family Tree in order to mitigate issues. Since your suggestion runs contrary to that approach, FS may not be interested in providing that in the tool. Hopefully FS might provide a response to this.

LegacyUser

Tom Huber said: The bigger problem is that FamilySearch wants to avoid any duplicates in the massive database of over 1.2 Billion names. There are enough duplicates as it is from the records that were incorporated into what is now FamilySearch FamilyTree (FSFT).

IT does not take much for a user to find a connection between them and their ancestral lines. And, because the compare algorithm is basically "old and clunky" computer code, all FamilySearch has done to date is to try and retain the possibility of adding people to the existing line. Unfortunately, it doesn't take much for the system to look at the GEDCOM entry and not be able to find a corresponding person in FSFT.

There are better methods and one of them is to use one of the free versions of the three family tree management programs. Load your GEDCOM into one of those and then use the abilities of the free version to look at the existing persons in the massive tree. The three programs are in the Solutions Gallery and are Ancestral Quest, Legacy, and Roots Magic. Each program has its fans and when comparing or finding one or more existing people in the massive tree, do a much better job than the Compare function used by the GEDCOM system.

However, there is no automating adding all names not found. With the massive tree, shortcuts are never a good idea. Mistakes always occur, so working with your ancestral lines, because of the nature of the massive tree (which is designed to have just one record for each person who has lived) and its open-edit nature, adding duplicates is always a problem and users who have spent untold hours straightening out records are often very frustrated by additional and recently-added duplicate records.

LegacyUser

Tom Huber said: There is a link to the solutions gallery at the bottom of this and most FamilySearch pages.