Monday, November 14, 2016

I Started a We're Related Mobile App Cousin Relationship Table

I've been writing weekly about the additions to the list of cousins on the We're Related mobile app - see This Week's We're Related Cousin Relationships for an example.

My friend Russ Worthington has made a cousin relationship table, and is even adding his cousin relationships to an Ancestry Member Tree, and using the Hints to try to support the cousin relationships that he receives on the mobile app.  See his blog for more details -

I haven't gone that far, but I do usually click on the lineage for the purported cousin and see if it makes sense to me.  In some cases, I have gone into FamilySearch Family Tree, and WikiTree to determine if the lineage there is the same, and if the lineage "looks right."  Ideally, each step in the lineage should be researched, but I don't want to take the time right now.

I do check the line that the app shows for my lineage, and in several instances it has added one or more generations and found ancestors that I do not have in my Ancestry Member Tree.  When that happens, I look closer at the purported ancestor of mine in the records.  I have not found one new ancestor doing this yet - almost all of the relationships that I don't have in my tree cannot be supported by records and good judgment.

I now have over 50 cousin relationships from the mobile app, and I cannot recall what I've investigated, so I made a cousin relationship table in Microsoft Word from the app information, and added a comment column so that I know what I've investigated.

Here are three screen shots of my tables:

Of the 52 relationships provided so far, 20 of them are Facebook friends.

As you can see, I have questioned the information of 8 of the relationships.  I probably need to be more consistent in my comments.

Only 11 of my common ancestors are from my mother's side of the family, and all but two of those are from New England.  However, three of them are in my "Unlikely" category.  My father was from New England so that makes some sense.  Maybe I should color code the grandparents line.

What else should I add to this table?  It is for my own use so that I can keep track of what I'm getting, and I probably won't add to the table forever, but it's a start.  It took about an hour this afternoon to make and if I get 10 to 15 new cousin relationships each week, adding them will not be an onerous task.


The URL for this post is:

Copyright (c) 2016, Randall J. Seaver

Please comment on this post on the website by clicking the URL above and then the "Comments" link at the bottom of each post.  Share it on Twitter, Facebook, Google+ or Pinterest using the icons below.  Or contact me by email at


Unknown said...

Great idea! Think I'll make a table too. Much easier to keep track of yes-related, no, and maybe.

M. Diane Rogers said...

I must get an up to date phone so I can try this. But I may be a little concerned about who the rellies might be.

Karen said...

Our connection is more likely correct than not at least on my side. The hiccup on my line is between the 2 David Niles. David Niles the younger was illegitimate. Preponderance of the evidence leads to the general consensus that David Niles the elder is his father. However, there is no definitive proof of that. I'll take you as a cousin any day regardless!!!

J. Paul Hawthorne said...

Great idea, Randy! I just made my spreadsheet which you can see here:

Jane said...

Randy, to get relationship results for Facebook friends, do both people have to have this app? I don't (and don't have a smart phone), but I believe we are related several ways.

Randy Seaver said...

Jane, I don't think so. I think we have to have Ancestry Member Trees and be Facebook friends. Somehow, Ancestry knows that a person on Facebook has an Ancestry Member Tree.

Team Spice said...

So the first table is from the Richmond/White line? How can I isolate that. I find it pretty interesting. After this election, doesn't this show us that we are far more connected than we are divided? :)