#355 GedMerge v0.7 - Merge GEDCOM files

[Greg Roach]

Anyone who has merged two gedcom files will know that
it is a slow and error-prone tasks. This module allows
a site administrator to merge (import) the indi/fam
facts from one gedcom into another. It automates the
entire process, leaving the user to simply confirm each
step.

The whole process is incremental, so you can stop at
any time and when you restart it will resume where you
left off. It also means that if you make a small
change in your import gedcom, then the next time you
import it you will only have to process the changes,
not the whole file.

It works by using the _UID tags to identify objects
that are the same in both files. These are copied
between gedcoms or created if not already present.

From each pair of matched objects, it tries to match
further objects using the FAMS/FAMC relationships. For
example if main gedcom has person X married to person
Y1 and the import gedcom has person X married to person
Y2, then there are two options: Y1 and Y2 are the same
person (so match them) or they are different persons
(so import Y2 into the main gedcom). Simply click on
the appropriate option. The "most likely" option is
generally the one at the top of the list.

(NB it is possible here that person Y2 should in fact
be married to someone completely different. If you
find a "structural" difference between the gedcoms, you
will need to stop and fix it before continuing.)

For each pair of matched objects, a "smart import"
process is then used that will import only facts that
are not already present. There is a degree of
intelligence built in, so that if you already have

1 DEAT
2 DATE 21 JAN 1900
3 PLAC Westminster, London, England

The system won't import any of these:

1 DEAT Y

1 DEAT
2 DATE ABT 1900

1 DEAT
2 PLAC Westminster

All imported facts are "tagged" with the same source
record, allowing you to easily identify and review them
after the import.

Note that there is no "undo" facility (it doesn't
currently work with the accept/reject mechanism), so
make a backup before you start :-)

[Julio Sánchez Fernández]

GEDCOM selection has changed. Global $GEDCOM is no more and find_gedcom_record wants the GEDCOM internal ID as a second argument. So gedmerge has stopped working again.

[janpolsen]

Adding more info about Julio's comment:

ERROR 2: Missing argument 2 for find_gedcom_record(), called in /var/www/genes.dk/public_html/gedmerge.php on line 41 and defined
0 Error occurred on line 1000 of file functions_db.php in function find_gedcom_record
1 called from line 41 of file gedmerge.php in function lfetch_gedcom_record
2 called from line 51 of file gedmerge.php in function url_of_object
3 called from line 407 of file gedmerge.php

Warning: Missing argument 2 for find_gedcom_record(), called in /var/www/genes.dk/public_html/gedmerge.php on line 41 and defined in /var/www/genes.dk/public_html/includes/functions/functions_db.php on line 1000

ERROR 8: Undefined variable: ged_id
0 Error occurred on line 1022 of file functions_db.php in function find_gedcom_record
1 called from line 41 of file gedmerge.php in function lfetch_gedcom_record
2 called from line 51 of file gedmerge.php in function url_of_object
3 called from line 407 of file gedmerge.php