Menu

Toolbar

Shortcut

Tools

-

Note: Married names can also be read from a second NAME tag if this has been specified in the Import Options under Handling of Special Gedcom Tags and Data. A married name from a second NAME tag overwrites any other married names from user-defined tags, from user-defined attributes or from user-defined tags in the family record.

Hint: To set the Gedcom converter to use the coding method of a specific genealogy program, start by determining whether the genealogy program is capable of managing married names and, if so, how they are coded. Export a test Gedcom file with the genealogy program that contains a test person with a defined additional married name in addition to a maiden name. This file will be opened in FamilyTreeFactory. Look at the display list of the individual record or of the family record to determine which method is used for coding. Based on the known names of the test person, you can easily determine which of the three methods shown in the dialog is correct. You can then specify the tag or the attribute type or the tags in the family record. The tag or the attribute type or the tags in the family record are then entered in the corresponding data field.

1.) Open the test Gedcom file and look for the individual record for Elisabeth Samplefam, born Samplemiss, in the list on the left (highlighted in yellow).

2.) In the individual record, look to see if the married name 'Samplefam' is shown separately or highlighted. This is the case in the line '2_MARNM Samplefam' (highlighted green). In this example, '_MARNM' is the tag. Another word could be in this position; only the structure is relevant. In general, user-defined tags usually start with an underline character so that they can be easily differentiated from Gedcom standard tags.

3.) Click on the button Change Gedcom Options... to open the dialog Gedcom Options. Select the Married Name Coding tab:

4.) Select the coding method of the three that contains the same structure of the married name as in the test Gedcom file. In this case, the method is user-defined tag. This is because there is a line '2 [entry field] Married Name1' with Married Name1 = married name (highlighted green). Now enter the tag in the entry field that was used in the test Gedcom file, in this case '_MARNM'.

5.) The method determined does not need to be defined for importing, as both methods are always used for importing.

6.) Click the button OK to save the Gedcom Options and close the dialog.

7.) In the converter dialog, click the button New Conversion.

8.) In the display list on the right for FamilyTreeFactory records, you can now see the names used in FamilyTreeFactory (highlighted blue): The surname is always the current/last surname. In this case, for Elisabeth Samplefam, born Samplemiss, the surname is the married name 'Samplefam'. The maiden name is marked accordingly.

1.) Open the test Gedcom file and look for the individual record for Elisabeth Samplefam, born Samplemiss, in the list on the left (highlighted in yellow).

2.) In the individual record, look to see if the married name 'Samplefam' is shown separately or highlighted. This is the case in the line '1 EVEN Samplefam', because the additional tag '2 TYPE MarriedName' is assigned (highlighted in green). The assignment is determined by the initial number being greater by 1: 2... is assigned to 1... In the line '2 TYPE MarriedName', 'MarriedName' refers to the married name type. Another word could be used here; only the structure is important. In Gedcom files, it is often the case that a TYPE tag is assigned to a tag in the next line that more closely describes the type of data. In this case, the TYPE tag with the words 'MarriedName' describes the word 'Samplefam' in the parent EVEN tag as a married name.

3.) Click on the button Change Gedcom Options... to open the dialog Gedcom Options. Select the Married Name Coding tab:

4.) Select the coding method of the three that contains the same structure of the married name as in the test Gedcom file. This is done with a line '1 EVEN...' and a second line '2 TYPE...'. In this case, the method is user-defined attribute. This is because there is a line '1 EVEN Married Name1' with Married Name1 = married name and a second line '2 TYPE [entry field]' (highlighted green). Now enter the type in the entry field that was used in the test Gedcom file, in this case 'MarriedName'.

5.) The method determined does not need to be defined for importing, as both methods are always used for importing.

6.) Click the button OK to save the Gedcom Options and close the dialog.

7.) In the converter dialog, click the button New Conversion.

8.) In the display list on the right for FamilyTreeFactory records, you can now see the names used in FamilyTreeFactory (highlighted blue): The surname is always the current/last surname. In this case, for Elisabeth Samplefam, born Samplemiss, the surname is the married name 'Samplefam'. The maiden name is marked accordingly.

1.) Open the test Gedcom file and look for the family record for the marriage of John Samplefam and Elisabeth Samplemiss in the center list (highlighted in yellow). As the names of the married couple are not directly named, searching for a specific couple in a large file can be difficult. If this is the case, look for the individual record of one spouse in the left list and double-click on the line '1 FAMS @...@' to display the referenced family record in the center list (highlighted in red '1 FAMS @F1@' ---> '0 @F1@)FAM'.

2.) In the family record, look to see if the married name 'Samplefam' is shown separately or highlighted. This is the case in the line '1 _NAMF Samplefam' (highlighted in green). In this example, '_NAMF' is the tag. Another word could be in this position; only the structure is relevant. In general, user-defined tags usually start with an underline character so that they can be easily differentiated from Gedcom standard tags.

3.) Click on the button Change Gedcom Options... to open the dialog Gedcom Options. Select the Married Name Coding tab:

4.) Select the coding method of the three that contains the same structure of the married name as in the test Gedcom file. In this case, the method is user-defined tags in the family record. This is because there is a line '1 [entry field] Married Name 2 (wife)' with Married Name 2 (wife) = married name (highlighted green). Now enter the tag in the entry field that was used in the test Gedcom file, in this case '_NAMF'.

5.) The method determined does not need to be defined for importing, as all methods are always used for importing.

6.) Click the button OK to save the Gedcom Options and close the dialog.

7.) In the converter dialog, click the button New Conversion.

8.) In the display list on the right for FamilyTreeFactory records, you can now see the names used in FamilyTreeFactory (highlighted blue): The surname is always the current/last surname. In this case, for Elisabeth Samplefam, born Samplemiss, the surname is the married name 'Samplefam'. The maiden name is marked accordingly.