April 17 updates

[Darren]

Hello all, just wanted to pass along some updates. The engineering team is working on integrating all of the Big Y SNPs automatically into the Y-DNA Haplotree. It is a bigger project than they had initially projected so it is taking longer than they would like.

Group Admins now should be able to place orders on invoice. If you do not see the Bill Me Later option next to the billing information when placing an order, please contact the helpdesk and include your GAP Username and the engineering team can get this added for you.

Character limit for naming a project subgroup has increased from 100 to 160.

Project admins will now receive email notifications again when results are posted as well as the option of obtaining a copy of a join request email when they send it to a prospective member.

Ability to convert or roll back a project to and from myGroups has been restored.

-Darren
Family Tree DNA

[gtc]

And once again, thank you very much for the information.

Please keep it coming. It makes a big difference.

[Earl Davis]

Thanks Darren.

Positive news.

Earl.

[wkauffman]

Hello all, just wanted to pass along some updates. The engineering team is working on integrating all of the Big Y SNPs automatically into the Y-DNA Haplotree. It is a bigger project than they had initially projected so it is taking longer than they would like.
--SNIP--

-Darren
Family Tree DNA

I would advise letting the major haplogroup admins review the results of your solution for rolling Big-Y SNPs and INDELs into the FTDNA version of haplotree.

There are some items like
1) removal of inconsistent novel SNPs from consideration. One needs to look across Big-Y results to determine consistency and not just rely on the quality calls present within the single Big-Y result being merged into a tree,
2) selection of a SNP to define a haplogroup level. Don't choose the first one. The chosen SNP should be testable by both Sanger and SNP chip based technologies,
3) include INDELs. There are a few that are relevant for defining clades,
4) selection rule for which existing name L, S, Z, FGC, BY, ... will be used as the primary node name,

which should be considered when new results are merged into a tree. The L21 and U106 regions have solid methodology and determined tree structures in place. Make sure what is rolled out is in agreement with these research efforts have established. FTDNA does not need yet another flubbed feature rollout to occur.