Family tree index
This page links via an A-Z index to the many family trees on Jerripedia. You can also access these trees and discover more family information on the Family pages.
At 21 September 2018 the number of trees was
Origins of names
The derivation of many of the surnames is explained in our family pages and others can be found in an article by George Balleine, and further articles have been added on Old family names of the Channel Islands and Jersey names of French origin. However, just because a Jersey's ancestor's name sounds French, does not mean that it is necessarily a long-established island surname, or even originates in France. Read The perils of French sounding names.
Jersey was a French-speaking island (both true French and the Jerriais patois) until well into the 19th century. Some country families did not have English as their main language until the late 20th century and the business of the States and publication of its laws were in French until early in that century. Consequently, the vast majority of children born in the island were given French personal names to go with their, largely, French surnames. This only began to change in the 19th century. As far as possible the members of the family trees in this section of Jerripedia are shown with the names they were baptised with, but if these trees have been copied by those who submitted them from trees published elsewhere, it is possible that anglicised versions of the correct French names will have been used.
Dates given in the family trees are for birth and death, where known, but might be for baptism and burial. These events almost always followed birth and death within a week, but sometimes baptisms may have been delayed, usually only by a few weeks, but perhaps longer if the parents were away from Jersey and had one or more children baptised there on their return.
We rarely indicate in a tree that dates are approximate because this might lead researchers to believe that other dates are accurate: all dates, particularly pre-1650, should be treated as approximate.
Beware of dates which look too evenly spaced to be true - they probably are not. Children in a large family were rarely born every second year; nor did son follow father, and grandfather and great-grandfather at exact intervals of 20, 25 or 30 years. When you encounter such regular gaps it is likely that this is an attempt by a researcher to show approximate dates within a known timespan for several generations.
Do not assume that two or more children in a family who are shown as having the same birth year are necessarily twins, triplets, etc. Again, this may be because the author of the tree does not know exactly when they were born. When we are happy that two children were twins, we add this to the tree.
Jerripedia's trees come from a wide variety of sources. The earliest added to the site in 2010 resulted from the research by members of the original editorial team into their own ancestry. Trees from Payne's Armorial of Jersey were added next, and since then there has been a steady flow of trees submitted by Jerripedia users, or assembled by us from parish records.
Wherever possible trees have been cross-checked with other sources, including (since 2012) our database of church records of baptisms, marriages and burials. We also cross-reference submitted trees with online sources, but never rely exclusively on online trees, unless they have been compiled by a small number of researchers into Channel Island families, in whose work we have total confidence.
We have researched a substantial number of trees from the family history section of Jersey Archive and the library of La Société Jersiaise. Many of these have been deposited by individual researchers, whereas others are the results of work by members of the research teams of the Channel Island Family History Society and La Société. These trees are treated in the same way as submitted trees and are checked with other sources wherever possible.
We do not list sources within individual trees, partly because the software on which this site is based does not lend itself to the same approach as that adopted by Ancestry (for example), but mainly because the work involved would detract from our objective, which is to provide as many family trees as we possibly can, in a format which is easy to consult and to levels of accuracy which meet our high standards.
Although we make every effort to ensure the accuracy of our family trees, they should be treated with the same degree of healthy scepticism as any other genealogical information on the Web. But there are two important differences between our trees and those you will find on other sites. First: our site is available for everybody to view with no charge. Second: all our trees are now checked before they are posted, or immediately after they have been added by contributors who are not part of our editorial team. They are checked against other online trees, against church and public registry records, against census returns, and any other relevant records.
When trees, or sections of a tree, are believed to be particularly suspect, a note is added to the tree. Sometimes those notes invite researchers to treat the trees with extreme caution, and it might be questioned why they have then been included in the site.
The answer is that anybody is entitled, as a registered user, to add any content to the site. When family historians prefer to send their trees to Jerripedia's editoral team for formatting and addition to the site, we believe that they are entitled to expect that their material will be included as if they had added it themselves. The editorial team reserves the privilege, however, to add cautionary notes to any tree, however it has been submitted.
If Jerripedia editors had to guarantee the accuracy of every tree presented, there would be no trees on the site. They are presented as a guide to family historians, who should always attempt to find as many alternative sources as possible and to get back to primary records where they exist.
When errors are identified in trees our policy is not to delete them but to add a clear note warning of the probable inaccuracy. Sometimes such notes are in turn challenged and some of the trees on the site contain an ongoing debate about their content, with the current content reflecting the editors' view of the most likely relationships.
For this reason, if you believe that you have identified any errors in these trees, please do not make changes yourself (except to correct an obvious typographical error) but click on the 'Discussion' tab at the top of the page and leave the information you have (or send it to email@example.com - please use Jerripedia as the subject of your email). This will be picked up by site editors and either the changes you suggest will be made to the relevant pages, or you will be contacted by email for further discussion. This does not prevent anyone registered as a contributor adding new trees by creating a link under the appropriate family page. You can add trees in any format you wish, but we do not have a facility for importing Gedcoms, so trees must be in a format which can be imported from a text editor. See Adding your family tree for guidance.
When new trees are now added to the site, links are created backwards and forwards with trees containing spouses, or other relations. This did not happen in the early days of Jerripedia and we embarked on the lengthy process of creating links between what are now nearly 3,000 trees in the site. Where the spouse of a member of one tree can be identified in their own family's tree, a link is created in each direction.
This is a very time-consuming process, and we have stopped the process of working through from A to Z, partly because we believe that it is of greater value to our users to concentrate on the addition of new trees and establish links to them while they are being processed, and partly because many new trees were added earlier in the A-Z index than we were reaching by working down the index. On opening older trees to insert links to new ones, we often take the opportunity to link to other existing trees, where we know that relationships exist. Also, when we access an old tree, we are taking the opportunity to format it to match our new style, and open it to make other necessary changes.
It is important to note that when the name of an individual shown as a spouse in one tree is also found in their own family tree, it cannot always be certain that they are one and the same person. If both trees show the same names and dates in the marriage, it can be reasonably assumed that they are the same people. Where full correspondence of names and dates is not available the link will be qualified as either possible or probable, depending on the amount of information available. Researchers who come across a link they believe to be inaccurate are asked to please draw the attention of the editor to the problem by leaving a message under the appropriate page's 'discussion' tab.
Treatment of new material
- Important note
Our policy in the past has been to create new trees, even when submitted trees are more or less a mirror copy of existing trees, but we have decided to change this approach from June 2018. We are now more likely to add any information which is new to expand an existing tree. Only when there is a substantial amount of new information will we create a new tree.
Not only will this reduce the workload of our editorial team, but it will help to reduce the number of trees researchers need to study to obtain all the available information for a family lineage. We will not delete any existing trees which overlap, but the policy change will affect most new trees submitted to us.
That does not mean that new trees are any less welcome, and if submitters are anxious that they should be included in full rather than new information being added to other trees, their wishes will be respected.