The Family Reconstruction

Reconstruction.doc  Compiled by E.G.Richards 21/6/2007

Index

Index	1
Introduction	2
1.1   The Name	2
1.2   The Clan	4
1.3   Records and their  Sources	4
1.4   The records	6
1.5   Person Identification numbers (PIN)	7
1.6   Collate	7
1.7   Names (NIN)	8
1.8   Dates	8
1.9   Identification numbers	8
The Reconstruction	9
2.1   Families	9
2.2   Provisional  families	9
2.3   Refining  provisional families	10
2.4    20th century births	10
2.5   Extras, mothers and fathers	10
2.6   Suggestion and assignment lists	11
2.7   Further steps	12
2.8   Second marriages	14
2.9  Gedcom files	14
2.10 PINDATA	15
2.11 FAMGROUP.FAM	15
The programs	16
3.1   NAMES	16
3.2   FAMGROUP	16
3.3   Files input by FAMGROUP	17
3.4   Files output by FAMGROUP	18
3.5   COLLATE	19
3.6   FAMLOG	19
Results and Discussion	20
Appendices	21
Marriages of parents of families	21
Families to extras	21
Daughters to girl marriages	21
Sons to boy marriages	22
Sons to fathers of families	22
Deaths	23
Death notes	23
Death records	23
Child match	23
Mother match	24
Father match	24
Possible mothers to mothers of families	25
Possible fathers to fathers of  families	25
Possible second marriages of fathers	26
Possible second marriages of mothers	26

Introduction

This project arose from a one name study of the name Gampton and its variants.  The data support the origin of the families concerned and of the name itself in the village of Galmpton in Devon, in the parish of Brixham The aim was to reconstruct the family relations between the persons mentioned in the records.

Not all people bearing the name GAMPTON  are related to each other.   It is convenient to refer to those that are as members of the clan.  Here we use the term in not quite its usual sense.

The project lead to the development of a computer program, FAMGROUP, which considerably facilitated it  It is by no means necessary to use this program and the methods used could be carried out by hand. Nevertheless, the program provides several advantages over the manual method:

1.	It is much faster
2.	It much less tedious
3.	It considerably reduces the number of errors made
4.	It is more systematic
5.	It provides a record of the details of how the reconstruction was done

It has the disadvantage that the primary data must be entered into the computer by hand; but this need not be done more than once (except for corrections).

1.1   The Name

The data consists, principally,  of records which refer to people with surnames which match G*M*T!ON.  Here we define the name by wild cards: ‘*’ stands for any sequence one or more letters and  ‘!‘ stands for zero or one letter.

The following spellings were encountered; sometimes several different spellings were often found in the same family:

GALMPTON, GALMTON, GALYMPTON, GAMEPTON, GAMETON, GAMPTION, GAMPTON,  GAMTON,  GAMTTON, GEMEPTON, GEMETON, GEMPTON, GIMPTOM, GOMPTON, GUMPTION, GUMPTON, GYMPTON.   

We have not included Campton, , Crumpton,  Kampton (with one exception) or Gamston.  It was held to important that  an image of the original document (GRO index page, census enumeration page etc.) be inspected.  Nevertheless errors of ytwo sorts are likely.

Firstly a name which was truly a GAMPTON variant was written as one of these, or some other variant.  These records are lost and not included.      

Secondly a name was written as GAMPTON or one of its variants though the true name was one of these other variants.  This leads to spurious records which are difficult to detect and which cannot be incorporated in the reconstruction.  One notable example is Lord GAMPTON in Oxford in a transcription of the 1871 census; close examination of the census page reveals that the name is more likely to be Crumpton 

The number of references to surnames in the centuries in the early parish (in the vicinity of Brixham, Devon) registers are given below:

    Baptisms/births	        Marriages			Burials
Century:			17th 	18th	19th. 	    17th	 18th	19th	  17th	18th	19th

Galmpton		9	0	5	    7	3	0	  4	0	0	`
Galmton			9	1	0	    0	0	0	  2	0	0
Galympton		0	0	0	    1	0	0	  0	0	0

Gamepton		0	2	0	    0	1	0	  0	0	0
Gameton		0	7	0	    1	2	0	  1	0	0
Gamption					    0	0	0	  0	0	0
Gampton		5	17	24	    2	11	16	  9	12	15
Gamton			0	0	0	    1	2	0	  3	2	0
Gamtton			0	0	1	    0	0	0	  0	0	0

Gemepton		0	0	1	    0	0	0	  0	0	0
Gemeton		0	1	0	    0	0	0	  0	0	0
Gempton		2	36	13	   0	10	9	  0	27	11

Gimpton			0	0	3	   0	 0	0	  0	0	2
Gompton		0	3	1	   0	 3	0	  0	2	0

Gumption		1	0	0	   0	 0	0	  0	0	0
Gympton                     	0	0	0  	   0	 0	0	  0	0	0
Total                                 24	63	48	   13	31	25	  19	43	18

Gympton appears  once in the 1851 census. The bearer was a servant and her master was perhaps uncertain of her name.
The figures for the 19th century are misleading because they do not include data after 1837;  they do not include GRO data.

First extant occurrence of the most common forms of the name are:
Galmpton			1589			1589			1641
Gampton			1604			1659			1570
Gempton			1685			1711			1707

Although name was probably GALMPTON  (with an L)  when it became hereditary;   this and similar variants were virtually extinct by 1800 but before the 17th century it was the most prevalent form of the name

The form GAMPTON appears first at the end of the 16th century and GEMPTON not till a century later. In the 18th century, these two names are about equally common.   After 1800 nearly all instances of surnames are GAMPTON and GEMPTON but there are a few instances  of GIMPTON.

.	Nowadays, GEMPTON is the most common (or even, perhaps,  the only) name in England and  is probably the only form in Australia and New Zealand.  GAMPTON may  be extinct in the United Kingdom but has been identified in the U.S.A.

In censuses and GRO births, marriages and deaths, we found few instances of other surnames besides GAMPTON and  GEMPTON.   There are 11 references to GOMPTON from 1717 and 30 to GIMPTON from 1794.  We encountered a few GALMPTONs, but none born after 1844.  The bearers of these two names are referred to with a more standard spelling of their name  in other records.   Among the GOMPTONs  was a fisherman, Marquis GOMPTON, known to be generally named GEMPTON.  The other was a Mary Ann born in Sherringham who appears in one census alone in her household as a GOMPTON.Several other instances of GOMPTON that were found turned out on closer inspection to be mistranscriptions of CROMPTON

Several instances of GAMTON were also found but these occurred in places far from the usual habitations and with first names not otherwise used by GAMPTONs.

We accordingly assumed that all variants except GAMPTON, GEMPTON and GIMPTON were extinct after 1844 and GRO indexes up to 1900 were only searched for these three names; nevertheless, names which are lexicographically close to these (including GALMPTON, GAMEPTON and GEMEPTON) would have been picked up. 20th century indexes were searched only for GEMPTON.  We also assumed that GAMPTON was extinct in the 20th century and the most later GRO indexes were search only for GEMPTON.  You should note that these assumptions may in fact be wrong.

Before the end of the 18th century records are almost entirely from Brixham and nearby parishes in Devon. In the 19th century they appear elsewhere: at Dover and Gravesend in Kent, in London, in Hull on the Yorkshire side of the Humber estuary, in Grimsby in Lincolnshire on the South side of the Humber estuary, in Caistor, a little further South into Lincolnshire, and in Guernsey. The name is absent from the Dover registers before about 1800.  In the 19th century and early 20th several families emigrated to America and to Australia and New Zealand.    Nevertheless, the name also occurs in isolated records from various parts of England:  Staffordshire, Cambridgeshire and London.

1.2   The Clan

I refer to people bearing the GAMPTON  surname  and  who are related by blood or by marriage, as members of the clan  –  I use this word in not quite its usual sense.

The rare  variants mentioned above occur in parts of the country where the name has not occurred before or after and  tend to use first names otherwise unknown. This leads to the (unproven) suspicion that they are not clan members.

A person may join the clan by:
1.	being born into it
2.           marrying into it (i.e. a girl not born into the clan marrying  a male clan member)

and a person may leave it by:
1.	dying
2.	marrying out of it (i.e. a girl clan member or widow marrying someone not in the clan)
 	Note that this category also includes the second marriages  of wives of deceased GAMPTON men.

1.3   Records and their  Sources

The following types of record in various repositories of data were searched for references before 1920.

1.	The GRO indexes from 1837 to 2003
	Initially the calendars at the FRC or microfiches of them at SOG were searched.  Later facsimiles of the calendars on 
              www.1837online.com and transcripts on FreeBMD.COM  (not quite complete at the time of writing) were exhaustively
              searched..   Certificates were obtained for only a few such events.

2.	The 1992 edition of the IGI at the library of the Society of Genealogists.

3.	Transcriptions of the parish registers of:

 	Brixham, Devon.		Three transcriptions of the parish registers of Brixham were available.
   	a.	The IGI (marriages and baptism), 1992 edition
   	b.	A transcription made by or on behalf of Arthur Gempton
   	c.	A partial transcription made by Devon Family History Society

Churston Ferrers, Devon	Two transcriptions of the registers of Churston Ferrers are available:
   	a.	The IGI.
b.	A transcription made by or on behalf of Arthur Gempton
	
The agreement between these transcriptions was very good

The transcriptions or copies/microfilm of the following registers were also searched at the library of the Society of Genealogists or at the appropriate Record Office:

Bermondsey, Surrey
Dover, Kent
Gravesend, Kent
Kingswear, Devon

We have not inspected registers from parishes on the Humber estuary  since the clan did not reach that locality till after 1837. Nevertheless the IGI was searched for these but nothing was found.

Boyd's Marriage Index was searched for all name variants.  None were found which were not in the transcriptions mentioned above.

4.	Transcriptions and facsimiles of census information:

1.   A transcription of the 1851 Census returns for Devon as published by the LDS on CD ROM

2.   A transcription of the 1881 census returns for the whole of England and Wales as published by the LDS on CD 
                     ROM..

	3.   A transcription of the 1901 census returns for England and Wales as published on the website: 
                   	 (www.census.pro.gov.uk)

	5,   Transcripts and facsimiles of the 1841, 1551, 1861, 1871, 1881, 1891 & 1901 as available in websites:
	      Findmypast.com
	      FreeCEN.com
	      Ancestry.com
                     Selected transcripts of the 1880 U.S. census

 	 It should be noted that, at the time of writing, none of  these English transcripts were complete

5.   	The graveyards of St.Mary, Brixham, and Kingswear and of Dittisham in Devon were searched for memorial
inscriptions    Transcriptions of some of these are also published by the Devon Family History Society and are in
agreement.

Several other churchyards in the vicinity of Brixham were searched but no relevant inscriptions were found.

6.	Various trade directories and miscellaneous lists

7.	Transcribed wills

	It should be noted that many Devon wills were destroyed in World War II by a bomb, but some were partially
               transcribed before this.
	PCC wills indexes were searched but none relevant were found
Modern, post 1858 will indexes have not yet been searched

8.	Various marriage allegations in the library of the Society of Genealogists

A few records bearing other surnames, such as wives and husbands, were also collected.

1.4   The records

Each record is identified by a Record Identification Numbers or RIN; this consists of an initial letter (see below) followed by a number.  Memorial inscriptions and census households which all contain records appertaining to several people are further identified by appending a number indicating their position in the memorial or census.  Census records are still further identified by the last two digits of the census year.

e.g.  C0123/09/51  indicates the 9th person in census household  123 in the 1851 census.
        W0066         indicates wedding record #66 obtained from a parish register

Each type of record was identified by a letter (RIN letter) as indicated below::

#   Category                                     RIN Letter           Count of G*M*T!ON records
________________________________________________________________________________________

1.   GRO births			B		            141		
2.   GRO marriages		M		            105 		

         		      Male						47
         		      Female					58
3.   GRO Deaths			D		            106

4.   PR baptisms			X		             146
5.   PR weddings			W			69

       		      Male						35
        		     Female					34
6.   PR funerals			F			81

7.   Wills			P			  7

8.   Census entries		C	                          305  

         		     Households                                                         103

9.   Memorial inscriptions		I			20
      Memorials			    	            			6

10. Directories etc.		D			20

11. Marriage allegations		A			  2

            						            -----
						           1002

Several records appertaining to married girls who no longer bear the name GAMPTON and of wives before their marriage to a GAMPTON were also collected but these are not included in the table above. 

The information in the various records is collected in a series of .TXT files.  These are (tab separated variable files- tsv) spreadsheet files which may be read into MS EXCEL or examined by a text editor program..

No claim is made that these 1002 records are the only ones recorded or availablre.

1.5   Person Identification numbers (PIN)

Several records may refer to the same person and we have attempted to identify such records with a PIN.

Each person is assigned a four digit Person Identification Number (PIN). I have appended each PIN by /GAM to indicate, for my own convenience, with which database they are associated; this last point need not concern you. e.g. 345/GAM is person 345 of the GAMPTON database.  Some other records collected refer to persons not bearing the clan name but who are related in some way. These may also be assigned a PIN. 

It is intended that each person should be assigned a unique number; when a record is identified as being about a certain person, the PIN of that person is assigned to it.  There may be several records, which describe the same person; these were assigned the same PIN.

An initial assignment of a PIN to the person who is the subject of several of the records was attempted:Firstly, the subject of each baptism and birth registration was assigned a unique PIN (for baptisms, this was generally the same number as the RIN number of the baptismal record). The only exception was when records for both the baptism and the birth registration of the same person were listed. 

We have thus assigned PINs to 521 individuals of which 398 were born a GAMPTON, figures that do not include all wives who married into the clan.  There are nevertheless a number of records appertaining to individuals, who could not be identified, which have  been assigned a PIN of 0/GAM

1.6   Collate

The first step in the reconstruction was to list all available records in alphabetical order of the first names of their subjects (This was facilitated by a program COLLATE). Records with the same first name were ordered chronologically by birth year.   In this way, records referring to the same person were close to one another in the list. This facilitated the assigning of PINs to many other records (but by no means all) Two records giving the same first name, birth year  (to within 2 years) and a similar birthplace were generally assumed to refer to the same person, though more detailed scrutiny was sometimes necessary.

Later as the analysis progressed, the subjects of other records became identified as a person already assigned a PIN; others were seen to have not been assigned a PIN and these were assigned a new PIN. Examples are wives and widows in census returns, memorials, and marriages; others were the husbands of girl clan members. A small number of records, funerals and deaths in particular, have eluded the identification of their subjects and the PIN of these was entered as 0/GAM. 

1.7   Names (NIN)

First (and second) names frequently appear  in the records in variant forms. These result in:

Spelling variations. e.g. Collette and Colletta
Reversal of order of two or more given names. e.g. William James for James William
Contraction of names. e.g. Jame for James
Latinisation of names  e.g. Jno. For John.
Substitution of diminutives. e,g. Willie for William
Substitutions of Nicknames e.g. Betsy for Elizabeth, Polly for Mary
Omission of one or more given names. e.g. Thomas for Thomas Samuel
Transcriptional errors. e.g. Narquis for Marquis

This makes the identification of a person by their name problematic.  To alleviate this, all the records were searched and a list made of all the first (and second) names given therein.  This list was sorted into alphabetical order and duplicate names  removed.     This resulted in a list (the A list) of 214 distinct forms. Some second names occur only as an initial and are included as such in the A list..

This list was inspected carefully and a second list (the list B) of 142 distinct names extracted from it.  Each name in list B was assigned a unique number (its Name Identification Number or NIN). This list included single letter initials – which could not be expanded into a name.  The forms in the A list were then assigned the NIN of the name to which they were judged to correspond. This name in the B list is termed the Standard Name.

The construction of List B was generally unproblematic.  Abbreviations, shortened forms and diminutives were easily expanded, as were common nicknames. 

If  two records bore first names with the same NIN, they were judged to refer to people with the same name, although the given forms of the name might differ. (e.g. Betdsy and Elizabeth have the same NIN)

It was invariably possible to assign a sex to each name.  This was also included in the B list.  It is perhaps a lucky accident that sexually ambivalent forenames were not encountered.

When a first name was encountered in the processing described below, the A list was searched till the name was found.  The NIN, standard name and sex of the person in the record was thus established.

Place names were sometimes recorded as the name of the parish in which the event occurred, sometimes as a registration district. The matching of place names was problematic like first names.  This problem was solved in a similar way so that each place was assigned a PNIN or Place Name Identification Number.

1.8   Dates

For the present purposes, only the year in which an event occurred is recorded; usually that is all this is known of it

Several factors render even these to be inaccurate. Thus dates which are erroneous may be given in a record. Some reasons for this include:

1.	In registrations of death or in censuses, the exact age of a person may not be known by the informant
2.	In GRO indexes for the March quarter, the actual event may have occurred in the previous year
3.     	Baptisms were usually conducted a few days after the birth, but sometimes much later - even in another year.
4.	Births may not have been registered till sometime after the statutory 6 weeks established in 1874
5.	In the 1841 census, the ages of adults were generally rounded  down to a multiple of 5 years	

1.9   Identification numbers

 In summary

PIN	Person identification number		e.g.  123/GAM

RIN	Record identification number		e.g. C0123/02/51,   B0123

NIN	Standard name identification number	e.g. 123

PNIN	Standard place name identification number	e.g. 56

The Reconstruction

I have attempted to work out the family relationship between the people mentioned in only B,X,M,W,D,F,C,I  (see above) records from 1600 to 2003 using the custom written program FAMGROUP. Nevertheless everything that the program does and which I describe below, could. have been done by hand.  FAMGROUP takes a few seconds. Done by hand it would take weeks or months.

It should be noted that the program required considerable interaction with user who must record the best choices for several assignments as described below.  In practice, the program was run several times with different choices af assignments

The input to the program is the databases containing the eleven categories of record described above. These are machine-readable versions of the ASCII files mentioned above.

The output is several lists discussed below.  Chief among these is a file called famlong.txt which contains a list of the parents and children (and the records appertaining to them) of 109 families. This is the Family List

2.1   Families

A family consists of a mother, a father and zero or more children.  The family list contains the names of these members together with the a list, in chronological order, of the records which mention the events in their lives.

A family list also gives the range of each family: i.e. the number of years from the marriage of the parents (or birth of the first child) to the birth of the last child; It may also give for the father, the number of the family in which he was a child, and for male children the number of the family (if any) in which they were the father.

All the children in a family (if any) have the same two parents (though the name of one may be unknown), but note that there were a number of childless marriages.  These are taken as families with no children

2.2   Provisional  families

The first step was to construct a provisional list of families and their members.  This provisional list was later refined.  Note, however, that births after 1911 were treated differently (see 20th Century births below).

Some records provide information about the first names of the father of a child, the mother or both. Such records are:
B   Birth registrations when the certificate is available
X   Baptisms in parish registers
C    Census returns
I     Memorial inscriptions.

All such records that mention the first name(s) of at least one parent of their subject (a child). These records were then sorted as follows:
1.	Into the alphabetical order of the standard first name of the fathers
2.	Those with the same father into alphabetical order of the standard first name of the mother
3.   	Those with the same names for both parents  into chronological order of the child’s birth years

Missing (NIN=0) names of a parent were treated as if they were alphabetically before AAA and put at the top of the appropriate section of the list.  There were no missing birth years, but had there been any, a birth year of 0 would have been used.

The list was then divided into a number of groups each member of which has the same father and the same mother.  The name of either (but not both) parent could be blank (NIN=0). These groups are the provisional families. The members of a family (the children) remain listed in the order of their birth years.

These provisional families may contain records about people who belong to two separate families whose parent or parents happen to have the same name.  Conversely the children of one actual family may be assigned to two or more of these provisional families; this can occur when only one parent is mentioned in one set of records and both or in another.

It is also important to note that a single child may be represented by more than one record (baptism, birth registration, several censuses and a memorial inscription).  The PINs of these records should later be made to match.  Sometimes two records in the same family matched by name but not by birth year; it is possible that these refer to two separate children, the first of which died before the birth of the other. This may be corroborated by a death record of the first

2.3   Refining  provisional families

We may expect a woman to produce her children  over a period (range) of no more than 30 years, say from the age of 16 to 46, but the range of a family is generally less and few exceed 25 years. If we find several children in the same provisional family produced over a longer period (more than 25 years), we may infer that two families are involved.  In these cases we may search for gaps (we have take this to be 9 years or more) between two consecutive children in the list and split the family in two at that point.  This division of a family into two may be corroborated if the two sets of children were born (or baptised) at  two different places. 

Having done this we inspect each provisional family for further gaps (we have taken a period of 6 or more years to indicate a gap; the figure of 6 years is adjustable and provides what I judge to be an appropriate value) between two sets of children. If we find such a gap, we again split the family into two families..  This cannot be a hard and fast rule and discretion and judgement must be employed in its application

A complication arises in censuses. Sometimes the father of the family is absent (at sea?) and only the mother is listed. If there are two such households with mothers with the same name in the same census, they will end up, wrongly, in the same family. The census data was inspected closely for such families and details of the censuses in which they occurred noted in a file (special.txt). 

We now scan the families to see if there are pairs of families which share a father  (or mother) but in which the other parent is missing in one but given in the other.  If the combined span of birth years of these two families does not exceed 25 years and if there are no gaps of 6 years or more, we suppose that the two sets of children belong to the same family and we amalgamate them.  Such an amalgamation may be corroborated if the birthplaces are geographically close. 

These processes represent a refining of the original list of provisional families. It cannot be totally excluded that a family in the resulting refined list may represent two actual families with parents of the same name.  Generally, all the children of a family were baptised (or born) in the same place, but for a few families they were born in different places with clear evidence that they belong to the same family; this provides evidence of migration.

If both parents of any child in a refined family are known, then the name of the father and mother of the family are known. The  assigned names of the parents for each such family are adjusted accordingly.

2.4   20th century births

Starting in 1911, the GRO birth registration indexes give the maiden name of the mother.  A different method was used to group these into families.  The records were sorted into alphabetical order of the maiden surname of the mother.  Records with the same maiden name were sorted into chronological order of the birth year.  Thereafter these families were treated in a similar to to the others.

2.5   Extras, mothers and fathers

When the provisional  family list had been constructed as described above, a number of B,X and C records, which mention neither of the subject's parents, had not been assigned to any family. These may include census returns and GRO birth registration index entries for which the certificate has not been obtained and.  These records are listed and referred to as Extras.  Others are listed as possible mothers or fathers

Records listed as extras are:
1.	Pre 1911 Birth index records of males for which a certificate is not available
2.	A very few baptismal records which do not indicate the name of either parent
3.           Census records which do not specify either parent and which do not refer to married or widowed females

Records listed as possible mothers are:
1.	Birth index or baptism records of females not bearing the clan name (and previously identified as likely wives)
2.	Census records of females who are married or widowed
3.	Records of females on the 	extra list which could not be assigned as a daughter in a family

Records listed as possible father
1.	Records of males on the extra list which could not be assigned as a son in a family

2.6   Suggestion and assignment lists

There remain several records  (including extras, see section 2.5) not included in the Family List and several categories of information about members of the families, which are likewise not yet included in the list.  These require the assignment of a match, to a target.    The target is usually (but see below) a record on some list.  The match is generally some member (father, mother or child) of some family. These assignments require that the two items should refer to the same person.  This identification of the person mentioned in the match record with that in the target requires the satisfaction of several criteria.   These are considered in detail below (See the Appendix).

The program works through the targets in turn, entering its details in the suggestion list.  For each, it inspects every relevant item to see if there it matches the target.  Sometimes no match will be found, sometimes just one and sometimes there may be several matches for a given target.  For every match that it finds, the details are added to the suggestion list.

Later, the user must inspect the suggestion list at leisure, confident that no other possible matches are likely to exist.  He may then edit it by selecting one of the suggested matches and deleting the others.  The resulting edited list is called an assignment list..  This is then made available to FAMGROUP and the assignments of the matches to the targets duly recorded.

This selection process cannot be done by the machine - the criteria are extensive or too complicated for this to be envisaged.. Nevertheless, some general priciples emerge:

1.	If there is just one match, this is generally accepted.  Care must be taken to ensure that the match has not been assigned to another target.

2.	When there is no match in the suggestion list, a match may sometimes be found by hand using more relaxed criteria if appropriate.

3.     When there is more than one match, each must be considered in detail in a manner that cannot be automated by the computer. 
        This may involve long chains of reasoning and the use of facts that cannot be exhaustively listed; human intervention may 
         succeed where the computer fails. Some such reasons for such assignments are recorded in family notes.doc

Sever target/match suggestion lists are prepared

1  	To assign a family to a record on the extras list (EXT).
    			Target:   A record on the extra list with a named person
Match:  A family in which the person may be a child

2	To assign daughters of families to the bride of marriages  (GIR)
Target:   The marriage record of a named girl
Match:  A daughter of a family who may be the bride

3	To assign sons of families to the grooms  of marriages (BOY)
Target:   The marriage of a named boy 
Match:  A son of a family who may be the groom

4	To assign a child of  some to a family to the father of some later family - thus establishing descents (PFM)
Target:   The named  father of a family
Match:  The child in some earlier family who may be this
father

5	To assign a family member to each  record of a death, burial or monumental inscription  (DEA)
Target:   A death , funeral or MI record
Match:  A father, mother or child of a family

6	To assign  a family to a record  on the mother list (MOT)
Target:   The record on the mother list
Match:  the family in which the mother may be the target

7	To assign a family to a record on the father list  (FAT)

Target:   The record on the father list
Match: the family in which the father may be the target

	8.	To assign assign marriages of men to fathers  of families as second marriages
			Target :   A marriage of a man
			Match:    A father of a family

	9.	To assign assign marriages of womenn to mothers  of families as second marriages
			Target :   A marriage of a woman
			Match:    A mother of a family

2.7   Matching

The reconstruction involved extensive matching of records. Thus, two  items (records, persons) may be compared to see if they are likely to refer to the same person. The minimum items of information that should match are:

1	First names.
If two items match (i.e. refer to the same person), the first names must bear the same NIM (see above), both greater than If both record a second name (or initial), the initial letters must be the same
Note that if a name is missing it is assigned a NIM of 0
Problems sometimes encountered are name omission and reversal.  Records concerning a person with two first names may give them both but in reverse order. e.g. William John might refer to a John William.  Alternatively, a record may only give one of them, William or John in this example.  When appropriate both names are compared.

2	Birth year.
If two items both containing a birth year match, the birth years must be the same within 2 years.This latitude may be extended

3.	Birth place
If two items both contain a birthplace, they must bear the same PNIN (see above)

Other, more stringent criteria of matching are employed where appropriate; likewise, the criteria, particularly concerning years, may be relaxed as appropriate.  It must be recognised that not every record bears all three of these items of information.

2.8   Further steps

After the provisional families have been defined, the program now further refines the families.

1.	Add additional families 
It is sometimes reasonable to postulate the existence of further families to be added to the list The range of dates of the children and the name of the father must be supplied (from the file addfam.txt)
2.	Sort families by birth year of first child
It is convenient to sort the families into the order determined by the birth year of the first child.

3.	Add surmised children
It is sometimes reasonable to postulate the existence of further children in some families. These are added with the record number replaced by ‘surmised’.  Details of the family and child are supplied and discussed in Family notes.doc.
4.	Suggest families of extras
A suggestion list of the families, in which each the person mentioned in the extra might be a child, is preparedExtras are B.X.C,I records which specify neither a father nor a mother
5.	Find marriages of parents 
For each family, the marriages of boys are scanned and one that occurs in an appropriate year (i.e. not later than 3 years after birth of eldest son or earlier than 9 years before) and for which the names of the groom and bride match the names of the father and mother is selected.

6.	Read the assignment file for extras and assign records to families as specified 

7.	At the same time,  unassigned extras are redistributed.  Some extras will have no assignment in the assignment file.  Such extras may:
a.	If male, refer to the father of a family; they are added to the father list of possible fathers
b.            If female, refer to the mother of a family; they are added to the mother list of possible mother

8.	Rearrange children records 
At this point, it is assumed that every record of every child in every record is marked by the PIN of the child.   The records of the children of each family are nor grouped by PIN (and so refer to the same child).  The set of records of each child is sorted chronologically; finally, the children are sorted by birth year.

9.	Suggest girl marriages to daughters 
A suggestion list is prepared which lists for every marriage of a female member, the possible female children, to which it may correspond.

10.	Read & save marriages of daughters 
The assignment list is read and marriages of females added to the events of the appropriate daughter
11.	Suggest boy marriages to sons
A suggestion list is prepared which lists for every marriage of a male member, the possible male children to which it may correspond.

12.	Read & save marriages of sons 
	The assignment list is read and marriages of males added to the events of the appropriate son.

13.	Augment families with childless marriages
At this point, several marriages of clan boys will remain unassigned.  These correspond to childless families.  This list of families is now augmented by these.

14..	Suggest the family in which they were born of fathers
A suggestion list is prepared in which the targets are the fathers of each family and the matches are children who match these fathers

15	Read & save parent family of fathers (ASSNPFM)
Children given in the assignment list iareassigned to the father of a family
16.	Suggest deaths (SUGDEA)
A suggestion list as prepared. In this, the targets are every Death, Burial or MI record and the matches to a possible father, mother or child.

17.	Read & save deaths (ASSNDEA)
Deaths are assigned to fathers, mothers or a child according to the assignment list.
19.	Suggest mother records (SUGMOT)
For the mother of each family, a suggestion list of a mother on the list of possible mother’s is made
20.	Read & save mothers (ASSNMOT)
Possible mother records are assigned to the mothers of families according to the assignment list.

21.	Suggest father records (SUGFAT)
For the father of each family, a suggestion list of a father on the list of possible fathers is made

22.	Read & save fathers (ASSNFAT)
Possible father records are assigned to the fathers of families according to the assignment list.

23.	Copy child records to father records
Records appertaining to children who have been identified as fathers (in procedure 17) are copied to the list of records of the father.

24.	Suggest second marriages of parents

25	Assign second marriages to parents

26.	Check PINs (CHKSUP)

The assignment of all records is now complete. It is assumed that each record bears a PIN.

27	Checks are now made:

1.   To ensure that each record for a particular mother, father or child carries the same PIN
2.   To ensure that no two children have been assigned records with the same RIN
3    To ensure that mothers or fathers of families and the brides or grooms  of the marriages assigned to the      parents carry  the same pin
4.   To ensure that mothers or fathers of families and the brides or grooms  of the marriages assigned to the parents carry  the  same first name
 
Any discrepancies or missing PINs must be corrected in the assignment file and the program re-run

28.	Sort records of fathers and mothers
The records of each father and of each mother are sorted into chronological order

29.	Save family data
A short list of families giving their father and mother, number of children and the family in which the father is a child is prepared. A long list given for each family, the records of the father and of the mother and their marriage, and for each child a list of their records
30.	Save various output lists (see below)

2.9 Second marriages

There is a strong economic incentive for either a man ore a woman to remarry after the premature death of their spouse, if only to look after the children.  This motive will be diminished, but not eliminated, when the youngest child is old enough to fend for itself.

A search was made for possible second marriages of fathers by first comparing the parents of every pair of families including childless ones).   Comparisons that satisfied the following criteria were listed as possible second families of fathers.

1.	The names of the father of the two families are known and the same2. 	The  year of death of the first mother must be before start of second family3.	The ages of fathers are both defined and equal within 2 years
4.	 Father is older than 20 & younger than 60 at both marriages 
5.	 Procreation range (the length of the period from the birth of the first child of the first family to the birth of the last child of the second must not exceed 50 years

Likewise a search for  possible second marriages of mothers was made by trying to match the mother of each family to the marriage of a female (girl) GAMPTON.   Comparisons that satisfied the following criteria were listed as possible second families of mothers.

1.	The names of the mother and bride must be known and be the same
2.	The gap in yearsa between the birth of the last child of thew first family and the start of the second family must be  positive and not  more that 17 years
3.	3.	The year of the marriage is after the birth of the  last child of the first family but not more than    20 years after
4.	The second marriage is after the death or last event of the father  If this is not so it may indicate a second marriage after a divorce
5.	The bride has not been identified as the child of any family
Details of a pair of families that satisfy these criteria were saved in a file called secmar.txt and are  are further discussed in family notes.doc and in second marriages.doc

2.10  Gedcom files

A GEDCOM file with all the genealogical information available can be produced by the program FAMLOG

This requires the following files:

pindata.txt
	This an ASCII file produced by program COLLATE (see below)
	It contains detail of every PIN in use: records that reference it, names and dates

maiden.txt
	This is an ASCII file
	Details of maiden names of certain wives

Famgroup.fam
	This is an ASCII file produced by program FAMGROUP

FAMLOG produces:

Gedcom.txt
An ASCII GEDCOM FILE which can be imported into appropriate genealogical files
               Note that the INDI numbers are the same as the PINs

Gedcom.err
	An ASCII file containing any errors detected by FAMLOG

pinlist.txt
	A list of the PINs of the INDI defined in the GEDCOM file
	There is a line for every PIN in use. The file contains:
PIN
Family in which PIN is the father
Family in which PIN is a child
Full name
Birth yeare
Principal record

Or  blanks if  a datum is not known

2.11 PINDATA

The file pindata.txt is produced by COLLATE and contains 10 lines of data for every PIN

Line 1	Field 	
        1  PIN (I4 format)                       2  List of record codes              	            The first starts in column 6 and they are in canonical order XBWMADFPIC, separated by spaces
Line 2	Field	1  Gender (M/F) in column 1
              			2  List of name sets, one for each record in canonical   order separated by *
                                               Surnames are enclosed in slashes /.../
Line 3 	Birth data
       		 Field 	1  Date:     Column 6-16: dd mmm yyyy or ABT yyyy
              			2  Reference:        19-26: Xnnnn or Xnnnn/nn
              		3  Place:      28+    not more than 45 character
Line 4 	 Baptism data
        			(as for births)
Line 5  	Death data
       			 (as for births)
Line 6  	Funeral data
       		 	(as for births)
Line 7    First Marriage data
        		Field	1 Spouse PIN: column 1-4
              			2 Date:                         6-16: dd MMM yyyy or ABT yyyy
              			3 Reference:              19-26: Xnnnn or Xnnnn/nn
             			 4 Place:                     28+    not more than 45 character
Line 8	Second  Marriage data
       			 (as for marriage 1)
                
Line 9  	Thired Marriage data
        			(as for marriage 1)
Line 10	 Occupation

2.12 FAMGROUP.FAM

This file is produced by FAMGROUP and it contains details of every family
There are 5 lines for each of NFAM families:

Line 1  Family number (I4),  Number of children, NC (I4)
Line 2  Father PIN (I4),  Mother PIN (I4)
Line 3  Father's first name (A16),  Mother's first name (A16)
Line 4  NC children's PINs (nI4)
Line 5  Blank

The programs

The programs were originally written in FORTRAN 77 for the Atari ST but have been run consitently on the PC using GEMULATOR, an emulator for the PC of the Atari PC.   The source code is available from the author and GEMULATOR can be down loaded from http://www.emulators.com 

The prospective user should note however that the programs access a database of records in binary form.  It would be possible to rewrite the input routines to access the tsv files mentioned in section 1.4

3.1   NAMES

A program was written to scan all the relevant records and make a list of all first names (including those just given as an initial).The program then sorted all the names into alphabetical order and all duplicates removed.  The items on this list we call forms. This list was then scanned by hand and all synonyms removed; at the same time each name was annotated with the sex of the name.  These names are referred to an standard names

The result was saved in a file namesb.txt.

Then the original  list of forms was then annotated with the number of the corresponding name in the NAMESB list.  Finally the list of annotated forms was saved in formsc.txt

When two first names need to be compared, the FORMSC list was searched till they were found.  The numbers then give  the name and sex of the names in NAMESB.  If the numbers of the two are the same, the names were taken to match.

e.g. Polly and Mary in the FORMSC list both bear the same number.  This corresponds to the standard female name MARY.

3.2   FAMGROUP

The source code is available to any person interested.

No claim is made that the program is efficient but it run for the GAMPTON database in less than 15 seconds

FAMGROUP is an interactive program and the writing of any suggestion file or the reading of any assignment file can be turned off at the start.

The first time the program is run there will be no defined assignment files.  These must, in due course be constructed in the light of the corresponding suggestion file.  Thus the first time the program is run, all but the construction of the suggestion file for extras is turned off;  then the assignment file for extras is constructed and the program run again.  All being well, the next suggestion file is produced and the assignment file constructed by the user.  In this way the suggestion and assignment files are made one by one.

There are further interventions desirable or essential in the preliminary stages:

1.	To construct a list of families in famind.txt and of records in recind.txt

2.	The B list of first names must be constructed after a prelinary run of FAMGROUP.  The A list and B list must be given in famgroup.txt

3.	It may be desirable to change some of the parameters define age ranges (in famgroup.txt)  as mentioned in the appendices.

4.	It may be desirable to construct addchl.txt, addfam.txt and respec.txt - see below

The files called progress/changes.txt qnd progress/interfmn.txt provide information of the progress of a run of the program at different stages

3.3   Files input by FAMGROUP

Items of information required by the program are contained in several binary files. These cannot be read by humans
But .txt and .xls files containing the same data are available.

The .txt files are in pure ASCII and cannot be easily printed.

Other input files include:

namesb.txt		Standard names with sex

formsc.txt		Forms with standard name equivalent

limits.txt		A list of parameters required in matching

addchl.txt		This contains details of a few children with no record but surmised to be a member of a family

addfam.txt		This contains details of families for which there is no direct evidence but which are surmised to exist

special.txt		This contains details of census households that have been listed as one family but which need to be
                                            separated
 
famind.txt		This contains pointers to families and is required by FAMGROUP

recind.txt		This contains pointers to records and is required by FAMGROUP

supagen.ids		This contains definitions of the databases to be used. It is an ASCII file

deathnot.txt	A list of annotations in Parish  burial registers that define relationships of the deceased

The following 7 assignment lists produced by hand from the suggestion lists

assnext.txt		Assignments of children to extras
assngir.txt 		Assignments of daughters to marriages of girls
assnboy.txt 		Assignments of daughters to marriages of girls
assnpfm.txt 		Assignments of sons to fathers of families
assndea.txt 		Assignments of children mother and fathers to death records
assnmot.txt 		Assignments of mothers of families to records in the mother list
assnfat.txt 		Assignments of fathers of families to records in the father list

The following binary files contain the raw information about the various categories of record

gampton.gro	GRO index and certificate data	BMD	
gampton.par	Parish registers 			XWF
gampton.cen	Census transc                                   C
gampton.mem	Memorial inscriptions		i

In addition, though not. used by FAMGROUP:

gampton.dir	directories etc		              E
gampton.all	marriage allegations		A
gampton.par       wills 				p			

3.4   Files output by FAMGROUP

Items of information required by the program are contained in several files.  Files with the extension .txt are all pure ASCII files, which may be printed and input into MS WORD

Files bearing other extensions are binary files that cannot be easily read.

The following suggestion files are written:

suggext.txt		Suggestion of children to extras
sugggir.txt 		Suggestion of daughters to marriages of girls
suggboy.txt 		Suggestion of sons to marriages of boys
suggpfm.txt 		Suggestion of sons to fathers of families
suggdea.txt 		Suggestion of children, mothers or fathers to death records
suggmot.txt	 	Suggestion of mothers of families to records in the mother list
suggfat.txt 		Suggestion of fathers of families to records in the father list

The following files are also produced

deathnot.txt
This contains the edited deathnotes from burial registers and memorial inscriptions (if any given)

bgmarrs.txt 
	This contain lists of every boy and girl marriage
For boy marriages it gives the family in which the groom was a child (if known) and was a father.
 
For girl marriages, it gives the family in which the bride was a daughter 

martofam.txt
This contains a list of every family, the birth year of the first child and the marriage year and RIN in identified

ukrecords.txt
	This contains details of every B,X,C record that could not be assigned

ukdeaths.txt
      	This contains a list of every D and F record that could not be assigned

famshort.txt
A list of the families giving the range, the number of children, the first names and birth years of both parents and the marriage RIN. It also gives the family in which the father was a child if known

It also gives statistics for the families

famlong.txt
A list of all families given for each the mother, father and children and all records in which these are the subject.
It gives the record number and full details of every record quoted.

interfmn.txt
In addition several lists of families and the children therein is produced at various stages of the program

errors.txt 
This is produced at stage CHKSUP
It contains a list of RIN supposedly referring to the same child, father or mother but which differ and duplication of a record

changess	An account of changes made in the family structure at various stages of the processing

secmar.txt
	A list of possible second marriages of father or mothers

3.5   COLLATE

COLLATE is a program which takes every record or selected records and lists them in alphabetical order of the first name.  Records with the same first name are sorted in chronological order of birth year (if this is not given it is treated as 0).  The list can be saved.

Records about the same person tend to be listed close together which facilitates the identification of the record.

There is also a facility to reallocate and edit PINs

There is also a facility to save a list of all used PINs together with the details of the person referenced in a file pindata.txt

3.6   FAMLOG

FAMGED is a program which produces a GEDCOM file which can be used to enter the data into any appropriate genealogical program

Input:
1.	pindata.txt produced by COLLATE        	A list of details of every PIN in use
2.	famgroup.fam produced by FAMGROUP        	Details of every family defined        
3.	maiden.dat
        	The maiden names of some wives
        
Output:

1.	ggg.ged 
        		The GEDCOM file

2.	ggg.err
        		Errors detected
        
3.	pinlst.txt
        		Details of every INDI in the GEDCOM file

Results and Discussion

The application of FAMGROUP to the GAMPTON database from 1600 - 2003 resulted in 109 families of which 16 were childless.  

Of the 973 records processed, all but  23 B, X, C and 43 D, F, I records were assigned to fathers, mothers or children of these families.

Of the 23 BXC records:  2 bear the name surname GAMTON,  have unusual first names and occur in unusual places'.  These are probably not clan members; 8 are GRO birth records and the remaining 15 are census records which provide no information of their family.

The 8 unassigned GRO birth records might be assigned to families if the certificates were to be purchased.    Four of them can be matched with an unassigned death records and one to an unassigned census record..
  
Of the  15 census records  4 are lodgers, servants (and a barman); two are a husband and wife and one can be matched to one of the birth records.

Of the 43 DFI records, 28 are funeral records from parish registers.; the remainder are 15 GRO death registrations, 4 of which can be matched with birth records and indicate that they refer to children who died in infancy.  .  In the case of  death records, the problem was not to find a person whose death was recorded but to decide which of several possibilities to choose. 

Of the 109 families, the number of families in which the father was a child was established was 71 (65%).  The number of families for which a likely marriage of the parents was found was  72 (66%).  The average number of children in a (non-childless) family was 3.5; the mean age difference between the mother and father was 4.0 years.  The mean age of men at their marriage was 27.2 years and for women, 24.1 years.  The mean generation gap between males was 34.2 years (i.e. there about 3 generation per century).

More tentatively we have concluded that 4 widowers and about 4 widows remarried.  One of the females who remarried is misclassify as a widow.  She had no first husband and her son was illegitimate.  It seems nevertheless that she married after the death of her infant

It remains to assess the validity of these results..  First we note that as the project developed, more data was occasionally found (as transcriptions became available on www.freeBMD, www.freeCEN and www.1837online).  These invariably proved to be consistent.   

We have not yet collected all available records. Most notably lacking are wills after 1856.  There were none found in PCC.

Nevertheless, some assignments were problematic and required assumption or divinations of transcription errors, the interchange of first and second names interchanged or nicknames substituted for official names.  In a few cases an assumption was made that a year was transcribed with an error of just 10 years.

We have linked many of the families by identifying the family in which the fathers were a children (see connections.doc).  If the name started with one family in GAMPTON in about 1400, we would expect all families to be linked to it by a chain of descent.  It is probably impossible to prove this since parish registers did not start until 1538.  At this time records seem to show that there were two clan families in Brixham.  Even so it is not possible to link in a convincing manner all clan members and we must assume that some events (Births, marriages, deaths) were not recorded in the parisg registers (at least in those we have searched).  This problem persists even intro the 20th century.  Whether this due to missing records, inadequate transcriptions, inadequate searches, changes of name, migrations or emigrations, we cannot say.  Maybe future research and the purchase of more certificates will clarify these issues.

Further problems arise from the methods  used in the reconstructions (as embodied in FAMGROUP and COLLATE).  Not all of the assignments made are certain.  Ultimately the reader must assess their validity for himself.   

Appendix

This appendix lists the criteria for the matches between targets and matches for the ten types of suggestion list (see section 2.6) and in the matching of marriages to the parents of the families. 2.7.5)

The following abbreviations are used

FY   Birth year of first child of a family
LY   Birth year of last child of a family
MY   Marriage year
BY   Birth year of a child
DY   Death year
RIN  Record identification code
PIN   Person identification code

BYT  Birth year in a target record
BYM Birth year in a match record

Marriages of parents of families

For each of the families, the first names of at least one parent and the birth years of the first and last child are known.  The marriages of the parents must be identified.

Target		Parents of family
Match:		Bride and groom of a marriage

For each family, we scan the list of marriages and attempt to match the bride and groom of the marriage to the parents of the family. 

 A match is registered if:
:
1.	The NINs of the father and groom agree
2.	The NINs of the mother and bride agree
3.	The year of the marriage was later than 9  years before the birth of the first child.
		MY > FY - 9
4.	The year of the marriage is earlier than 3  years after the birth of the first child 
	(to allow for a possible anticipation of the marriage)
		MY < FY + 3

This process does not generate a suggestion or assignment list.  The offsets of 3 and 9 years are adjusted to give sensible results.

Families to extras

	Target:	The person on the EXTRA list
	Match:	A child in some family

For each target, the families are scanned; then each child of the family is scanned.

A possible match is registered if:

1.	The NINs  of the child and extra agree
2.      	The BYT  of the extra was earlier than  three years after the BYM of the child.
		BYT  <  BYM +  3
3.      	The BYT  of the extra is later than three years before the BYM of the child.
		BYT  >  BYM +  3
Daughters to girl marriages

	Target:	The bride of a marriage of a clan girl
	Match:	A daughter in some family

	For each girl marriage, the children of each family are scanned.

A possible match is registered if:

2.	The daughter was at least 19 at the time of the marriage
		BYM  <  MY  - 19
3.	The daughter was no older than 45 at the time of the marriage (she had at least one child)	
	         	BYM  >  MY - 45
4.	The daughter was nor married at the time of the marriage

Sons to boy marriages

	Target:	The groom of a marriage of a clan boy	
	Match:	A son in some family

	For each boy marriage, the children of each family are scanned.

A possible match is registered if:

1.	The NINs of the groom and son match
2.	The son was at least 17 at the time of the marriage
		BY  < MY - 17
3.	The daughter was no older than 30 at the time of the marriage.
		BY > MY - 30

Sons to fathers of families

Target:		The fathers of each family
Match:		The sons of earlier families

For each family the children of earlier families were scanned

A possible match is registered if:

.	The NINs of the first names father of the (later) family and of the son agree
2.	The second name of initial (if any) of the first names father of the family and of the son 
               match
3.	The son was at least 17 at the start of the (later) family.
		FY > MY - 30
4.	The son was no more than 30 at the start of the family.
		LY < MY -1Deaths of Children, mothers and fathers

Deaths

Death notes

Records of death include GRO death registrations, GRO death certificates, Parish burial (funeral) records and memorial inscriptions.  Burial registers frequently contain marginal notes that specify the family of the deceased as do memorial inscription. Such textual information are referred to as death notes

Death notes may record the relationship of their subject to others members of their family and may specify:
a.  RIN of the record
b.  The relationship of the deceased to one or more other persons.
c.  The relations to whom the deceased is related

Death records

Target:		A death record
Match:		a.	A child of some family
		b.	The father of some family
		c.	The mother of some family

Note that a death may refer to a father AND to a son
 	                                  a mother OR a daughter, but not both

GRO index records and memorial inscriptions provide (after 1866, the age at death) the age of the deceased at death; these greatly facilitate the identification of their subject.

For each death, the fathers mothers and children of each family were searched.

Child match

Target:		A death record
Match:		A child of some family

For each death we search every child of every family. 

A possible child match was registered if:

1.      	The deceased was not a wife or widow as indicated in the deathnote
2.	The NINs of the deceased and the child agree
3.      	The second name initials (if given) are the same
4.      	The DY of the deceased (if given) was after the BY of the child
 		DY > BYM 
5.	The DY of the child was before than 90 year after the BY of the child
		DY < BYM  + 90
6.	The BYM of the child is later than 2 years before the birth year BYT (if any) given in the 
              death record.
		BYM > BYT - 2
7.	The BYM of the child is earlier than 2 years after the birth year BYT (if any) given in the 
              death record.
		BYM <  BYT + 2
8.	The DY is after all other records of the child
9.      	If the deceased is a SON or DAU as mentioned in a deathnote,   the first names given in the 
deathnote  matches those of  a parent  of   the child.

Mother match

Target:		A death record
Match:	.	The mother of some family

For each death we search the mothers of  every family. 

A possible mother match was registered if:
		
1.      	The deceased is female
2.     	The first NIN of the deceased matches that of the mother
3.      	The DY of the deceased was or after the BY of the mother's last child.
		DY > LY
4.	The DY was earlier than 65 years after the birth of the last child of the family
		DY < LY + 65
5.      	The BY (if given) of the deceased was later  than 45 years before the birth of the last
  	child of the family.
		BY > LY - 45
6.      	The BY (if given) of the deceased is not later than 17 years before the birth of the first
  	child of the family.
		BY < FY - 17
7.     	 If the deceased is a wife or widow (in deathnote), the NIN of the father matches that of the 
 husband given in the deathnote

Father match

Target:		A death record
Match:	.	The father of some family

For each death we search the fathers of  every family. 

A possible father match was registered if:
		
1.      	The deceased is male
2.     	The first NIN of the deceased matches that of the father
3.      	The DY of the deceased was in or after the BY of the family's last child.
		DY <  LY
4.	The DY was earlier than 70 years after the birth of the last child of the family
	  	DY <  FY + 70 
5.      	The BY (if given) of the deceased was later than 45 years before the birth of the last
  	child of the family.
		BY < LY - 45
6.      	The BY (if given) of the deceased was earlier than 17 years before the birth of the first
  	child of the family.
		BY < FY - 17
7.     	 If the deceased is a husband (in deathnote) the NIN of the mother matches that of the 
 wife given in the deathnote

Possible mothers to mothers of families

So far, we have only recorded the name, and possibly the marriage of the mothers of the families.  We must now list any other records in which they are the subject.  These are in the mother list and  include:
a.	GRO birth index references of females not bearing surname of clan
b.	Census listings  - of wives, widows or female heads bearing  the clan surname
c.	Unassigned female extras

Target:		Records in the mother list
Match		The mother of  a family

For each female on the mother list (MLF), each family was scanned and its mother (FAMM) tested for a match

A possible match was registered if:

1. 	The standard NINs of the mother (MLF)  matches that of the mother (FAMM) of the family
2.      	The birth year, of the mother (MLF), BYT was more than 16 years before the birth of the first
         	child of her family
	BYT < FY - 16 
3.	The birth year, of the mother (MLF) was less than 46 years before the birth of the first child of
 her   family
		BYT > LY - 46
4.      	The NIN of the husband  (of MLF; if defined) matches that of the father of the family
5.      	The surnames of the mother (MLF if married)  matches that of the father of  the family

Possible fathers to fathers of  families

So far, we have only recorded the name, and possibly the marriage of the fathers of the families.  We must now list any other records in which they may be the subject.  Such records were placed on the father list and include:
1.	Unassigned male extras

Target:		Person mention in the father list
Match:		Father of a family

For each man on the father list (FLM), each family was scanned and its father (FAMF) tested as a match

A possible match was registered if:

1.     	The NIN names of father (FLM) and match (FAMF)  agree
2.      	The birth year of the father (FLM)  was  earlier than 16 years before the birth of the first
child  of the family.
	BYT < FY -16
3.	The birth year of the father (FLM)  was later than 46  years before the birth of the first 
child of the family.
	BYT > FY - 46

Possible second marriages of fathers

A search was made for possible second marriages of fathers by first comparing the parents of every pair of families including childless ones).   Comparisons that satisfied the following criteria were listed as possible second families of fathers.

1.	The names of the father of the two families are known and the same2. 	The  year of death of the first mother must be before start of second family3.	The ages of fathers are both defined and equal within 2 years
4.	 Father is older than 20 & younger than 60 at both marriages 
5.	 Procreation range (the length of the period from the birth of the first child of the first family to the birth of the last child of the second must not exceed 50 years

Possible second marriages of mothers

Likewise, a search for  possible second marriages of mothers was made by trying to match the mother of each family to the marriage of a female (girl) GAMPTON.   Comparisons that satisfied the following criteria were listed as possible second families of mothers.

1.	The names of the mother and bride must be known and be the same
2.	The gap in years between the birth of the last child of the first family and the start of the second family must be  positive and not  more that 17 years
3.	The year of the marriage is after the birth of the  last child of the first family but not more than    20 years after
4.	The second marriage is after the death or last event of the father.  If this is not so it may indicate a second marriage after a divorce
5.	The bride has not been identified as the child of any family