Some people eat, sleep and chew gum, I do genealogy and write...

Sunday, July 15, 2018

Returning to the Challenges of Francis Cooke

Week after week as I receive an email generated from the Family Tree about those whom I am watching, I see almost constant changes to people such as the Mayflower passenger Francis Cooke. Insanity is often defined as extreme foolishness or irrationality. I think this definition applies to those who feel that they need to keep editing a prominent person. It boggles my mind to think that there are so many people out there in the greater genealogical community that know so little about history and particularly about New England history to think that they have "discovered" some new information for a person such as a Mayflower passenger.

Notes, life sketches, memories, documents, and dozens of source do not seem to make an impact on the waves of changes. Of course, all of these "changes" also fail to be supported by even one source. Fortunately, there is a small group of people who ardently defend the reality of the entries and change everything entered back to conform with the more than well established and sourced information.

For example, there is some who added a birth date for Francis Cooke of 1 October 1577 and further shows he was born in Gides Hall, Essex, England. In fact, no new sources have been added to his entries for at least a year and there are no records showing a birth or christening record for Francis Cooke. The Gides Hall records date from the 1700s and show a person named Francis Cooke marrying a woman named Hester on 2 November 1766. Remember, the Mayflower arrived in America in 1620.

These few entries in my Family Tree take up an inordinate amount of time and effort just to maintain the status quo. Over the years, there has been some discussion about making such entries read-only or locked, but that presupposes that the information is complete and correct at the time the entries are locked.

There are presently 1357 people in the Family Tree with the name of Francis Cooke.

As an example, one of them was born in England in 1566 and supposedly died in Boston, Suffolk, Massachusetts, United States in 1675.

He apparently lived to be 109 years old. There are no sources listed for this person. By the way, the actual entry and the search listing do not agree. The entry is for Francis Cooks KGS8-47J.

Usually, when I write a post like this one, I get several suggestions to make my views known in GetSatisfaction. There are presently 4929 topics on just the Family Tree in GetSatisfaction. The total number of topics is 12,209. Am I supposed to search through all these topics to see if this issue has already been raised? Should I start a new topic?

Well, I did search and, as I already knew, found that this topic has been around for at least five years or more. It also turns out that one of the people who commented on this problem is the same person who is cleaning up Francis Cooke today. So some of us have been working on this same issue for many years.

By the way, the response here outlines several options for limiting these irrational changes. This is only one of the many similar topics.

Now, short of requiring a psych evaluation for potential users of the program are there any other ways that the number of changes to these prominent people can be reduced?

I don't have an answer that is any different than all the different responses in GetSatisfaction. But I do know that I will outlast those who are making irrational changes and I already have assistance from a 2nd generation and will now start working on the third generation of those who will defend the integrity of the Family Tree.


  1. This is exactly why there needs to be a robust system of editorial control for the FamilySearch Family Tree. I once suggested different classes of users. People such as yourself, who have demonstrated thorough understanding of the research process, could receive unlimited editing privileges. Others should be restricted in the kinds of profiles they can alter, though anyone could be free to make suggestions for changes on any profile. Or something along these lines.

    Until the developers of the FSFT are willing to seriously face the realities you mention, progress will be strenuous and slow, and much work will be wasted.

    1. That option has certainly been raised many times. But who would select the classes of users?