Family Origins 9 Summary

Export

Data export problems:

Test GEDCOM 1

The GEDCOM GEDCHK report found no syntax errors, 16 tag exceptions, and 3 extension tags.

All the tag exceptions were as a result of the illegal use of the CONT tag with a superior PAGE tag when exporting source citations. This means the citation information could be truncated when importing the Gedcom file to another program. This is one of those ill defined items in the Gedcom specification. No deductions were made for this problem.

The 3 tag extensions are _SCBK, _PRIM, _TYPE and are all used in connection with linked object (OBJE) information. The failure of an importing program to read these tags would cause no data loss.

Conclusion:

With the exception of possible citation data loss all other recorded data should transfer properly. When importing a Family Origins Gedcom file the user should use a text editor to search for PAGE tags to determine if any information has not transferred.

Export rating: 100 %

GEDCOM imports:

Control GEDCOM

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

Family Origins did not recognize the following tags but recorded the information to the exception list.

Address (ADDR) information subordinated to the residence (RESI) tag was not recognized and placed in the exception list.

The submitter family file information (SUBN) was placed in the exception list. This information is not required for non church transfers.

Family origins did not recognize the following tags and did not place the data in the exception list (data lost)

Family Origins recognizes only one name per individual. Any information attached to a second use of NAME tag under one individual will be lost.

A note at the 0 (zero) level transferred only the reference number. The note contents would have to be recovered from the original Gedcom file.

The descriptive information used with the ORDN tag was lost although the date and place information transferred.

Place (PLAC) information when subordinated to LDS events using the Temple (TEMP) code was ignored. FO does not record this data.

Problems with source input:

The DATA tag and the subordinate TEXT tag is not recognized when used with source citations. Information is recorded in the exception list.

Family Origins does not recognize the DATA/EVEN/X structure when used for source information. The tags and information are transferred to the source fields and require editing.

A note placed under in the repository information was not transferred but appeared in the exception list.

Summary:

Most of the tags Family Origins fails to recognize are rarely used or contain non vital information. For the majority of these tags the information is available in the exception list. In those instances where the data is not transferred and does not appear on the exception list the most important are notes at the 0 (zero) level. These items can be located on the imported Gedcom file by using a text editor and searching for 0 NOTE.

Import rating: 70.85 %