4.6 Lineage linked data
Earlier you saw how a genealogical database records relationships between people. A lineage linked database allows queries such as 'Ada Rosewell the daughter of John Rosewell' and makes possible the creation of family pedigrees and other charts. For example, the pedigree chart below shows how Alcimenes was the son of Jason (the Argonaut) and Medea and the grandson of Aeson and Alcimedes.
Part of the family tree of Jason the Argonaut (from Graves, R. (1944) The Golden Fleece)
There is a widely used standard format (GEDCOM) for data files that describes genealogical trees such as this. GEDCOM format files can be exported and imported into all genealogical packages and make it easy to exchange genealogical information. You can see the GEDCOM encoding for the family tree by clicking on 'View document' below.
Using the above file structure, spend a few minutes identifying the features below.
Note how each individual has a record and is identified by a number. For example, the entry for Jason (I1) is:
0 @I1@ INDI
1 NAME Jason //
1 SEX M
1 FAMS @F1@
1 FAMC @F2@
There are also references to families associated with Jason, F1 and F2. These can be found defined elsewhere in the file. F1 is Jason and Medea's family with their five children:
0 @F1@ FAM
1 HUSB @I1@
1 WIFE @I2@
1 CHIL @I3@
1 CHIL @I4@
1 CHIL @I5@
1 CHIL @I6@
1 CHIL @I7@
and F2 is the family consisting of Jason's parents and himself:
0 @F2@ FAM
1 HUSB @I8@
1 WIFE @I9@
1 CHIL @I1@
Notice how Jason, coded as I1, appears as the husband in family F1 and a child in family F2. These links trace out the lineages in the data; they make it possible to browse and search related individuals and draw charts such as the one above.
GEDCOM files are not intended to be human readable and they can be much more complex than the example seen here. Their main use is a transfer format.