DNA_Schedule Table

The DNA_Schedule table defines recurring, unattended gathers. Each row is one schedule: which kit to gather, how often and at what time, which optional passes to include, and the cM range to use. The app reads these rows to run gathers automatically without manual intervention.

Internal credential storage. Because scheduled gathers run unattended, each schedule stores the credentials needed to sign in: userID and password. This is internal storage within the DNAGedcom Client; the password column holds the password value associated with the scheduled login.

Column Reference

Column	Type	Description
Id	int (PK)	Auto-incrementing primary key.
recurType	string	The recurrence type (for example the unit of repetition, such as daily or weekly).
recurValue	string	The recurrence value that goes with `recurType` (for example which day or interval).
runTime	string	The time of day the scheduled gather should run.
company	string	The testing company to gather from.
kitIdentifier	string	The kit to gather (its identifier).
kitDescription	string	A human-readable description of the kit.
userID	string	The account user ID used to sign in for the gather.
password	string	The password value associated with the scheduled login.
gatherICW	bool	True to include an in-common-with (shared match) pass.
gatherChromo	bool	True to include a chromosome/segment pass.
gatherTree	bool	True to include a tree-gathering pass.
minCM	int	The minimum centimorgan threshold for the gather.
maxCM	int	The maximum centimorgan threshold for the gather.

How It’s Populated

Schedules are saved with an insert-or-replace, so updating a schedule overwrites its existing row. The app loads all rows to determine which gathers are due to run.

Related Tables

DNA_Kits — the kit registry; company and kitIdentifier identify the kit to gather.
DNA_Login — the cross-service credential registry used for interactive gathers.
Gather_History — records each gather’s request/start/end times and result metrics, including those produced by scheduled runs.