My paternal grandparents and their children are mentioned in the Tennesseans' Old Hickory News column a number of times during the 25+ years in which they lived in Old Hickory Tennessee. While searching at Newspapers.com for my aunt Viola Cook, I noticed a paper from the day my Dad, her youngest brother, was born. The search result from that edition pointed to a notice of members of the Sunset Club who were having birthdays on that day. Among those listed was a Viola Cook of Old Hickory who was celebrating her 16th birthday. Wait a minute... My Aunt Viola would turn 15 in 1930, not 16. Not only that, but her birthday was on June 12th. Could this be my Aunt Vi or another Viola Cook? I've searched the census records for 1930 to try and locate another Viola Cook in Old Hickory Tennessee who was that age. I did find one in Davidson County but not in Old Hickory community. A check of that Viola's records revealed that while she was born in the right year to be the one mentioned in the article, her birth month was February. I may never know why her name is listed or if that is MY Viola Cook. If it is Aunt Vi, I'm sure there is a very interesting story behind all of this.
Earlier today I received notification via email that FamilyTreeDNA has made some changes that will bring them in compliance with the new European data protection law known as the General Data Protection Regulation (GDPR). If you have an account or accounts with them you should have received this notice. Check your Spam folder or filters if you haven't received a copy.
Changes to these settings will take effect May 28, 2018.
Includes Changes to the Following:
Privacy & Sharing--The ability to opt out of match email notification but still participate in matching.
Project Preferences--The ability to select an access level for each individual Group Administrator.
Email Notifications--Same as mentioned under Privacy & Sharing
Updates to Account Information, and Genealogy sections of the My Profile page.
While you are logged on checking out the settings, you might as well make sure you have assigned a beneficiary for your account. Also, please fill in the info for your earliest known ancestor if you can and make sure you are using the correct ancestors. See my previous blog post on this topic.
When sorting thru DNA matches at AncestryDNA, I like to note the connection for each of my matches as being thru the ancestors of one of my four Grandparents. Both my parents have ancestors who were in Tennessee in the early 1800s. Most of the time I will only be connected to the match on one side. There a few times when I will have multiple connections. See the example below with Bill who shares matches with me who are from my PGF's Mom(King/Manire) and my MGF's Mom(Pittman/Adcock) He has no tree and trying to figure this one out will take seeing the segments in a chromosome browser.
Thru my admin and shared links, I can tell how much DNA Bill shares with Me, my sister, and my mother. Unfortunately, we did not begin DNA testing until after my Dad had passed so he was never tested.
Bill's match with Me
Shared matches only show those in common who share at a 4th cousin level(Ancestry's minimum for 4th cousins is 20 cMs) I noticed that my Mom isn't listed as a shared match.
Bill's match with my Mom
After looking at Mom's amount of shared DNA with Bill, I'm really hoping I will be able to check this match in a chromosome browser so I can identify the grandparent(s) who passed on the 2 segments I received. On checking Bill's match with my sister's test it appears they do not share any DNA within the range that Ancestry would report. This is a good example of randomness of DNA inheritance. I've written to Bill and asked if he was planning on uploading to GEDmatch, MyHeritage or FTDNA. Hopefully, I will get the opportunity to view the segments in a chromosome browser and see what occurred.