List of tables
ALIASES
AREAS
BBCVT
CHCODES
CLASSES
COMTYPES
DATACOLS
DATASTYP
DCDTNOTS
DEBUG
DENSDATA
ELEVSRCS
FAMGRPS
FAMILIES
FASIGN
FEDSTAT
FEEDBACK
FIELDATA
GENERA
GUYINFO
GUYPLTCT
INANAREA
INFRASP
ITEMTYPS
KEYVIOL
KINGDOMS
KV*
MONUNITS
NESW
NOTES
ORDERS
ORIGINS
PHYLDIVS
PLOTDATA
PLOTS
PRJDSTMU
PROJECTS
RECORDRS
SELDCOMS
SELDDSTS
SELDFAMG
SELDFAMS
SELDFSS
SELDGENR
SELDISLS
SELDORGN
SELDPRJS
SELDTAXA
STATIONS
SYSTMDOC
TAXA
TAXAUTHS
TAXONCOD
THRETMON
TNCNOTES
TRANSECS
TRANTYPS
USFWSRAR
USFWSTAS
WEEDDATA
User-defined ad hoc tables
- ALIASES: The ALIASES table is part of the system documentation, and contains descriptions of
various PDOXWIN aliases which may be used in association with the
database. (See PDOXWIN documentation for information about aliases.)
Go back to diagram
- AREAS: This table
contains descriptions of the general geographic areas in which project
data is taken. Go back to diagram
- BBCVT: The BBCVT
table contains data allowing conversion of Braun-Blanquet categories to
midpoint values of those categories for use in certain types of
calculations. (NOTE: Be SURE that your use of these values is
statistically valid! It's tricky...!) Go back to
diagram
- CHCODES: The
CHCODES table contains information about "Critical habitat?" codes: e.g. es,
critical habitat has been designated; o, it hasn't; critical habitat
designation is ot pplicable for this entity; or critical habitat
designation is unknown/unresearched for the corresponding entity
(species). Go back to diagram
- CLASSES: The CLASSES
table contains information about all taxonomic classes in the database;
all class-related information should be stored in this table. Go back to diagram
- COMTYPES: Community
types table: includes codes & descriptions of community types; each
record in PLOTS.DB is assigned one of these community types. Go back to diagram
- DATACOLS: The
DATACOLS table includes information about particular DATA COLlection
effort(s). It specifies, in particular, the DATA SET TYPE and DATA
COLLECTION DATE for data collected at particular MONitoring UNITS.
DATACOLS also includes other attribute information for data collections,
such as data collector, recorder, weather conditions, etc. Go back to diagram
- DATASTYP: The
DATASTYP table contains information about the DATA Set TYPe, i.e. all
details about the monitoring METHODS used. Each data collection
method--no matter how slightly each varies--should have a separate
DATASTYP entry describing the exact method, highlighting differences
among other similar methods which may also be defined in the database.
Go back to diagram
- DCDTNOTS: The
DCDTNOTS table contains Data Collection DaTe NOTes, i.e. any notes which
are particular to a particular data collection DATE (vs. applicable only
to a portion of the day and/or monitoring unit). Go
back to diagram
- DEBUG: If the DEBUG.DB
table exists in your working directory (:WORK:), the system is by
definition in "PT Debug Mode": certain features of the programs will
work differently than normal, typically to provide additional information
to the programmer about the internal workings of the program during
troubleshooting. Typically, this table should NOT exist (you may delete
it at will). Go back to diagram
- DENSDATA: This table
[should be described by Guy; corresponds to Excel spreadsheet
MASTDEN.XLS]. Go back to diagram
- ELEVSRCS: The
ELEVSRCS table contains codes for ELEVation SouRCeS (i.e. where did you
get the elevation info which you've associated with a monitoring unit?),
along with detailed information about these codes' interpretations.
Go back to diagram
- FAMGRPS: [FAMGRPS is
an OLD table from a pre-release version; it was replaced by the ORDERS,
CLASSES, PHYLDIVS, KINGDOM tables.] Go back to
diagram
- FAMILIES: The
FAMILIES table contains information about all taxonomic families in the
database. All family-related information should be stored in this table.
GENERA.DB links this table to TAXA.DB. Go back to diagram
- FASIGN: The FASIGN
table contains Feral Animal SIGN codes & code interpretations (used in
the THRETMON table). Go back to diagram
- FEDSTAT: This table
contains codes & descriptions for Federal Endangered/Threatened Species
status. Go back to diagram
- FEEDBACK: The
FEEDBACK table provides a place for you to record questions, notes, and
feedback to the programmer about the Monitoring Database system.
Go back to diagram
- FIELDATA: The
FIELDATA table contains virtually ALL NUMERIC DATA FROM FIELD
OBSERVATIONS. The rationale behind this is that if all data is
maintained in a single table, comprehensive queries relating to taxa at
any project, transect, plot, date, etc. are much easier, and data from
changes to the database (e.g. addition of new data set types) will be
AUTOMATICALLY incorporated into the answers to existing queries.
Appropriate forms simplify what might seem at first to be complicated by
showing the user in a logical format ONLY the data that's needed.
Additionally, single-click conversion routines for each data type convert
data into formats which allow the easiest and most flexible querying and
reporting. Go back to diagram
- GENERA: Master table
of genera used in database. Used to relate TAXA.DB|Genera to
FAMILIES.DB. Go back to diagram
- GUYINFO: The GUYINFO
table contains specific information for certain monitoring units used by
Guy Hughes when the Monitoring Database was first conceived. (This table
is not an integral part of the Monitoring Database infrastructure; this
information is retained for historical purposes only.) Go back to diagram
- GUYPLTCT: The
GUYINFO table contains specific community type information for certain
monitoring units used by Guy Hughes when the Monitoring Database was
first conceived. (This table is not an integral part of the Monitoring
Database infrastructure; this information is retained for historical
purposes only.) Go back to diagram
- INANAREA: The
INANAREA table maintains valid options for the answer to the question "Is
this species found in [this particular area]?" It is used as a data
validity check (lookup table) for various fields, e.g. "In HALE?" [Is
this plant found in Haleakala National Park?], "In HAVO?", etc. Go back to diagram
- INFRASP: Infraspecific
taxon codes (e.g., "var.", "ssp."), to force consistency. Go back to diagram
- ITEMTYPS: This table
defines "Item types" as used on this form (see above). It is used ONLY
for SYSTEM DOCUMENTATION. Go back to diagram
- KEYVIOL: This is a
PDOXWIN system-generated table. [See PDOXWIN documentation regarding
"key violations."] Go back to diagram
- KINGDOMS: The
KINGDOMS table contains information about all taxonomic kingdoms in the
database; all kingdom-related information should be stored in this table.
Go back to diagram
- KV*: All "KV" tables are
KeyViolation tables which occurred during the 01/95 conversion of Guy's
Excel data to PDOXWIN. After discrepancies in this information are
compared to the corresponding "good" tables (DENSDATA.DB, PLOTDATA.DB,
WEEDDATA.DB), these tables may be deleted. Go back to
diagram
- MONUNITS: The
MONUNITS table defines the MONitoring UNITS with which data will be
associated (e.g. Transects, Plots, Stations). This table contains
information relevant at the respective level of each monitoring unit
(e.g. transect description, plot sketch, station description).
Go back to diagram
- NESW: The NESW table
contains lookup values for compass directions (N, E, S, W) for data
validation. Go back to diagram
- NOTES: The purpose of
the NOTES table is to allow an online medium to chronologically record
general notes about data collection methods, use of the database itself,
standards/conventions that you may wish to document, and anything else
relevant to the entire data collection process that should be documented.
Note that QUESTIONS RE: the database management system should instead be
logged in the FEEDBACK section, and PROCEDURES RE: the database
management system should be documented in the USERDOC.DOC document
INSTEAD of being logged in the NOTES table. -pt/951212 Go back to diagram
- ORDERS: The ORDERS
table contains information about all taxonomic orders in the database;
all order-related information should be stored in this table. Go back to diagram
- ORIGINS: This table
contains codes and descriptions of ORIGINS of the taxa in the database
(e.g., Endemic, Poly intro, Post-Cook intro). Go back
to diagram
- PHYLDIVS: The
PHYLDIVS table contains information about all taxonomic phyla/divisions
in the database; all phylum/division-related information should be stored
in this table. Go back to diagram
- PLOTDATA: This table
[should be described by Guy; corresponds to Excel spreadsheet
MASPLOT.XLS]. Go back to diagram
- PLOTS: This table
contains codes & descriptions of TNCH plots. All information specific to
particular plots should be stored in this table. Plots are specific to
transects; plots contain stations. Go back to
diagram
- PRJDSTMU: The
PRJDSTMU table enables the user to associate a Project and Data Set Type
to a particular Monitoring Unit. (NOTE: This table is not currently [07/97] used as an integral part of
the Monitoring Database. In fact, I'm not exactly sure why this table is
here; it might be useful if the "start date" of the Prj/DST on that MU
were indicated [but, if ALL data from the entire series were in FIELDATA,
this info could be derived from the raw data--as it should be].
-pt/970729) Go back to diagram
- PROJECTS: This table
contains codes & descriptions of various projects. (At the time of
conversion, all data was set to Project=TNCH; this may be changed if
appropriate.) Go back to diagram
- RECORDRS: The RECORDRS table
contains codes & full names of observers/data recorders. Can be used to
validate entry of both types of data, when appropriate. Go back to diagram
- SELDCOMS: The SELDCOMS table
was designed for use by the USRQUERY form (which is not currently [07/97]
incorporated into the Monitoring Database, but will be "someday"). Go back to diagram
- SELDDSTS: The SELDDSTS table
was designed for use by the USRQUERY form (which is not currently [07/97]
incorporated into the Monitoring Database, but will be "someday"). Go back to diagram
- SELDFAMG: The SELDFAMG table
was designed for use by the USRQUERY form (which is not currently [07/97]
incorporated into the Monitoring Database, but will be "someday"). Go back to diagram
- SELDFAMS: The SELDFAMS table
was designed for use by the USRQUERY form (which is not currently [07/97]
incorporated into the Monitoring Database, but will be "someday"). Go back to diagram
- SELDFSS: This table
was designed for use by the USRQUERY form (which is not currently [07/97]
incorporated into the Monitoring Database, but will be "someday"). Go back to diagram
- SELDGENR: This table
was designed for use by the USRQUERY form (which is not currently [07/97]
incorporated into the Monitoring Database, but will be "someday"). Go back to diagram
- SELDISLS: This table
was designed for use by the USRQUERY form (which is not currently [07/97]
incorporated into the Monitoring Database, but will be "someday"). Go back to diagram
- SELDORGN: This table
was designed for use by the USRQUERY form (which is not currently [07/97]
incorporated into the Monitoring Database, but will be "someday"). Go back to diagram
- SELDPRJS: This table
was designed for use by the USRQUERY form (which is not currently [07/97]
incorporated into the Monitoring Database, but will be "someday"). Go back to diagram
- SELDTAXA: This table
was designed for use by the USRQUERY form (which is not currently [07/97]
incorporated into the Monitoring Database, but will be "someday"). Go back to diagram
- STATIONS: This table
contains codes & descriptions of TNCH stations. Stations are specific to
plots (see PLOTS.DB). Also contains cross-reference to the corresponding
USFWS station. Go back to diagram
- SYSTMDOC: [SYSTMDOC
contains the information you are viewing now!] Contains SYSTeM
DOCumenation (by filename) (one level of "metadata"). See also [other
system documentation] for functional/procedural system
documentation. Go back to diagram
- TAXA: This table
contains information about each taxon in any data set. Cross-references
to codes used by specific groups (e.g. TNCH-Maui, NBS/HALE, HHP) are
found in TAXONCOD.DB. Go back to diagram
- TAXAUTHS: The
TAXAUTHS table documents the TAXONOMIC AUTHORITY for any taxon not
covered in the standard taxonomic reference sources (e.g. for plants, the
Manual; HBS updates; Contributions to the Manual; Neal 1965; Mabberly;
Hortus III), or otherwise taxonomically revised (e.g. later publications
not recorded in a standard source). [table added to Monitoring Database
970404/pt] Go back to diagram
- TAXONCOD: TNCH taxon
codes, with entries cross-referencing them to TAXA.DB and the OLD HALE
TAXA (necessary for linking to NBS/HALE database until it is fully
converted to new keys). (Should also have HHP codes added... OR:
TAXONHHP.DB should be created with unique keys) Go back
to diagram
- THRETMON: The
THRETMON table is a counterpart to the FIELDATA table, but instead of
containing completely numeric data, contains a set of specialized data
(some of which is non-numeric) relevant to THREAT MONITORING (i.e.
threats to native/rare species). THRETMON data is viewed via specialized
forms, each corresponding to a particular Data Set Type (or field data
collection method; e.g., UNG5X10M, UNG5X50M). Go back
to diagram
- TNCNOTES: This
table just contains notes about the conversion. When all items are duly
noted/dealt with, this table may be deleted. Go back to
diagram
- TRANSECS: This
table contains codes & descriptions of TNCH transects. Transects contain
plots; plots contain stations. Go back to diagram
- TRANTYPS: The
TRANTYPS table include codes denoting TRANsect TYPeS, interpretations of
these codes, and descriptions (verbal and visual) of these transect
types. (The "transect type" is an integral part of the definition of
every Monitoring Unit.) Go back to diagram
- USFWSRAR: [The
USFWSRAR table is an artifact of pre-release versions of the Monitoring
Database, and is NOT USED at all by the current version. It was
previously used to define specific "rarity categories" then--but no
longer--used by USFWS.] Go back to diagram
- USFWSTAS: U.S.
Fish & Wildlife Service stations master table. Should eventually be used to
correlate data sets with the USFWS (bird?) transect stations. Go back to diagram
- WEEDDATA: This
table [should be described by Guy Hughes; corresponds to Excel spreadsheet
MASWEED.XLS]. Go back to diagram
- User-defined ad hoc tables: Users
of the Monitoring Database can define their own ad hoc data tables, to be
linked into the infrastructure of and to be used with the Monitoring Database. There
are no limitations on these additional tables except your imagination and your computer's
capacity. (NOTE to database designers: Although Referential Integrity is an essential element of the Monitoring
Database, be sure you thoroughly understand it--and see the Monitoring Database documentation--
before implementing this powerful feature in your own tables.) Go back to diagram
[Monitoring Database] [Alien Species In Hawaii] [Hawaiian Ecosystems at Risk]
Comments, questions, feedback about this
website or its contents? e-mail the HEAR project
(This document was last updated 29 July 1997 by PT.)