Genealogical resources contain records of different kinds and each may or may not correspond to a kind of genealogical record linkage. To link entities that are represented by different kinds of records we need to bring the identifying data into a single record -- one which has the fields appropriate for the desired linkage result. For example, suppose the genealogical record linkage system is to link two records as representing the same event. The system needs to view and access two different documents and see them as recording the same event. To build compatible linkage records the system requires a model of the record structure. To view or access the records requires an engine. An automated system builds documents following the document model and when it accesses them, it uses the document engine. When this system links events into individuals, it must utilize the individual model and engine. When it links events and individuals into families, it must add the capabilities of a lineage-linked model and engine.
| 1-3.1 | Lineage-linked model. | ||
| 1-3.2 | Basic genealogical relationships. | ||
| 1-3.3 | Entity class transformations. | ||
| 1-3.4 | Data propagation rules. | ||
| 1-3.5 | Individuals & their merotypes. | ||