Ancestral Quest 3.0.34 Summary

Export

Data export problems:

Test GEDCOM 1. This test used the GEDCOM 5.5 export option using the ANSEL code option. Because Ancestral Quest 3 provided the original code for PAF 4 there are a number of similarities to the PAF GEDCOM.
The GEDCOM GEDCHK report found two syntax errors, two tag exceptions, and 13 extension tags.
The tag exceptions included the following:
The FILE tag was used out of context with the OBJE tag when identifying the location of an image.

The 13 extensions are:

	_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 or source type.
	_SSHOW	possibly indicate if image is included in slideshow?
	_DATE2	used for second date in a date range.
	_HUSB	used to indicate child status within a family.
	_WIFE	used to indicate child status within a family.
	_MASTER	indicates source is to appear in Master listing.
	_ITALIC	indicates source title to be in italics.
	_PAREN	indicates source facts are to be enclosed in parentheses.

The two syntax problems concerned the coding of the object (OBJE) linked to individual 20 (Joseph Smith). The required subordinate tags FORM and FILE were missing.

Conclusion:

There will be limited information loss from the Ancestral Quest Gedcom file. All user defined tags are exported using the miscellaneous EVEN tag. Care must be taken when using the description field for these tags however, as this information should be the descriptions as defined in the GEDCOM specifications. Other information should be entered in the notes or source comments. To avoid date losses do not use the date range option as that will output the second date with an extended tag. AQ also has the ability to code images for export. Few programs can read this data. Information transfer using extended tags will also be ignored.

Export rating 97.59 %

GEDCOM imports:

Control GEDCOM

Option to send all unrecognized items to notes was selected.

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

Ancestral Quest recognizes only one name tag per individual. Married name information was sent to notes. Conflicting birth information (duplicate BIRT tag) was also sent to notes.

Ancestral Quest 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.
MEDI		media type information.

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

PLAC		place information lost when importing LDS ordinance events (baptism has option). Only Temple name retained.
STAT		status information for LDS ordinances.

Events requiring editing after importation.

	SSN		Social Security number missing but related data recorded.
	IDNO		employee ID number recorded but related data sent to notes.
	ALIA		partial import (reference number only) to aka field.
	ADOP		child linked but parental status required editing.

Problems with source input:

Use of the DATA/EVEN/ substructure in source resulted in source information requiring editing. No data was lost but some was sent to notes.

Some source information was sent to notes while a few other sources required minor editing.

Source data for nickname was not imported.

Source data for cause of death not imported.

Source linkages for notes were sent to notes.

Import Rating: 76.90 %

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