Legacy 3 Deluxe (4 Jul 2001 build) Summary

Export

Legacy does not provide fields for LDS ordinance status information or for individual's roles in an event. This information was not entered in the first test file.

Data export problems:

Test GEDCOM 1.

This test was made with a Legacy version dated circa May 15, 2001.

The GEDCOM GEDCHK report found no syntax errors, two tag exceptions, and two extension tags. The tag exceptions included the following:

A DATE tag was out of context subordinated to a family note tag.
An illegal tag, COMM, was used for a note in the submitter information.

The two extension tags are:

_NAME. Found in the repository information and duplicates the regular NAME tag information.
_MEDI. MEDI is a legitimate tag and doesn't require the preceding underscore. In this instance it was used subordinate to the source tag. It should have been subordinate to the repository and call number tags.

Test GEDCOM 2.

Data export problems:

The GEDCOM GEDCHK report found no syntax errors, 18 tag exceptions, 3 tag extensions.

The tag exceptions were associated with two subordinate tags, Sealed to Spouse (SLGS) and Address of Individual (ADDR) and the COMM tag as it appeared in test one.

The three tag exceptions included the _NAME and _MEDI tags found in test one plus a _STAT tag which is legal without the preceding underscore.

Conclusion:

It appears the user in test 2 created a STAT tag in order to enter the LDS ordinance status information Legacy does not support. Of the tag exceptions, the COMM tag appears in both test files. In the case of the SLGS tag it would appear user entry technique might have caused the problem. EVEN, ANUL and ENGA tags had been subordinated along with their subordinate tags. User one successfully entered this same information. In the case of the Address information the program placed the tags in the wrong context.

All the three tag extensions are legal tags without the preceding underscore. Both the _STAT and _MEDI tags were both out of context in any case.
Based on the results of the first test file Legacy's GEDCOM export, assuming the data has been properly entered, should create few problems when imported to other programs.

Export rating: 98.10 %

GEDCOM imports:

Control GEDCOM

Legacy allows the user to map in unknown tags. On import the program did not indicate any tags as unrecognized.

Problems in the control file import of facts were as follows:

The data from several recognized tags did not transfer. They were:
Number of marriages (NMR)
Divorce information (DIV) Recorded as status and date. Place information was discarded.
Annulment (ANUL) also recorded as status with date only.
Number of children (NCHI)
LDS ordinance status (STAT) No fields are available for this information on the ordinance screen.
LDS fields available for Temple code but not for Temple location (This data is not really required).
Address information using the 5.5 address structure. (ADDR/ADR1/ADR2/CITY/STAE/POST/CTRY)
Physical description (DSCR)
Notes subordinate to repository information.
Source information relative to married name and nickname.
Source information subordinate to adoption tag (ADOP)

The following tags, all related to family events, transferred the basic information but failed to link sources, sureties, and citation notes.

Marriage banns (MARB)
Marriage license (MARL)
Divorce final decree (DIVF)
Engagement (ENGA)
Marriage settlement (MARL)
Marriage contract (MARC)

Transferred items requiring editing:

Information related to the use of the Associate tag. (ASSO)
Name suffix appeared in AKA with nickname.

Items using the Role tag (ROLE) appeared in the source detail comments.

Problems with source transfer:

All source information transferred properly. Some editing required was when the Gedcom source structure used the DATA tag and subordinate tags. In that instance, the subordinate tags were included in the publication data.

Summary:

With a few notable exceptions the problems found are related to tags not in common use. Minor editing will be required to assure information is the locations the user wants and to make sure notes word wrap as expected.

Import rating: 82.48 %

Legacy 3 Deluxe (4 Jul 2001 build) Summary

Export

Legacy does not provide fields for LDS ordinance status information or for individual's roles in an event. This information was not entered in the first test file.

Data export problems:

Test GEDCOM 1.

This test was made with a Legacy version dated circa May 15, 2001.

The GEDCOM GEDCHK report found no syntax errors, two tag exceptions, and two extension tags. The tag exceptions included the following:

A DATE tag was out of context subordinated to a family note tag.

An illegal tag, COMM, was used for a note in the submitter information.

The two extension tags are:

_NAME. Found in the repository information and duplicates the regular NAME tag information.

_MEDI. MEDI is a legitimate tag and doesn't require the preceding underscore. In this instance it was used subordinate to the source tag. It should have been subordinate to the repository and call number tags.

Test GEDCOM 2.

Data export problems:

The GEDCOM GEDCHK report found no syntax errors, 18 tag exceptions, 3 tag extensions.

The tag exceptions were associated with two subordinate tags, Sealed to Spouse (SLGS) and Address of Individual (ADDR) and the COMM tag as it appeared in test one.

The three tag exceptions included the _NAME and _MEDI tags found in test one plus a _STAT tag which is legal without the preceding underscore.

Conclusion:

Export rating: 98.10 %

GEDCOM imports:

Control GEDCOM

Legacy allows the user to map in unknown tags. On import the program did not indicate any tags as unrecognized.

Problems in the control file import of facts were as follows:

The data from several recognized tags did not transfer. They were:

Number of marriages (NMR)

Divorce information (DIV) Recorded as status and date. Place information was discarded.

Annulment (ANUL) also recorded as status with date only.

Number of children (NCHI)

LDS ordinance status (STAT) No fields are available for this information on the ordinance screen.

LDS fields available for Temple code but not for Temple location (This data is not really required).

Address information using the 5.5 address structure. (ADDR/ADR1/ADR2/CITY/STAE/POST/CTRY)

Physical description (DSCR)

Notes subordinate to repository information.

Source information relative to married name and nickname.

Source information subordinate to adoption tag (ADOP)

The following tags, all related to family events, transferred the basic information but failed to link sources, sureties, and citation notes.

Marriage banns (MARB)

Marriage license (MARL)

Divorce final decree (DIVF)

Engagement (ENGA)

Marriage settlement (MARL)

Marriage contract (MARC)

Transferred items requiring editing:

Information related to the use of the Associate tag. (ASSO)

Name suffix appeared in AKA with nickname.

Items using the Role tag (ROLE) appeared in the source detail comments.

Problems with source transfer:

All source information transferred properly. Some editing required was when the Gedcom source structure used the DATA tag and subordinate tags. In that instance, the subordinate tags were included in the publication data.

Summary:

With a few notable exceptions the problems found are related to tags not in common use. Minor editing will be required to assure information is the locations the user wants and to make sure notes word wrap as expected.

Import rating: 82.48 %