LivingDNA update

 I don't pay that much attention to the "ethnicity", aka Bio-geographical, estimates from the assorted companies I and many cousins have tested with as I'm having way too much fun comparing trees and mapping chromosomes to ancestral lines in order to focus on those matches that just have to be from somewhere on one or other of my brickwalls.

But a recent question on the DNA-Newbies list at Groups.IO prompted me to review if LivingDNA had added anything new into the equation with their update (about a year ago)

My original results may be found here although the link to the share within that post only seems to partially work now.

Now they look like this:

ie rather harder to distinguish visually which regions are strongest in my ancestry by their calculations.

Clicking on a region brings up a potted history of the region from the Ice Age to medieval times

The detailed breakdown by region comparison is

2017

              :

Feb 2020 

So I'm even more of a mongrel with less idea than before of where in particular to look to solve my brickwalls!

The Scottish groups are now more combined than they were.

I've been mining the shared matches between pairs of 2nd and 3rd cousins in our match lists for clues.

This amorphous mess of "Scottish" is well supported by practically all of these shared matches showing up as personal pile-up regions where there are an absolute heap of triangulating matches and the likely common ancestor back beyond our paper trails spreading out from the known ancestry in Perthshire / Stirlingshire to  include Argyll, Dumfriesshire and down to Lanarkshire.

And then there's that persistent percentage of Irish all companies give us - only 4% on LivingDNA 18 on Ancestry.

Every so often however I do manage to link trees of matches together and still hope that one day, I'll have some answers, or at least clues on which branch to target for yDNA or mtDNA to support my findings.

Anyone got a stray Archibald Henderson or Amelia Millar they want a home for?

Or a yDNA Jenkins or Buchanan to see where that might lead? ( yDNA testers wanted refers)

Amelia Millar brickwall review

 

Cracking this brickwall was one of my main aims for entering DNA testing way back in 2007.
And still is.
I've never been brave enough to tally up the $$ for kits I've sponsored for descendants over the years, particularly as the initial tests were so much more expensive than now.
Many of these people are no longer with us, but their DNA lives on in our match lists to provide excellent clues for the more recent generations.

Test the relatives in your earliest generations NOW before it is too late.

My four-pronged approach towards cracking this brickwall is covered under the following headings, which I do admit make this all sound rather more systematic than I am in reality.

1. Review of research into likely families 
2. mtDNA match review
3. atDNA matches likely to be from Amelia
4. Recreation of the DNA of Amelia

1) Review of research into likely families 

Genealogy and DNA go hand in hand. 

Most of us "working" the DNA for all the clues we can mine spend a LOT of time researching / checking / creating the trees of our matches to see if the DNA is coming from where we hope/think/are being hinted at it being.  

To which every so often I add general research into Millar/Miller, Chrystal families in the right areas (Kippen, Gargunnock, Kilmadock, Fintry) "just in case" something I've missed now makes more sense with any additional information acquired.
Those more likely looking candidates usually get "tidied up" on the FamilySearch tree, and added to WikiTree, potentially being included as a link to my WikiTree Amelia Millar Brickwall page there via a "category" link.

One day someone will pop up with family information on the missing link(s).

 

2) mtDNA match review

From our one mtDNA tested descendant we believe Amelia Millar's mitochondrial haplogroup to be T2e.

FamilyTreeDNA (FTDNA) sends notifications when a new match is found.
Although the chances of a relevant, close, genealogically significant match popping up un-prompted are slim, I always check to see how close, what they have entered as their most distant maternal ancestor, or what can be determined about their tree.

To date we have no exact matches (Genetic Distance of 0).

 

If you have tested either y- or mt- DNA do please make sure that you have completed the details on your profile under

Account Settings > Genealogy > Earliest Known Ancestors

where there are places to record both your Direct Paternal and Direct Maternal Ancestors

These are respectively your father's father's father's .... father

and your mother's mother's mother's ... mother

and must be male and female respectively.

eg

  

you'd be amazed at how many show their most distant maternal ancestor as male!

The entry here is what shows on the public mtDNA results pages for any projects you have joined (if you have elected to share your results), and is what your matches see about you on their match list.

 

The hope here is that one day I'll track down a direct female line descendant of the most likely families (hopefully a Chrystal) and they'll turn out to be haplogroup T2e to add to any additional evidence from autosomal matches and research eg.

3) atDNA matches likely to be from Amelia

We have a large number of  tested descendants of James Henderson and Amelia Millar and thus a large number of shared matches to work with, but as yet no real way of reliably separating the matches between the two given that 3 out of 4 of the parents of this couple are puzzles* and the fourth known branch is getting a bit far back to reliably get strong autosomal matches that can be proven to be from the McEwan DNA.

We do have some however, so, as always, I live in hope.

 

It doesn't help that this area of Perthshire/Stirlingshire has fairly inter-connnected families.

Just how much that is impacting the match lists is starting to become even more apparent now that Ancestry is actually showing us how much they have down-weighted matches below 90cM by applying their Timber** algorithm to remove the DNA that they've determined is less genealogically significant from the displayed match strength.

Where I could check Ancestry matches on other sites they were generally coming up at least slightly larger elsewhere.

But where I couldn't check elsewhere I was completely in the dark - until now.

 

So it can be a tad hard to separate out the matches relating to Amelia's DNA from that of James'.

 

*James' father is documented as Archibald Henderson but we have a yDNA discontinuity between the 3 (matching) yDNA tested descendants of James and the single yDNA tested descendant of the only one of his paper trail brother's that I've managed to find and convince to test.

 

** The "Timber" algorithm is explained in detail in the Matching White Paper that is available under Ancestry's DNA help - click on the ? top right on your DNA Matches box on the DNA home page.

 

Which pre-amble leads to 4).

4) Recreation of the DNA of Amelia

This aspect of the search is making me feel like an archaeologist digging up mammoths and trying to create a living one from their DNA. I do so hope Amelia would be amused!

So it's time to make all those DNA tests work even harder (payback time <g>).

Cue Borland  Genetics.

I'm in the process of publicizing to tested descendants of James and Amelia (Millar) Henderson that they can help this endeavour by uploading their DNA file to BorlandGenetics from wherever they tested and to let me know they have done so.

I can then invite them to a private Henderson-Millar project there for their DNA to be used in this reconstruction of the DNA of our shared ancestors.

Hopefully with enough in the pool we will get a reasonable amount of DNA that can be used to begin creating ancestral DNA profiles, AND also be able to use the output for use on Genetic Affairs and/or DNAGEDCOM for  clustering reports of the resultant matches.

The site offers you matching as well as advanced tools such as the above, which I've only just begun exploring.
Have a read.

If you are comfortable with the terms and conditions, and privacy aspects outlined on the site, contribute your DNA and we'll see how far we can get creating DNA profiles for James and Amelia.

It would be good to narrow down some options for her parents / ancestry.

Summary

Join me in this fascinating, and very frustrating but absorbing, journey

-  by testing your oldest generations of Henderson/Millar descendants and 

- upload to sites where their DNA can be compared across companies - ie GEDmatch and BorlandGenetics

- extend the connected pedigrees on the very DNA friendly collaborative WikiTree (see my Amelia Millar brickwall category page with some families of interest)

One day we WILL know who Amelia's family was.

New year, new updates

2020 is starting off a lot better than 2019.
Not that I make resolutions for a New Year as I'll only break them within the first few days (no chocolate? pay more attention to housework?) I do tend to check what hasn't been updated lately.

My gateway web pages (LornaHen) the related more detailed family website (BigBrother) and the basic BDM snapshots of the deceased rellies and their connections (RootsWeb Worldconnect replacement) have all had a refresh.
It's been a while and several links had become obsolete or unworkable (WorldConnect in particular, why did they change it? It's not for the better.).
Research has also moved on and new connections made. You all know how genealogy and DNA goes!

Perhaps the revitalization from a New Year will also extend to the long overdue updates to DNASurnames, and the Fairbairn and Runciman sites as there have definitely been new findings in the first two in particular with BigY results arriving.

It's not that there hasn't been any activity, just that what has been updated has mostly been tidied up on the FamilySearch tree and WikiTree, as have a lot of DNA connection investigations.

For the more intriguing of the latter I've started using WikiTree custom pages to keep track of the connected families and DNA conclusions as a result of the investigations.

WikiTree allows you to create custom pages for anything you wish and operates a category system to link profiles of interest.
Most of these are eg by place, surname, one name studies etc which have a monitored hierarchy but can also include Personal Categories which you link to yourself as the main grouping.

If a person on WikiTree has been associated with a category a tiny almost invisible link will appear at the top of their profile page

clicking on the link takes you to the bottom of the page where there is a list of categories associated with the person, eg my fledgling investigation into what I hope will be new Turnbull matches

One resolution I have made, is to review my chromosome maps and hopefully show progress since last year. 

and for the downside....

For the second time on FamilySearch the same person has (re)merged my paternal grandfather with his namesake born in the same month and year, despite my collaborative note - which is now yet more detailed as to why NOT to merge them.

They were born a fortnight apart, one registered in Oamaru, the other in Palmerston North, ie separate islands of New Zealand.
The separate NZ Historical BDM index entries show their different parents had been added to a note on each, but that didn't deter this person.
Yes on the surface it looks like the one who married first may have moved islands and remarried but he didn't. He remarried a bit further north.
It doesn't help that the older fiche birth indexes for New Zealand don't make it easy to find them to add the place details to the exact birth dates and parents available from the Historical BDM index online at the Dept of Internal Affairs.
Both are indexed as Archifold Hinderson instead of Archibald Henderson!

This time I've added yet more research into the note on both profiles.
The North Islander has been placed safely up in Te Kuiti with his 2nd wife in the 1919 electoral roll, his father's obit has been added  as well, which places him in Cambridge (Waikato, North Island) whilst my granddad is recorded down in Woodhaugh, Dunedin in 1919 with his first and only wife Agnes later moving to Roxburgh, Otago (South Island).
I do know that he once ventured north, at least as far as Wellington, on his honeymoon, but he did not already have a son by then, at least not Cyril.

I've also sent the chap a message via FamilySearch to PLEASE STOP merging these Archibalds.

WikiTree has also been updated with a disambiguation note on Granddad, with the other chap now also added there, he is after all nearly family - his son married my mother's 2nd cousin!
But there are other things I'd rather have been researching last night in the time spent doing the additional research that should, hopefully STOP the "helpful" person from merging them again.

Thankfully such persistance is rare, and an apology has just been received.

This does not detract from the overall benefit of sharing tree research.
We do not own our ancestors but we do owe it to them to be remembered accurately.

Such trees do tend to get better over time as duplications are reduced, research notes added etc.

Just the other day I was re-examining the scant tree of a DNA match on Ancestry wondering where his missing link to my DAWE family was and this time round, someone had added exactly the link I was missing.
The FamilySearch tree has now been extended to link him back to the rest of his ancestors already there.
This allowed me to breakthrough that mystery and connect in a newfound 3rd cousin thanks to both DNA and the collaborative tree at FamilySearch.

So mark your key people to be "Watched" so you can keep an eye on changes, you never know what you will learn, or who you will "meet" as a result.

Collaborative trees - the upside

Many of you may already have realised I'm a great fan of collaborative trees, WikiTree and FamilySearch in particular.

The downsides (enthusiastic newbies connecting up families with the scantest of evidence, or agin the evidence without a thought) are far far outweighed by the benefits of sharing.

Examples of both hit home strongly last night. (See next post for yesterday's example of the downside.)

For the huge plus side, my weekly Watch list email from FamilySearch highlighted that someone had added both a previously unknown child to the family of my 4x great grandparents Archibald Fairbain and Alison Crosser, and a baptism source for my 3x great grandfather Walter. (FamilySearch / WikiTree)

Which latter in particular is a bit embarrassing.

After all my research into Fairbairns you'd think I'd have gone back and rechecked my early work looking for the gaps that could now be filled.

There he is, baptized just across the border in Norham.
Which fits his 1841 census entry saying he was born in England, even if he did recant on that by 1851.

It's hardly an out of the way place for them to have been.
Courtesy of google we can see that it was 4 miles between Norham and Swinton where by the time the 1851 census came round Walter said he was born, having forgotten that 10 years earlier he'd said "England".

Unfortunately, there appear to only be the two baptisms there, no marriage for Archibald and Alison to fill that record gap, but also none for the presumed eldest son Archibald to contradict that he is the one baptized in Whitsome & Hilton, Berwickshire in 1783. :)
There seems to be only one other Fairbairn baptizing his children around this timeframe (1760 to 1800), a Thomas, with a William and an Ann.

Thank you to the person updating the Fairbairn tree that brought this to my attention.
Updates will ensue on WikiTree (done) and my Webpages
 

Amelia's turn

Haven't posted for a while so you'll have to believe me that I've been busy behind the scenes, just not publishing.

For nigh on the last two years we've been working on a Mystery Grandfather case that took a few twists and turns, throwing up a few curve balls along the way, particularly in the tree of one of the closer matches which resulted in the case being extended to two Mystery Grandfathers.
With that now behind us, case solved as best it can be, it's time to return to my own brickwalls, particularly given the demolishing of the Jane GIBSON brickwall last October.

So now I'm trying to concentrate on Amelia MILLAR born Kippen, Stirlingshire, see suggested, rather empty, pedigree below, and follow progress of research on DNA suggested connections at my WikiTree page for this brickwall.
It could take some time, particularly as it is often not yet clear if the DNA matches being investigated come from Amelia's DNA or James' - which latter can be consigned to a subsequent investigation.
My main problem - staying focused!!

embeddable family tree updated live from WikiTree

Maternal side Chromosome Map update

I see that my Paternal side chromosome map was last published Dec 2016.
The intention was for the companion Maternal side map to follow shortly thereafter, but 2017 had other plans.

Click to enlarge

A quick reminder for myself of the maternal brickwall ancestors that I hope DNA will one day aid in cracking (see embedded WikiTree Widgets below for each of my maternal grandparent's pedigrees):

• Jane GIBSON: supposedly born Martock, Somerset in 1812, married Simon ANDREWS in Martock, 1840 and emigrates to New Zealand on the "Timandra", arriving 1842.
• William AUSTIN: husband of Emma Parker CLINTON - disappears after arrival in Australia;  Emma remarries as a spinster with no children!
• William CLINTON: married Jemima PARKER in London, 1810 - and had the above daughter Emma Parker CLINTON

Way too many unknown grandparent segments as yet - but I hope that visual phasing* of my 3 first cousins' DNA will reduce that.
*Visual phasing links:

• https://isogg.org/wiki/Visual_phasing
• http://thegeneticgenealogist.com/2016/11/21/visual-phasing-an-example-part-1-of-5/
• https://genealogylady.net/2017/05/02/down-the-dna-rabbit-hole-visual-phasing-with-two-siblings/
• https://www.youtube.com/watch?v=neB4oFlwJHA
  a hint: to mark who owns each crossover instead of the technique shown I used the owner's letter in a simple right justified cell which positioned the owner right next to the line.

My maternal grandfather's pedigree (WikiTree) - if you are a descendant of any of these PLEASE upload your autosomal DNA file (eg FamilyFinder from FamilyTreeDNA, Ancestry, MyHeritage, 23andme) to GEDMatch.com and contact me.
Every little clue helps.

embeddable family tree updated live from WikiTree

 My maternal grandmother's pedigree (WikiTree)

embeddable family tree updated live from WikiTree

How many to go?

As you can probably deduce, I'm a DNA junkie.
Apart from using my autosomal DNA matches (and a lot of genealogical research) to map my chromosomes so that I know (eventually - I hope!) which bits on which chromosomes were inherited from which ancestors*, another of my aims to is document the haplogroups for each of my ancestors out to my 2*great grandparents (at least) -  yDNA and/or mtDNA.

Knowing this data is of help in working with autosomal DNA matches to rule in or out of contention certain lines, and you never do know what else you may learn.

So I thought it was time to take stock.
The above is a screen shot of my ancestry tree pedigree with the symbols I've attached for the appropriate haplogroups where known.

How am I doing?
Grandparents: one to go, George Ernest ANDREWS.
There's a test in progress for a descendant of Simon ANDREWS, due next month.

Great Grandparents: two to go, other than George Gibson ANDREWS who will be sorted next month.
Helen Sinton WIGHT (WorldConnect / WikiTree / Geni / FamilySearch) and
Ellen TURNBULL (WorldConnect / WikiTree / Geni / FamilySearch.

Can you help?
Concentrating on Helen Sinton WIGHT first.
Helen Sinton WIGHT has no living descendants who inherited her mitochondrial DNA.
Working back to her mother, Helen WIGHT nee SINTON (my webpages / WorldConnect / WikiTree) there may be some options, but although (or because) this WIGHT family is the one that started my whole genealogy journey back in the 1970s, it is the least documented, and very poorly sourced given how new I was to this back then! 

Can YOU help by contributing any knowledge you have on descendants of Helen?
The three main collaborative world trees that anyone can access for free, that I follow and work with are: WikiTree, Geni and FamilySearch.
Let's see if we can turn up any living descendants down any of the lines in general, hopefully at least one in particular that carries Helen's mitochondrial DNA AND one who may be convinced to indulge my curiousity.

Both WikiTree and Geni have DNA related tools that can be quickly checked for DNA candidates of interest - and easily rechecked as the tree grows:
WikiTree -  descendants of Helen who have inherited her mtDNA a short list - but I am working on an update as we speak. None on the current list are still with us, and the first two branches I've worked on don't appear to have any likely surviving candidates for mtDNA.
Geni - living descendants of Helen who have inherited her mtDNA (none as at Jul 2016)
FamilySearch - descendants of Helen WIGHT nee SINTON

Regardless of this specific quest for mitochondrial DNA candidates, there may well be some cousins still around who would be most welcome to contribute autosomal DNA and see what that adds to our overall DNA knowledge of connections.
Pop along to my atDNA project FFLornaHen on FamilyTreeDNA and order a FamilyFinder test, or test at Ancestry and then transfer that file to both GEDMatch.comhttp://GEDMatch.com and to FamilyTreeDNA so we can all fish in both ponds for matches and use the tools only available on the latter two sites to make the most of our investment(s).
I'd love to hear from any of you - contact form on most of my webpages.

* the main aim of all that work with my atDNA is to concentrate on the matches at the spots where I don't yet know which ancestor is to blame - can you hear the sounds of the crumbling brickwalls?
A wonderful side effect is of course confirming the family tree, testing theories, and as recently highlighted, finding new siblings for some of the ancestors.
Some of the distant cousins you get to "meet" may even be able to shed more light on our shared ancestors with photos, family knowledge etc.

BINGO

For quite some years I've been trying to determine the fate of William the brother of my 2* great grandfather James HENDERSON. They were the sons of Archibald, a smith at the Bridge of Allan, Stirlingshire. who sprang into existence from apparently nowhere in time to be paid for smithing work in the Stirling of Keir estates and to marry in 1804 to Margaret McEWAN.

Back in 1994 a researcher in Australia contacted one of my cousins about her husband's ancestor William HENDERSON, who had married a Margaret SINCLAIR, and whose family had emigrated to Australia.
The data shown was, however, that for a different HENDERSON family back up the chain.
Time passed.
A couple of years ago I got more stubborn about trying to find any signs of "my" William having survived beyond his baptism and found a smith at the Bridge of Allan with a wife Margaret that just "felt right" - you know how it is when you get a feeling about a family, even if you can't find proof :)

As I dug away discovering his family I was reminded of the 1994 letter, dug it out, and sure enough, the descendants matched but the parents given for William didn't.

Back at Christmas time Diane contacted me about this family on WikiTree, kindly providing some modern day updates.
But even better, her husband was willing to humour me in seeing if we could prove his ancestor William was indeed brother of my James.
No Y-DNA candidates appear to be available so we used atDNA with our  fingers firmly crossed that even though the odds of a specific pair of 4th cousins actually turning up a detectable atDNA match were only 50%.
With all the HENDERSON kits we have on file, surely one would match?
Results are just in.
Given the subject line of this post, I think you already know the outcome!
We have significant matches with one descendant of William and James' sister Margaret, and 8 significant segment matches with 7 descendants of my James (including to me).
I think I've definitely found William.
(I don't yet know if the tree of our 1994 correspondent has changed tack over the years)

The HENDERSON chromosome map will be updated shortly (to also include results from another of James' descendants)

Build your own "luck"

Isn't it  amazing we get lucky in this genie hunt - by working hard!

Keep notes on all the potentially interesting snippets when you find them and you never know when you'll get lucky after all.
Some years ago I noted a newspaper obituary for a William SINTON who had died in Birkenhead (Cheshire) having served 20 years as chief engineer for the Ocean S.S. Co.
Never could find him in a census to figure out who he was.

I'm currently checking off assorted old SINTON research to upload more to WikiTree. In particular at the moment, the children of John SINTON & Alison HALL.
Amongst whom were a William and Elizabeth with nothing known beyond the 1851 census in Lismore & Appin (Argyll).

Something brought me back to the above obituary so I decided to explore further.
With probate information now more readily available I quickly found that he was married to an Elizabeth Formby HALSALL.
William was obviously home from his travels at regular intervals, as although he didn't appear in any census, Elizabeth shows up with a growing family over the years.
The first child was called Mary Hall SINTON, so this was looking a rather likely lead as to the fate of William.
Then in the 1871 census, who should show up living with wife Elizabeth but a "sister" Elizabeth SINTON, of the right age, and shown as born Scotland.

Bingo. Two birds one stone.

Parents with a sense of humour?

Who needs them?
Having found yet another Family Finder DNA match amongst my Devonshire DAWEs, I've been checking off my data to upload a few more of my DAWE family to WikiTree.
Checking the marriage of Charles FLOOD I found his father was one Noah FLOOD.
Back at the  turn of the 19th Century when Noah would have been growing up, I wonder if he was teased unmercifully?

The newly identified Family Finder DNA match is the second descendant of Isaac & Sarah (SMITH) DAWE's son William DAWE who is a match to 3 of the descendants of William's brother Isaac Smith DAWE so we have some DAWE, or SMITH, autosomal DNA that has survived down to present day over 6 generations.

How well do you know your cousin?

Better than one of mine does possibly?
I recently uploaded a branch of the RICHARDSONs to WikiTree, three generations down from John & Elizabeth (SHIEL) RICHARDSON, and let the small group of interested parties know it was there in case they wanted to use WikiTree's excellent privacy and trust controls to connect themselves up to their ancestors.
One of them emailed me with some updates, which were duly incorporated into my own database. 
I thanked her, commenting that her dates differed in a couple of instances. 
“No my cousin’s birthday is definitely 20th October.” 
The next day, another email arrived. “I’ve just checked with my mother and found I’ve been sending my cousin her birthday card a day late my entire adult life. She’s going to be rather surprised when I finally get it right for her 50th birthday.”
Gave us both a good chuckle for the day.

WikiTree & DNA

Ever since this post back in 2011 I've continued to sporadically use WikiTree.
Mainly as I "finish" a particular line and want to see what pops out, but also for research I've done for others, where they can then continue the tree on their own.

Over the last week that has been a concerted effort as my interest went up several notches.

Yes, it has always been a great collaborative site for a One World Tree,  ie everyone connected, and only appearing once (all going well!);
Yes it has always been Free;
Yes it has great privacy controls;
Yes it has a great range of navigation options - with dinky little icons for pedigrees, descendant lists etc;

Now however it has completely grabbed my attention as some tools have been added that help those of us trying to find our DNA matches.

If you've ventured into genetic genealogy and don't know where to find your matches, convince them to upload at least their pedigree to WikiTree AND enter which DNA test they've taken in the place provided (you can enter your name as Anonymous and restrict who can see what, but without a visible tree the main benefit of this may be a little compromised).

All the people impacted by the test will get a link posted against their profile (= page = person) saying It may be possible to confirm family relationships with (person x) by comparing against (link to test taker's name) (link to the test taken) test.

Read this article about which of the affected relations get the note added to them.

With the randomness of autosomal dna inheritance being explored using tests such as FamilyFinder (Family Tree DNA) or 23andme, anything that helps find where a match might be is most welcome.
None of this shows actual DNA results, only family tree connections with links to test taker and those impacted. It is up to you how much more you wish to share, eg in the free text biography section.

Even if you aren't interested in the DNA results, the note draws attention to possible newfound relations on a branch one or other of you may not have.

PS if thinking about venturing into genetic genealogy, now's a great time, Family Tree DNA are having a summer sale - details on my DNASurnames Blog.

Course over, play time

As part of a course I gave last week on using online family trees (notes in process of being shifted to here), I had a play with WikiTree.
It's a collaborative tree, so you can really only do one automatic gedcom upload, preferably only for a small manageable section of your tree that you're prepared to monitor and merge in duplicates when you find rellies also working there that you can collaborate with.
Thereafter maintenance should be manual. Read their help files.
This is an experiment with their embeddable widgets, which update when the base data they come from is updated.

embeddable family tree updated live from WikiTree

And for my main HENDERSON brick wall where the gaps would be great to be filled in...

embeddable family tree updated live from WikiTree