{"id":294,"date":"2020-02-11T15:13:30","date_gmt":"2020-02-11T15:13:30","guid":{"rendered":"https:\/\/fhug.org.uk\/kb\/?post_type=kb_article&#038;p=294"},"modified":"2021-04-12T07:02:27","modified_gmt":"2021-04-12T07:02:27","slug":"merge-compare-file","status":"publish","type":"kb_article","link":"https:\/\/www.fhug.org.uk\/kb\/kb-article\/merge-compare-file\/","title":{"rendered":"Merge\/Compare File"},"content":{"rendered":"<h2 id=\"introduction\" class=\"sectionedit2\">Introduction<\/h2>\n<div class=\"level2\">\n<p>For Family Historian the files being merged are Gedcoms which have an extension of .ged e.g. myfile.ged<\/p>\n<p>Merging in another Gedcom is an excellent way of bringing in numerous records without having to type them in manually.<\/p>\n<p>You may have received this Gedcom from another researcher, or have downloaded it from somewhere like Worldconnect, or FamilySearch, etc.<\/p>\n<p>However, merging without a prior comparison may bring unforeseen consequences to the point where you may end up with an unusable Project. For this reason, like many other processes and tasks, it is strongly recommended that you back up your main Project first.<\/p>\n<p>You may wish to create a couple of small Projects and experiment with them. The procedure for this could be to make a small Project, either manually or through use of the <a href=\"https:\/\/fhug.org.uk\/kb\/kb-article\/split-tree-helper\/\">Split Tree Helper<\/a>, save it, and then copy it under a different name. Edit one of the Projects by adding, removing and amending people and data and then save it again.<\/p>\n<\/div>\n<h2 id=\"merge_compare_procedure\" class=\"sectionedit3\">Merge\/Compare Procedure<\/h2>\n<div class=\"level2\">\n<p>Note below is a suggestion on how to work this process. You may find a way to go through the compare better suited to your needs.<\/p>\n<ul>\n<li class=\"level1\">\n<div class=\"li\">Prior to a merge, backup your current master Project using <a href=\"#!\" class=\"cs_tooltip\" fhugtt=\"This is the menu across the top of the main Family Historian windows. The &gt; denotes a submenu\">File&nbsp&gt;&nbspBackup\/Restore<\/a> or <a href=\"#!\" class=\"cs_tooltip\" fhugtt=\"This is the menu across the top of the main Family Historian windows. The &gt; denotes a submenu\">File&nbsp&gt;&nbspProject&nbspWindow&nbsp&gt;&nbspMore&nbspTasks&nbsp&gt;&nbspCopy&nbspProject<\/a>.<\/div>\n<\/li>\n<\/ul>\n<ul>\n<li class=\"level1\">\n<div class=\"li\">Make a copy of the new GEDCOM file outside of Family Historian (e.g. using Windows Explorer).<\/div>\n<\/li>\n<\/ul>\n<ul>\n<li class=\"level1 node\">\n<div class=\"li\">Import the new file into a temporary new Project and use <a href=\"#!\" class=\"cs_tooltip\" fhugtt=\"This is the menu across the top of the main Family Historian windows. The &gt; denotes a submenu\">File&nbsp&gt;&nbspValidate&#8230;<\/a> to\u00a0 validate it. This may occur automatically. Any import errors such as UDF may need to be fixed.<\/div>\n<ul>\n<li class=\"level2\">\n<div class=\"li\">Tip: If you have standardised your place names on your Projects, you may like to take this opportunity to amend the place names on the new Project to fit in with your standard.<\/div>\n<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<ul>\n<li class=\"level1\">\n<div class=\"li\">If this new Project contains branches on it you do not want, delete them now. This can be done manually, but the <a href=\"https:\/\/fhug.org.uk\/kb\/kb-article\/split-tree-helper\/\">Split Tree Helper<\/a> will be a better method as any unassociated data can be removed.<\/div>\n<\/li>\n<\/ul>\n<ul>\n<li class=\"level1\">\n<div class=\"li\">Open your current master Project.<\/div>\n<\/li>\n<\/ul>\n<ul>\n<li class=\"level1\">\n<div class=\"li\">Go to <a href=\"#!\" class=\"cs_tooltip\" fhugtt=\"This is the menu across the top of the main Family Historian windows. The &gt; denotes a submenu\">File&nbsp&gt;&nbspMerge\/Compare&nbspFile<\/a>, then Open the new Project&#8217;s GEDCOM file from within its <code>.fh_data<\/code> sub-folder.<\/div>\n<\/li>\n<\/ul>\n<ul>\n<li class=\"level1 node\">\n<div class=\"li\">You will see three related lists in the new window (you may wish to maximise this window):<\/div>\n<ul>\n<li class=\"level2\">\n<div class=\"li\">An information pane which shows actions to be applied to either or both of the other lists.<\/div>\n<\/li>\n<li class=\"level2\">\n<div class=\"li\">A list showing details of the current file.<\/div>\n<\/li>\n<li class=\"level2\">\n<div class=\"li\">A list showing details of the new file.<\/div>\n<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<ul>\n<li class=\"level1\">\n<div class=\"li\">This is the comparison and it occurs immediately prior to the actual merge. You are not forced to compare, you can go straight into the merge, but you will need to tidy up afterwards probably.<\/div>\n<\/li>\n<\/ul>\n<ul>\n<li class=\"level1\">\n<div class=\"li\">For now just concentrate on the Action, Match Score and Chk columns in the first list. The other columns give an indication where there is data that will either be retained or discarded which will be of help once the basics have been grasped.<\/div>\n<\/li>\n<\/ul>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-11289 size-full lazyload\" data-src=\"https:\/\/fhug.org.uk\/kb\/wp-content\/uploads\/2020\/02\/mergea.jpg\" alt=\"\" width=\"478\" height=\"316\" data-srcset=\"https:\/\/www.fhug.org.uk\/kb\/wp-content\/uploads\/2020\/02\/mergea.jpg 478w, https:\/\/www.fhug.org.uk\/kb\/wp-content\/uploads\/2020\/02\/mergea-300x198.jpg 300w, https:\/\/www.fhug.org.uk\/kb\/wp-content\/uploads\/2020\/02\/mergea-150x99.jpg 150w\" data-sizes=\"(max-width: 478px) 100vw, 478px\" src=\"data:image\/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==\" style=\"--smush-placeholder-width: 478px; --smush-placeholder-aspect-ratio: 478\/316;\" \/><\/p>\n<ul>\n<li class=\"level1 node\">\n<div class=\"li\">Sort by Score by double clicking the column heading.<\/div>\n<ul>\n<li class=\"level2\">\n<div class=\"li\">Tip: The higher the Score the more likely the match &#8211; more details are the same. However just because there is a score does not mean the records are right to be merged e.g. namesakes will match.<\/div>\n<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<ul>\n<li class=\"level1\">\n<div class=\"li\">Open out the first record, through the + by the side of the name and see what the difference is between the records. Decide whether to Keep or Discard the contained pieces of information by using the appropriate button.<\/div>\n<\/li>\n<\/ul>\n<ul>\n<li class=\"level1\">\n<div class=\"li\">If you hit the wrong button do not worry, just hit the button you wanted and the Keep\/Discard will change.<\/div>\n<\/li>\n<\/ul>\n<ul>\n<li class=\"level1\">\n<div class=\"li\">You may see unusual records in the new file. These are common in files created by other applications and can be identified and removed easily later (so don&#8217;t bother now).<\/div>\n<\/li>\n<\/ul>\n<ul>\n<li class=\"level1\">\n<div class=\"li\">When you are happy that you have done all you can on that record, click on the name in both the Current and New Records list and then click on the the Check button at the bottom of the window. You will see a Y in the Chk column.<\/div>\n<\/li>\n<\/ul>\n<ul>\n<li class=\"level1\">\n<div class=\"li\">Continue through the file and don&#8217;t be afraid to continually sort by different criteria. As you&#8217;ve checked the records you&#8217;ve already done, you won&#8217;t lose them.<\/div>\n<\/li>\n<\/ul>\n<ul>\n<li class=\"level1\">\n<div class=\"li\">If you can see that two names ought to match click on the name in the current window, and with the control key pressed, click on the name in the new window and then use the Match button.<\/div>\n<\/li>\n<\/ul>\n<ul>\n<li class=\"level1\">\n<div class=\"li\">If you see that two names are matched that should not be, do the same but use the Unmatch button.<\/div>\n<\/li>\n<\/ul>\n<ul>\n<li class=\"level1\">\n<div class=\"li\">Do not be afraid to sort other columns. It is especially useful to sort the new names column to see where there are no matches and it becomes apparent to you where you have missed data.<\/div>\n<\/li>\n<\/ul>\n<ul>\n<li class=\"level1\">\n<div class=\"li\">There is no halfway house unfortunately so if you are going to merge a large file be prepared for a long task.<\/div>\n<\/li>\n<\/ul>\n<ul>\n<li class=\"level1\">\n<div class=\"li\">Having completed the <em>Individuals <\/em>tab, move on to the <em>Families<\/em> tab and repeat the process, then the <em>Notes <\/em>tab, and so on until all tabs have been merged. A <em class=\"u\">VERY COMMON MISTAKE<\/em> is to ignore most of the tabs.<\/div>\n<\/li>\n<\/ul>\n<ul>\n<li class=\"level1\">\n<div class=\"li\">When you are happy that you have done all you can press the <em>Merge <\/em>button.<\/div>\n<\/li>\n<\/ul>\n<ul>\n<li class=\"level1\">\n<div class=\"li\">If you have not checked all the records you will be prompted to confirm that it is ok to go ahead.<\/div>\n<\/li>\n<\/ul>\n<ul>\n<li class=\"level1\">\n<div class=\"li\">You will the be asked if you wish to create a new source for the merge. This is worthwhile and there are various options on how to link the records or to confirm records that, for example, you and your fellow researcher have independently found.<\/div>\n<\/li>\n<\/ul>\n<ul>\n<li class=\"level1\">\n<div class=\"li\">Eventually, when everything is satisfactory, you can delete the temporary new Project created originally.<\/div>\n<\/li>\n<\/ul>\n<\/div>\n<h2 id=\"common_problems\" class=\"sectionedit4\">Common Problems<\/h2>\n<div class=\"level3\">\n<ul>\n<li class=\"level1 node\">\n<div class=\"li\">Records that should not have been matched, have been.<\/div>\n<ul>\n<li class=\"level2\">\n<div class=\"li\">This often manifests itself by people having more than one set of parents. Identify the incorrect link, go to the <em>All <\/em>tab for that <em>Individual <\/em>and clear the link. Thereafter link the person then to the correct place. See <a href=\"https:\/\/fhug.org.uk\/kb\/kb-article\/correcting-duplicate-spouses-families\/\">Correcting Duplicate Spouses\/Families<\/a> and <a href=\"https:\/\/fhug.org.uk\/kb\/kb-article\/removing-unwanted-relations\/\">Removing Unwanted Relations<\/a>.<\/div>\n<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<ul>\n<li class=\"level1 node\">\n<div class=\"li\">Records that should have been matched, have not.<\/div>\n<ul>\n<li class=\"level2\">\n<div class=\"li\">These will appear as duplicates on your file, and in Diagrams there will coloured ribbons connecting them. Identify the duplicate records and merge. A common cause is forgetting to merge all the tabs.<\/div>\n<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<ul>\n<li class=\"level1 node\">\n<div class=\"li\">Data, such as names, have been kept, such as Alternate Names or dates.<\/div>\n<ul>\n<li class=\"level2\">\n<div class=\"li\">These can be identified through running a Query.<\/div>\n<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<ul>\n<li class=\"level1 node\">\n<div class=\"li\">Unrecognised data has appeared (UDF).<\/div>\n<ul>\n<li class=\"level2\">\n<div class=\"li\">This may be Uncategorised Data. These are data items that Family Historian cannot recognise. See <a href=\"https:\/\/fhug.org.uk\/kb\/kb-article\/handling-uncategorised-data-fields\/\">Handling Uncategorised Data Fields (UDF)<\/a>. These can be removed through putting them in a Named List using the Find Uncategorised Data option in the Tools menu and then removing, or converting the data to valid fields, or using the V5+ <a href=\"https:\/\/pluginstore.family-historian.co.uk\/page\/plugin\/udf-list\">UDF List<\/a> Plugin.<\/div>\n<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<ul>\n<li class=\"level1 node\">\n<div class=\"li\">Names, especially from FamilySearch, are in upper case.<\/div>\n<ul>\n<li class=\"level2\">\n<div class=\"li\">V4 or below: Nothing you can do bar editing the file record by record or by using a text editor<\/div>\n<\/li>\n<li class=\"level2\">\n<div class=\"li\">V5 or above: Use the <a href=\"https:\/\/pluginstore.family-historian.co.uk\/page\/plugin\/clean-up-surname-capitalisation\">Clean up Surname Capitalisation<\/a> Plugin<\/div>\n<\/li>\n<\/ul>\n<\/li>\n<li class=\"level2\">\n<div class=\"li\">\n<div class=\"li\">The file you have been sent is not a Gedcom but is specific to another genealogy application.<\/div>\n<ul>\n<li class=\"level2\">\n<div class=\"li\">Common file types are .paf Personal Ancestral File, .FTM or .FTW Family Tree Maker. These need to be converted to Gedcom prior to import, which will require the original program that created the file to perform the conversion. If you cannot find a method of doing this, the best thing is to politely request the info as a Gedcom. Ask the person who sent the data to look for an Export option on their program, or else beg on the <abbr title=\"\" data-original-title=\"Family Historian Users Group\">FHUG<\/abbr> forum or <abbr title=\"\" data-original-title=\"Family Historian\">FH<\/abbr> Rootsweb and hope someone has the creating software.<\/div>\n<\/li>\n<li class=\"level2\">\n<div class=\"li\">Also see <a href=\"https:\/\/fhug.org.uk\/kb\/kb-article\/importing-to-family-historian\/\">Importing to Family Historian<\/a>.<\/div>\n<\/li>\n<\/ul>\n<\/div>\n<\/li>\n<\/ul>\n<ul>\n<li class=\"level1 node\">\n<div class=\"li\">Warning message: &#8220;<em>The file you have selected to merge\/compare with the current file contains media, and has not been saved since it was moved or copied from its previous location.<\/em>&#8221; etc\u2026<\/div>\n<ul>\n<li class=\"level2\">V4 or above: Ignore the warning but ensure both Projects\/Gedcom are fully backed up.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/div>\n","protected":false},"template":"","fh_version":[13,14,15,739],"skill_level":[17],"topic":[725,58,105],"class_list":["post-294","kb_article","type-kb_article","status-publish","hentry","fh_version-v4","fh_version-v5","fh_version-v6","fh_version-v7","skill_level-intermediate","topic-importing","topic-importing-and-exporting","topic-merging-and-splitting-trees"],"_links":{"self":[{"href":"https:\/\/www.fhug.org.uk\/kb\/wp-json\/wp\/v2\/kb_article\/294","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.fhug.org.uk\/kb\/wp-json\/wp\/v2\/kb_article"}],"about":[{"href":"https:\/\/www.fhug.org.uk\/kb\/wp-json\/wp\/v2\/types\/kb_article"}],"wp:attachment":[{"href":"https:\/\/www.fhug.org.uk\/kb\/wp-json\/wp\/v2\/media?parent=294"}],"wp:term":[{"taxonomy":"fh_version","embeddable":true,"href":"https:\/\/www.fhug.org.uk\/kb\/wp-json\/wp\/v2\/fh_version?post=294"},{"taxonomy":"skill_level","embeddable":true,"href":"https:\/\/www.fhug.org.uk\/kb\/wp-json\/wp\/v2\/skill_level?post=294"},{"taxonomy":"topic","embeddable":true,"href":"https:\/\/www.fhug.org.uk\/kb\/wp-json\/wp\/v2\/topic?post=294"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}