Gather_History Table

The Gather_History table records the history of gather requests run in the DNAGedcom Client. Each row represents one gather request for one kit — what was requested, when it ran, and summary metrics about the data that was collected. It is used to populate the gather history view and per-kit gather summaries.

Column Reference

Request Details

Column	Type	Description
Id	int (PK)	Auto-incrementing primary key
company	string	The service the gather ran against (Ancestry, FTDNA, MyHeritage, GEDmatch, 23andMe)
kitIdentifier	string	Identifier of the kit being gathered
kitDescription	string	Friendly description / name of the kit
userID	string	The service account user ID used for the gather

Requested Options

Column	Type	Description
gatherICW	bool	Whether In-Common-With (shared match) gathering was requested
gatherChromo	bool	Whether chromosome / segment gathering was requested
gatherTree	bool	Whether tree gathering was requested
minCM	decimal	Minimum shared cM threshold requested for the gather
maxCM	decimal	Maximum shared cM threshold requested for the gather

Timing

Column	Type	Description
requestDate	DateTime	When the gather was requested / queued
startDate	DateTime	When the gather actually started running (shows as “Pending” until set)
endDate	DateTime	When the gather finished

Result Metrics

Column	Type	Description
metricMinCM	decimal	Lowest shared cM actually seen among gathered matches
metricMaxCM	decimal	Highest shared cM actually seen among gathered matches
metricMatchCount	int	Number of matches gathered
metricICWCount	int	Number of ICW (shared match) records gathered
metricChromoCount	int	Number of chromosome / segment records gathered
metricTreeCount	int	Number of tree records gathered

How It’s Populated

A row is inserted when a gather is requested (requestDate set, startDate still pending). As the gather runs, the record is updated, and when it completes the row is finalized with the actual startDate, endDate, and the result metrics. The gather history view reads these rows ordered by requestDate descending, and a separate summary query rolls them up per kit (latest request date, max/min cM, and the largest match / ICW / chromosome / tree counts seen).

Related Tables

• DNA_Schedule — recurring gather schedules, which share the same request fields (company, kit, options, cM range).
• DNA_Process — lower-level record of an individual gather process run with timing and parameters.
• DNA_Kits — the kits that gathers are run against.