We already have a standard to store autosomal DNA match data, namely as notes of associations (person references) of type DNA. This standard was introduced by the segment map Gramplet and Gramps Web adheres to it.
Next, I’d like to define a standard for storing Y-DNA SNP data, which can be used to determine the Y-DNA haplogroup. In this case, it’s not about matches between two people, but about a list of positively or negatively tested SNPs of a single individual. The typical format is the one used e.g. by the YSEQ clade finder: M343+, L21+, DF13+, DF23+, M222-, ...
My preferred candidate at the moment is a person attribute of the custom type YDNA and the SNPs as value. But there are many other possibilities. Person notes, person attribute notes, …
Any opinions?
I wrote some code about ten years ago in response to feature request #8919 - “Add ability to record Genetic information eg: Haplogroup”.
It uses the person attributes “yDNA” and “mtDNA” to record haplogroups.
To record test results, we created an event type called “DNA Test”. This allows you to store details such as the testing company, the test ordered and the date of the test etc… The results are stored in person reference attributes with one attribute per genetic marker. This included STR as well as SNP data.
Some users created Forms to help them enter the data quickly. @RenTheRoot may be interested in this.
My original segment map code was further developed by @GaryGriffin.
1 Like
Cool, good to know, and it looks like attributes are the right track. I am not sure but I suspect 8 years ago Y-DNA was mostly about STRs, while now it’s more about SNPs… Perhaps we need a more specific attribute type like ySNP. I would have put all SNPs (several hundred) into a single attribute rather than hundreds of attributes of the same type to avoid clutter. Was that also the approach back then?
The additions I made did not involve the DNA Test event.
The DNA Test event had attributes, each was a STR. But I am not aware that anyone utilized it. I implemented as the following, but it was a dead end.
You are right that this does not scale well, so I never pursued it.
1 Like
