PAF 5.1.12 Summary

Export

Data export problems:

Test GEDCOM 1. This test used the GEDCOM 5.5 export option using the ANSEL code option. PAF 5.1.12 also uses several tags from the draft specifications of GEDCOM 5.5.1. These tags will not be recognized by programs supporting the 5.5 specification. The test file does not contain any data to test these tags. As a result they do not appear in this report. It also supports a Unicode character set. At the time of testing this character set is not supported by other genealogical programs.

The GEDCOM GEDCHK report found no syntax errors, 8 tag exceptions, and 9 extension tags.

The tag exceptions included the following:

Seven of the tag exceptions were related to an Individual's address. They were at the 1 level. Should have been at the 2 level.
The other exception, source call numbers (CALN) were at the 1 level rather than subordinate to the REPO tag and occurred 9 times

The 9 extensions are:

_UID	special individual ID code inserted for later file comparisons.
_AKA	used for the “also known as” name.
_MARNM	used for married name.
_PRIMARY	indicated primary family for adopted child.
_SCBK	used for image object identification.
_PRIM	indicates preferred image.
_TYPE	used to indicate photo type.
_SSHOW	possibly indicate if image is included in slideshow?
_NAME	used for name in the address group of tags.

Conclusion:

There will be limited information loss from the PAF 5.5 Gedcom file. The most critical loss would be that of the source call numbers. Those users who utilize the address fields will also miss this information.

Export rating: 92.73 %

GEDCOM imports:

Control GEDCOM

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

PAF recognizes only one name tag per individual. Married name not imported.
PAF has no fields for the following tags, all data was imported to notes.

	ROLE	individual role in event.
	PROP	property possessed by individual.
	ASSO	associated individuals.
	CAST	identifies caste or ethnic group of individual.
	NATI	nationality
	NCHI	number of children.
	NMR	number of marriages.
	ADDR	address data for individual.
	AGE	age information.

PAF has no fields for these tags. Data was lost.

	QUAY	quality/surety levels.
	NSFX	name suffix information.
	PLAC	place information lost when importing LDS ordinance events. Only Temple name retained.
	STAT	status information for LDS ordinances.

Events requiring editing after importation.

	ORDI	ordination of individual.
	EVEN	miscellaneous custom events using the TYPE tag as descriptions.
	SSN	Social Security number.
	IDNO	misinterpreted employee ID number causing import problems with related data.
	MEDI	media type source information is imported to source comments.
	EDUC	education information.
	ALIA	partial import (reference number only) to aka field.

Source data for nickname was not imported.
Source data for cause of death not imported.
Census data imported to MILT-END event.

Problems with source input:

Use of the DATA/EVEN/ substructure in source resulted in source information requiring editing. No data was lost.

Conclusion:

Of the data sent to notes on import that concerning property (PROP), nationality (NATI), and address (ADDR) is the most important and, in a large GEDCOM, would result in considerable affort to edit. The most serious loss is that of the surety information. Overall, importation of data from a program that supports the 5.5 specification more fully will require extensive editing.

Import rating 69.61 %

The Gedcom Testbook Project
© Gentech 2001
Last Updated 22 August 2001