DNA_Tag Table

The DNA_Tag table is the unified, cross-service store of tags applied to tests and matches. Each row records one named tag, attached either to a test or to a match, for one testing company. Tags mirror the labels a service lets you put on a match (or test) so they can be filtered and analyzed alongside the rest of the gathered data.

Test tags vs. match tags. Some services tag by test and others tag by match. As the schema notes: A* applies tags by test id, so for A* rows the testguid is set; for services that tag by match id (such as GEDmatch-style services), testguid will be null and matchguid identifies the tagged match instead.

Column Reference

Column	Type	Description
Id	int (PK)	Auto-incrementing primary key.
company	string	The testing company the tag belongs to.
testguid	string	The tagged test’s GUID. A* tags by test id, so this is set for A*; it is null for services that tag by match id.
matchguid	string	The tagged match’s GUID. Used by services that tag by match id.
name	string	The tag’s name/label.
created_date	string	When the tag row was first recorded.

How It’s Populated

Tags are written through a single shared routine. It looks for an existing row matching company, matchguid, testguid, and name; if none exists the tag is inserted, otherwise the existing row is updated while preserving its original created_date. The supporting index covers (company, matchguid, testguid, name).

Related Tables

DNA_Kits — the kit registry; a tag’s testguid corresponds to a kit’s GUID.
Per-service match tables — the match records a tag’s matchguid refers to (for example the A* match group rows).