[TASS] Variable Star Database Tables

[Michael Gutzwiller <deepsky@FUSE.NET>]

As I promised in an earlier email I've created a first pass on database
tables for TASS variable stars.  There are two IE diagrams attached, a
logical and a physical model of the tables I'm proposing and how they fit in
with the current schema.

Each of the tables is explained below:

TASS_cat:  This is an existing table.  It may be the TenXCat table instead.

Person:  This is an existing table, or at least an existing script.  It is
currently not on Michael's machine but the script exists and I propose not
changing it, just populating it.  For the purposes of variable star analysis
anyone who wanted to could add themselves to the table.

KnownVariable:  This table has all the known variables, probably populated
with the GCVS and possibly augmented from other sources.

AnalystTeam:  A group of one or more Persons who are analyzing the TASS
database for variable stars.  The name field is just an arbitrary name the
group gives themselves.

AnalystTeamPerson: Maintains the many to many relationship between the
AnalystTeam and Person tables, this implies a person may be member of many
teams and a team may have many persons.

Candidate:  An entry in the TASS database chosen as interesting by the
AnalystTeam.  It is just marked as interesting by whatever criteria the team
choses.  Any team can mark any TASS_cat item as a candidate.

RejectedCandidate:  This is an entry created by the analyst team to indicate
misleading candidates.  These may represent contaminated stars which vary in
brightness in RA or Dec due to a nearby bright star, etc.

Promoter:  A selected Person who can promote a candidate to a TASSVariable.

TASSVariable:  An entry from the Candidate table that has been promoted to a
full fledged Variable found by TASS.

Publication:  A publication that describes or mentions a particular
TASSVariable.

VariablePublication:  Maintains the many to many relationship between a
TASSVariable and a Publication.  A variable may appear in many publications
and a publication can contain many variables.

The following relationships can be enforced by the database:

* The promoter of a variable may not be a member of the AnalystTeam.
* A promoter can only be entered by Michael or some other trusted person.
(This is our list of bishops.)
* Many analyst teams may claim a single tass id but the system sets the date
found value (via a trigger).
* Only one TASS variable may exist for a single tass id.

The three levels of candiates are:

1.  Candidate found by a team.
2.  Candidate promoted to TASS variable.
3.  Candidate published.

Let me know of any comments or suggestions.

Mike G.

variable_logical.gif

variable_physical.gif