HelpDatabase Reference › MeAnd23W_Matches

MeAnd23W_Matches Table

The MeAnd23W_Matches table holds 23andMe DNA relative (match) data captured by the older 23andMe import path. Each row represents one match for one 23andMe profile.

Legacy table: MeAnd23W_Matches is populated only by the original (pre-redesign) 23andMe Relative Finder import. It has been replaced by MeAnd23W_Relatives, which the current browser-based gather writes to. When the client detects the current (“New”) 23andMe format, the legacy import returns immediately and no rows are written here. Treat this table as historical: existing databases may still contain rows, but new gathers populate MeAnd23W_Relatives instead.

How It’s Populated

The legacy import fetches the Relative Finder match list in a single batch and writes one row per match. Unlike the current table, there are no separate per-match gather steps feeding extra columns — everything below comes straight from the match-list response, and haplogroups arrive inline with the list (rather than from a dedicated step). The same data is also written to a CSV export.

psid is the 23andMe profile ID — the profile/kit being gathered. ehid is the match’s profile/share identifier.

Column Reference

Identifiers

ColumnTypeDescription
Idint (PK)Auto-incrementing primary key
loginUsernamestringDNAGedcom username who gathered this data
psidstringThe 23andMe profile ID being gathered (the profile/kit whose matches these are)
ehidstringThe match’s profile/share identifier
eidstringMatch profile ID
eiidstringSecondary match identifier
NamestringMatch’s full display name
firststringFirst name (or first initial if private)
laststringLast name (or last initial if private)
urlstringMatch’s profile URL
imgstringURL to the match’s profile image

Relationship & DNA

ColumnTypeDescription
RelationshipstringUser-set / overridden relationship label
PredictedRelationshipstring23andMe’s algorithm-predicted relationship label
PredictedRangestringPredicted relationship range
DNASharedstringShared DNA percentage (the legacy “pct” value)
SegmentsSharedstringNumber of shared DNA segments
patsidstringPaternal-side flag
matsidestringMaternal-side flag
rel_userstringUser/overridden relationship code
rel_algstringAlgorithm-predicted relationship code

Haplogroups

ColumnTypeDescription
MaternalHaplogroupstringMaternal (mtDNA) haplogroup. In the legacy import this arrives inline with the match list.
PaternalHaplogroupstringPaternal (Y-DNA) haplogroup. In the legacy import this arrives inline with the match list.

Profile & Biographical

ColumnTypeDescription
SexstringMatch’s sex
BirthYearstringBirth year
BirthplacestringBirthplace
ResidencestringCurrent location
AncestrystringAncestry summary text
FamilySurnamesstringFamily surnames the match listed
FamilyLocationsstringFamily locations the match listed
NotesstringNote / description text for the match

Sharing & Contact

ColumnTypeDescription
SharingStatusstringSharing status
IntroductionStatusstringIntroduction / communication status
can_resendstringWhether an introduction can be re-sent
resend_datestringDate an introduction may be re-sent

Gather Tracking

ColumnTypeDescription
addedstringDate the match was added / opted in
created_datestringDate this record was created (gather timestamp)
visiblestringVisibility flag
discstringDiscovery / legacy flag
syncstringSync status flag (“0” until uploaded)

Data Preservation Rules

The legacy import inserts a match only if no existing row has the same Name; if a row with that name already exists, the incoming record is skipped entirely (no update). This is a simpler, name-only de-duplication than the (psid, ehid) keying used by MeAnd23W_Relatives, and it means matches that share a name can collide.

Related Tables

  • MeAnd23W_Relatives — the current, comprehensive relatives table that replaced this one.
  • MeAnd23W_ICW — In Common With data (shared matches between two people).
  • MeAnd23W_FIANew — chromosome segment data.
  • MeAnd23W_Triag — triangulation results between matches.