advertisement

This page describes a set of tests included in version 1.05 of the GEDCOM file assess.ged (download - view). Details change between versions.

Area Summary

People with the surname "Name" have names that help assess the name import method of the target application.

01-Primary Name with Type

This person's primary name record includes a TYPE NameBirth subrecord.

Some applications do not support the TYPE record under the NAME record. Some applications support the TYPE record, but only with a specific set of possible values. Some applications support the TYPE record, but only on non-primary names.

Test Result Criteria

  1. If a target application imports the NAME value into a name record and the TYPE value is used as the label for that record, set the test result to "Supported".
  2. For any other outcome, set the test result to "Imported Incorrectly" and describe the outcome in the comment.

GEDCOM Records for @I202@

1 NAME 01-Primary Name with Type /Name/
2 TYPE NameBirth

02-More than One Name

This person's record includes two names. The primary name should be "02-More than One Name Name". The additional name is "02-Additional Name".

Applications that support only a single name will reject or ignore one of the names.

According to the GEDCOM 5.5.1 specification, the first NAME record should be given preference. An application that supports a single name only must ignore the second NAME record, not the first.

For TMG to GEDCOM users, if the target application ignores the first NAME record or treats the second NAME record as primary, set the Names.Primary Tag Sequence property to "After non-primary (last)".

Test Result Criteria

  1. If a target application imports both NAME records and the first NAME record ("02-More than One Name Name") is chosen as the preferred or primary name, set the test result to "Supported".
  2. If a target application imports both NAME records and the second NAME record ("02-Additional Name") is chosen as the preferred or primary name, set the test result to "Imported Incorrectly" and describe the outcome in the comment.
  3. If a target application rejects the second NAME record with a message in its import log, set the test result to "Rejected".
  4. If a target application ignores the second NAME record, set the test result to "Ignored".
  5. For any other outcome, set the test result to "Imported Incorrectly" and describe the outcome in the comment.

GEDCOM Records for @I203@

1 NAME 02-More than One Name /Name/
1 NAME 02-Additional /Name/

03-Secondary Name with Type

This person's secondary name record includes a TYPE NameMarried subrecord. See the comments for 01-Primary Name with Type Name above.

Test Result Criteria

  1. If a target application imports both NAME records and the TYPE value is used as the label for the "03-Secondary Name" name, set the test result to "Supported".
  2. If a target application rejects the second NAME record with a message in its import log, set the test result to "Rejected".
  3. If a target application ignores the second NAME record, set the test result to "Ignored".
  4. For any other outcome, set the test result to "Imported Incorrectly" and describe the outcome in the comment.

GEDCOM Records for @I204@

1 NAME 03-Secondary Name with Type /Name/
1 NAME 03-Secondary /Name/
2 TYPE NameMarried

04-Name with Nickname

This person's name includes a nickname value, "Jack". The test is designed to reveal how the target application imports and renders names with nicknames.

The target application should assign the NICK value to a field of the imported name record. Alternatively, it may create an additional NAME record using the NICK value and (optionally) the SURN value.

Test Result Criteria

  1. If a target application imports the NICK value to a field of the primary name record, set the test result to "Supported".
  2. If a target application imports the NICK value and creates an additional altername name record with the given name set to the NICK value, set the test result to "Supported (w/comment)" and describe the outcome in the comment.
  3. If the target application imports the NICK value to a note field or some other field that is not designated for a name value, set the test result to "Imported Incorrectly".
  4. If a target application rejects the NICK record with a message in its import log, set the test result to "Rejected".
  5. If a target application ignores the NICK record, set the test result to "Ignored".
  6. For any other outcome, set the test result to "Imported Incorrectly" and describe the outcome in the comment.

GEDCOM Records for @I205@

1 NAME 04-Name with Nickname "Jack" /Name/
2 GIVN 04-Name with Nickname
2 NICK Jack
2 SURN Name

05-Name with Suffix

This person's name includes a suffix value, "Jr". The test is designed to reveal how the target application imports and renders names with suffixes.

Test Result Criteria

  1. If a target application imports the NAME value with the suffix value "Jr" in a suffix field or otherwise handled as a name suffix, set the test result to "Supported".
  2. For any other outcome, set the test result to "Imported Incorrectly" and describe the outcome in the comment.

GEDCOM Records for @I206@

1 NAME 05-Name with Suffix /Name/ Jr
2 GIVN 05-Name with Suffix
2 SURN Name
2 NSFX Jr

06-Name with Comma-Suffix (1)

This person's name includes a suffix value, "Jr". The test is designed to reveal how the target application imports and renders names with suffixes when the NAME record includes a comma before the suffix but the NSFX record omits the comma.

Test Result Criteria

  1. If a target application imports the NAME value with the value "Jr" or ", Jr" in a suffix field or otherwise handled as a name suffix, set the test result to "Supported (w/comment)" and include the exact suffix value in the comment.
  2. For any other outcome, set the test result to "Imported Incorrectly" and describe the outcome in the comment.

GEDCOM Records for @I207@

1 NAME 06-Name with Comma-Suffix (1) /Name/, Jr
2 GIVN 06-Name with Comma-Suffix (1)
2 SURN Name
2 NSFX Jr

07-Name with Comma-Suffix (2)

This person's name includes a suffix value, "Jr". The test is designed to reveal how the target application imports and renders names with suffixes when both the NAME record and the NSFX record include a comma before the suffix.

Test Result Criteria

  1. If a target application imports the NAME value with the value "Jr" or ", Jr" in a suffix field or otherwise handled as a name suffix, set the test result to "Supported (w/comment)" and include the exact suffix value in the comment.
  2. For any other outcome, set the test result to "Imported Incorrectly" and describe the outcome in the comment.

GEDCOM Records for @I208@

1 NAME 07-Name with Comma-Suffix (2) /Name/, Jr
2 GIVN 07-Name with Comma-Suffix (2)
2 SURN Name
2 NSFX , Jr

08-Name with Double @@

"@" characters have special meaning in GEDCOM and when used as data, the specification requires that they be doubled. This person's name includes "@@"". The test is designed to reveal if a target application handles the "@" character in a name.

Test Result Criteria

  1. If a target application imports the name and replaces the double "@@" with a single "@" character, set the test result to "Supported".
  2. For any other outcome, set the test result to "Imported Incorrectly" and describe the outcome in the comment.

GEDCOM Records for @I209@

1 NAME 08-Name with Double @@ /Name/

09-Primary Name with Memo

This person has a primary NAME with a NOTE value. The NOTE value is:

This is a note added to the primary name.

Test Result Criteria

  1. If a target application imports the name and the NOTE value is visible, set the test result to "Supported".
  2. For any other outcome, set the test result to "Imported Incorrectly" and describe the outcome in the comment.

GEDCOM Records for @I210@

1 NAME 09-Primary Name with Memo /Name/
2 NOTE This is a note added to the primary name.

10-Secondary Name with Memo

This person has a secondary NAME with a NOTE value. The NOTE value is:

This is a note added to the secondary name.

Test Result Criteria

  1. If a target application imports the secondary NAME record and the NOTE value is visible, set the test result to "Supported".
  2. For any other outcome, set the test result to "Imported Incorrectly" and describe the outcome in the comment.

GEDCOM Records for @I211@

1 NAME 10-Secondary Name with Memo /Name/
1 NAME 10-Additional /Name/
2 NOTE This is a note added to the secondary name.
On This Page