How to deal with obvious errors in family trees?
Guidance for how to deal with obvious errors in family trees and entries is needed.
There can be many ERRORS in the records of "Deceased" individuals/persons in "Family Tree" of 'FamilySearch' ...
Question: What sorts of 'obvious' errors are you referring to?
Knowing that; and, having an understanding of the 'obvious' errors, would help us better advise you.
this is an "open" database - that each user can correct and update.
not some static database set in stone.
each entry has edit features that can be used to correct any errors.
let us know which entry in the database you are referring to.0
I don't know how new you are to FamilySearch and the massive tree that is called Family Tree. If you are new, welcome to a public forum we we users do our best to help each other. We've been told that each discussion thread is read by FamilySearch personnel, but due to time restraints, they may or may not respond.
FamilySearch FamilyTree is a Single tree that is built on an open-edit concept. The idea is that eventually one profile will exist for each person who has lived and died and will be as complete as possible and eventually, it will be as accurate as records allow.
Most people who create a profile for a deceased person or enter / change information in an existing profile believe they are related to the person whose record is being impacted. The information they provide may be correct or be erroneous. Your question deals with what to do about errors (it really doesn't matter if they are obvious or not) that are discovered.
Here is what I have found to be largely effective.
- I make sure each person's record is as complete as possible with regard to available records, whether those records are found in FamilySearch, some other site, or where the person lived.
- Then I worry about what is correct and what is incorrect and why, if incorrect, it is incorrect. The source of the bad data may be a bogus genealogy, produced by a fraudulent "genealogist," such as Gustave Anjou. It may be based upon an incomplete or erroneous application to an organization, such as the American Daughters of the Revolution. It may be the result of mistakes while copying information from other sources. It may be because some person's "family historian" just knows that their information is correct.
- If I determine that a recent change (within the past month) was made that introduced errors into the record, then I'll use the internal FamilySearch messaging system and include at least some of the following
- Thanks for doing your best to make the record as complete as possible
- Changes that you have made that are problematical (and why they are problematical).
- What I have done to correct the problem and why I did it.
- An invitation to collaborate with respect to our common relative's record.
- Thanking them again for their efforts.
- I do not expect a response for a number of reasons, most of which have to do with the person who made the changes may not be a regular contributor to the massive tree.
The above is a shortened version of what I've used in the past. Hopefully, it will help others collaborate with respect to common relatives and producing a complete record.0
I can't figure out how to correct my aunt's name on her profile. Her profile is https://www.familysearch.org/tree/person/sources/GW38-3ZJ and her correct name is Jewel Dean Burnett. Leona is not her first name and Deen is misspelled. Thanks for any help.0
When indexing, what do you do with the date of birth of still born children? Do you put the year of the record, or leave it as not recorded?0
I used Legacy 9 and it's Family Search conections to update members of my tree last night and now my tree is a total disaster, full of duplicate entries, mangled entries and absolute garbage. How can I delete all these errors or remove everything I've done and start again?0
Mick, your question is quite a bit different than the one this topic is based on. To do your question more justice, please start a new topic with a title something like "Help, Import of data to Family Search from Legacy 9 has messed up the data in the FamilyTree". You could just copy and paste the content of your original question here into that new posting.
That may give you more visibility and allow a dedicated space for Legacy 9 import problems that may exist. This is important because the makers of Legacy 9 may have a bug in their interface software with the FS API. If that is the case it has the potential for many Legacy people damaging the FSFT. Also having "Legacy 9" in the total of the post may alert Legacy developers who sometimes monitor these forums as well as others who may be using Legacy.0