How to Deal With Conflicting Dates in Genealogy.

One of the most frustrating things that can happen when you’re researching family history is a conflict in dates, most commonly for births, but also sometimes for marriages and deaths. When presented with two or more possible dates you have to try and work out which one is true, or at least the most likely, as in some cases you’ll never know with absolute certainty.
Gregorian and Julian Calendars
One great source of confusion came when Britain adopted the Gregorian calendar and abandoned the Julian calendar which had been in existence for centuries. That happened in 1752.It meant a jump of several days in the calendar took place in September, so the final day under the Julian system was Wednesday, September 2, which was followed by Thursday, September 14. If you find dates marked OS, this indicates the date given is under the Julian system. When researching in this time period, the sudden leap can be disorienting. If the birth came before 1752, the date should be under the Julian system, but if the records you’re consulting are later, there might well be a discrepancy of several days. By adjusting the date to allow for the different system you might be able to reconcile the differences.
Sources
When faced with conflicting dates you need to consider the sources you have. The closer you are to a primary source, the greater the likelihood of the date being correct. A birth certificate, for example, is the ideal primary source for establishing when someone was born. The dates in a family Bible, by contrast, can’t be trusted to the same extent as you have no idea when they were written down.Similarly, although it’s an official document, a death certificate can’t be seen as a primary source for a birth date, as the official filling it in is simply going on information he receives from relatives of the deceased, which might not be accurate.
Parish registers are far from primary sources when it comes to births. The birth dates that are in them are given orally and so aren’t necessarily precise. Remember, too, that when working with baptismal registers, these record the date of baptism, not of birth.
Whenever possible, take the extra time to search for primary sources, or at least as close as you can get. If you have a handwritten copy of a primary source, remember that there’s still room for error in it, so you should treat it as a secondary source of information and keep trying to find the original.
Time
The greater the time between an event and when it was recorded makes the accuracy more questionable. Memories could be faulty, for instance, there could be confusion, or simply the wrong information has been passed to someone. Ideally the event should have been recorded within days of happening, or at most within weeks.Transcription Problems
When records are transcribed, whether in the past on paper, or by hand for inclusion in a database, there’s the possibility of human error. Someone can type the date wrongly, people can be confused between the way dates are written in Europe and America; there are any number of possibilities. As stated, any transcription is a secondary source, and should be treated with a degree of superstition.Resolving Problems
When faced with documents showing different dates for an event (and it’s more likely to be a birth than anything else), look at what you have before you. Is one a primary source, or something close to it, such as a transcription? What is the second document, and when did it originate?How great is the discrepancy? If it’s simply a matter of days, then by discovering other sources you might be able to achieve a consensus on the particular day. Where it’s larger, meaning months or years, then you have to evaluate the sources and see what else you can find.
Where you can find nothing else that can corroborate one date or the other, you need to look for other documents, such as a record of death or marriage, that can help shed light on the problem. These are secondary sources when it comes to birth dates, but they can help to resolve things.
No Resolution
There may be times when it’s impossible to find a definitive answer, or even one that seems likely. The evidence you need might not be extant or might never have existed (this will involve records before 1837, when births, deaths and marriage were centrally recorded). In instances like these you have no choice but to continue searching quietly and record both dates, assigning precedence to the one that seems more likely.Business Energy With a Difference
If you are looking for business energy or need advanced solutions like remote energy monitoring, new supplies, downgrading or upgrading capacity, have a no obligation chat with Purely Energy.
To find our more get in touch here. or call 0161 521 3400.
- Genealogy and a Criminal Past
- How to Deal With Conflicting Dates in Genealogy.
- Tracing the Female Line in your Ancestry
- How to Use Obituaries for Study
- Taking a Genealogy Course
- What's at the National Archive?
- Using the International Genealogical Index
- Using Local Libraries as Sources
- How Do You Know When You've Really Hit a Dead End?
- The Increase in Online Genealogical Resources
- Researching British Genealogy from Abroad
- The Importance of the 1911 Census
- Do You Need a Professional Genealogist?
- Latin In Church and Legal Records
- The Family Bible In Genealogy
- Genealogy And Military Records
- How To Find And Use Medieval Genealogy Information
- The Importance of the Protestation in Genealogy
- Checking Taxation Records for Family History Research
- Sharing The Results Of Your Genealogy Research
- Using Criminal Records For Family History Research
- How Museum Collections Can Help You In Genealogy
- Poor Law Records and Tracing Your Family Tree
- Surname Variations When Tracing Your Family Tree
- Tracing Ancestors Transported to the Colonies as Criminals
- Tracing Family History On The Female Side
- Using Geographical Maps to Trace Family History
- Using The Internet to Trace Your Ancestors
- Utilising Local History To Research Your Family Tree
- Genealogy and Medical Records