2MAPPS Software Interface Specification DBM06 3.0  97/05/28

Interface Name:     DBMAN/DB Extended Bright Source Data Interface
Type of Interface:  Database (Informix) Field Data Specification

Written By:         DBMAN   _______________________________ T. Evans

Read By:            Informix DB

Description:  DBMAN loads 2MASS data into the Informix 2MASS database.  This 
SIS describes the DB fields (AKA "table columns") for the extended bright 
source (or "fuzzy stars") data.  These sources are too bright to be galaxies,
and thus have no extended src data elsewhere, but they also have extended 
emission around them.  Descriptions of other DB data are found in the other 
DBMxx SISs.  Also, information from each DBMAN run will also be written to a
UNIX summary file.

The DB table containing this data from survey scans is named "exbr_src", and
the table containing this data from calibration scans is named "exbr_src_c". 
Both are in the "tmass" DB.

Each source can be linked back to its own point src data through the hemis + 
date + scan + id "key".

If a field is not applicable or contains a "bad or N/A measurement value" (see
previous 2MAPPS SISs for details) for a certain source, the field will contain 
"NULL" values as defined by the DB.  

The descriptions below contain the following information:

1. "Name" contains the names of the DB fields or table columns.  Note that they
are all in lower case, because the DB doesn't distinguish between upper and 
lower case names.  If there is a number in parentheses after the name, please
refer to the numbered notes at the end of the descriptions for more information.
NOTE: The "cntr" column MUST be the first column in each table. 

2. "Description" contains short descriptions of the field contents.

3. "Units" contains the units of the values in the fields.

4. "DBType" contains the DB data storage types for the fields.  Note that some 
data types are further defined by values in parentheses following the type name.
Also, these types are NOT cast in stone and could change, especially for the 
position fields.

5. "Null" indicates (y/n) whether the DB fields accept NULL values.

6. "Idx" contains a code indicating whether fields are indexed and what type
of indexes they have.  If the code is "0", the field is not indexed.  If it
is "1", the field has a simple index.  If there is a "u" after the digit(s),
the index is a "unique" one.  If the code has a 2-digit number, the first digit
indicates to which composite index the field belongs, and the second digit
indicates the ordering of the fields within the composite index. 

7. "Fmt" contains a C-like description of the best formats for displaying the
field contents, *excluding* a leading space for field separation.

8. "Tbl" contains the (sub-)table ID to which the fields belong.
NOTE: The "cntr" field will be the first field in each sub-table, and is used
as a join index.  The 1st sub-table ("01") is the "main" sub-table, and must
contain one entry per table cntr number; any other sub-table will not contain 
an entry for a cntr number if its fields would all be NULL.

9. "Min" and "Std" indicate (y/n) whether the DB fields are found in the "mini"
and "standard" table output views.

NOTE:  A line beginning with "-------" can only be used herein to delineate the
section of field/data dictionary lines seen below.

Name               Description                                                  Units  DBType      Null Idx Fmt               Tbl Min Std
-----------------------------------------------------------------------------------------------------------------------------------------
cntr               entry counter (key) number (unique within table)             -      integer       n   1u 8d                 01   y   y
hemis              hemisphere (N/S) of observation                              -      char(1)       n  21u 1s                 01   n   y
date               observation date                                             -      date          n  22u yymmdd             01   n   y
scan               scan number (unique within date)                             -      smallint      n  23u 3hd                01   n   y
id                 2MASS source ID number                                       -      integer       n  24u 6d                 01   y   y
sigma              global background sigma                                      DN     decimal(5,3)  n   1  6.3f               01   y   y
subdiff1           local background deviation from global background            -      decimal(5,3)  n   1  6.3f               01   n   y
subdiff2           2nd local background deviation from global background        -      decimal(5,3)  n   1  6.3f               01   n   y
flg                description flag                                             -      smallint      n   0  1d                 01   y   y
pts_key        (1) key to point src data DB record                              -      integer       n   0  9d                 01   n   n
-----------------------------------------------------------------------------------------------------------------------------------------
total # columns = 10, # bytes/row = 33
-----------------------------------------------------------------------------------------------------------------------------------------

NOTES:

(1)Point src record key: no default (non-null)
   The pts_key field will be set to the key of the record containing the point
   src data (see SIS DBM01).  The point src data will also have the same date,
   hemisphere, scan, id keys.