* Merge/Compare GEDCOM files

[jsnyder]

I have found a GEDCOM file that can possibly add many individuals to my current project and add substandial detail to current individuals. Being relatively new to FH and before comparing and merging a new file of 1300 individuals with the current project of nearly 1000, I want to get a better understanding of now the Merge/Compare File feature works. I have read FH Help and user manual and am puzzled why I see some records and fields treated unexpectedly when experimenting with the Chapter 15 Tutorial. I hope my questions are clear.

For example, when I merge files 15a and 15b the records for Sarah Marie Watts show “Null Merge,” which, according to the manual, means “the 2 records are identical or the new one is a subset of the current one.” But the new record under the Spouse family shows Ian Robert Peabody on a different line than the current Ian Peabody, which the manual says is “because they do not match.” If they don’t match, why is the record Action “Null Merge”? If it has something to do with Subset, then I would benefit from a better explanation of how merge/compare works with subsets. I am confused, for all but the highest level fields have subordinate fields, which, I gather, are subsets.

Also, why is there no “Y” under the R+ column? After all, the manual says “Y in the R+ column means that the record or field branch ... contains data that is only to be found in the new file.” I also wonder why “Durban, South Africa” in the birthplace field is not struck-out, given that the birth date and other identical fields are struck-out.

Merge-Compare screenshot-7.jpg (174.54 KiB) Viewed 3679 times

There may be straightforward logic why things don’t appear as it seems they should, but misunderstanding how Merge/Compare works could lead to unanticipated results and possibly waste considerable time when sorting through hundreds of records. Thank you for any clarification.

[tatewise]

I cannot explain why the Place details are not struck out. That looks like a mistake.

However, I can throw some light on your other points.
The key is to understand the record structure, and the difference between subordinate fields, and subordinate records.
Each Individual and each Family have a separate record, and the Merge/Compare focusses on one Record at a time.
The Sarah Marie WATTS Individual record subordinate fields are those shown in blue directly below her Name.
Wherever the right-hand column starts with a box, then that indicates a link to a subordinate record, and the colour changes to brown.
If there is then a link to another subordinate record the colour changes back to blue, and so on for each generation.
e.g.
...with Cameron PEABODY
Cameron PEABODY (1901-bef1979) [1]
Amanda PEABODY ( - ) [3]

You would need to switch to these other Records to see Y in the R+ column, because the details are not held in the Sarah Marie WATTS record fields.

[jsnyder]

Thank you for clarifying these points. Although it probably should have been obvious to me, your explanation of the color changes was the first I had read of this part of the Merge/Compare feature. I think I’m getting a better understanding of what happens when two files are compared/matched. This leads to a couple questions regarding terminology:

1. Is your “subordinate record” the same as the user manual’s “subset” and your “subordinate field” is the the same as the manual’s “field branch” and FH Help’s “child field”?

2. I gather that the Information pane’s hierarchical structure shows how merging will work. So, if a subordinate record in the New Record pane (e.g. Amanda PEABODY (-) [3]) is merged with the matched record in the Current Record pane is it true that “Null Merge” refers solely to the primary record (e.g. Sara Marie WATTS) and one subordinate field below the primary (e.g. Name, Sex, Spouse Family, etc.) and not to its secondary (and below) subordinate fields? Therefore, is it also true that each secondary (and below) subordinate record is matched independently (i.e. “matched rec” in the Information pane), has its own score, and must be examined outside the primary record?

I think it's starting to sink in but it will take time to better understand when and how records and fields are merged and when “Null Merge” and “All” terms apply.

[tatewise]

1. Subordinate record is not the same as subset. Subset means the New Record has less data than the Current Record, but the data that does exist matches. Subordinate fields are as you say.

2. Your understanding is almost perfect. Subsidiary fields are all the top blue fields but may be several levels. Subsidiary records change to brown, and as you say are matched separately.