Thomas Delbridge LHNP-9N6 - implications of correcting wrong information on tree
Thomas Delbridge (ref LHNP-9N6) is recorded on the Family Tree as being born in Dunster, England in 1756. Our Dunster parish records confirm that he was baptised on 3 March 1756, son of John Delbridge, and also show that he was buried six days later, on 9 March 1756. However, according to the Family Tree he didn't die until 1845, in Virginia, USA, and was married, and raised several children in Meherrin County. There's no doubt that the Virginian Thomas Delbridge did exist, but certainly he wasn't the one born in Dunster in 1756 - and in fact the 1840 Virginia census says he was born about 1766 anyway.
LHNP-9N6 is actually two separate people, one born in Dunster, and the other one who was probably born in 1766 but origins and ancestry currently unknown.
I'm new to this database, and want to understand what will happen if I start to correct this (assuming that I can…). If I add the 1756 burial to Thomas's burial, will the alleged marriage and children automatically be disconnected? Or should I start by amending the records to say LHNP-9N6 is place of birth unknown, and add a new person Thomas as the son of John b. Dunster 1756? The latter seems the logical thing to do, but I would appreciate some guidance before I screw things up.
Best Answer
-
@BarbaraHoffbauer
Welcome to the FamilySearch Community and the joys (?) of the FamilySearch tree.Nothing will be changed "automatically."
When you add the death to Thomas, the first thing that will happen is an alert from the DQS (Data Quality Score) about events (marriage and children) after his death.
The best first step is a review of the change log - looking for a previous merge of two or more profiles of the same name. I took a quick look, but you'll want to review in detail.
If there is nothing good to be found on the profiles that have been merged away, I usually try to create a new separate profile of the same name as a place to attach the records that belong to that "other" Thomas. It's a good practice, for the sake of the greater tree, and can help keep future contributors from recreating a family that doesn't belong.
If you need more help, please feel free to say, and some of the experienced community members will surely assist.1
