Chapter 5. Support Tables

Table of Contents

General Support Tables
BODYPARTS
LAB_PERSONNEL
OBSERVERS (Data Collection Staff)
OBSERVER_ROLES
UNKSNAMES (problem in identifying focal's neighbor or a lone male)
Group Membership and Life Events
BSTATUSES (Birth Accuracy Indicators)
CONFIDENCES (death cause (nature and agent), dispersal, and matgrp Confidence levels)
DAD_SOFTWARE
DCAUSES (Causes of Death)
DEMOG_REFERENCES (Demography Note References)
DEATHNATURES (Natures of Death Causes)
ENTRYTYPES (Categories of Entry to Study Population)
GAP_END_STATUSES (Explanations for Behavior Gap Ends)
MSTATUSES (Maturity Marker Statuses)
DAD_DATA_COMPLETENESS (Completeness Scores in Paternity Analyses)
DAD_DATA_MISMATCHES (Types of Genetic Mismatches)
RNKTYPES (Ranking Categories)
STATUSES (Indicators of Record and Baboon Vividity)
Physical Traits
HORMONE_IDS
HORMONE_PREP_PROCEDURES
HYBRIDGENE_SOFTWARE
MARKERS
WP_HEALSTATUSES
WP_REPORTSTATES
WP_WOUNDPATHCODES
Social And Multiparty Interactions
ACTIVITIES
ACTS (Interaction Types)
DATA_STRUCTURES (Data structures produced by Psion devices)
CONTEXT_TYPES (multiparty Interaction Context Categories)
FOODCODES (Food item Codes)
FOODTYPES (Food Types)
KIDCONTACTS (spatial relationship between mother and infant)
MPIACTS (Multiparty Interaction Types)
NCODES (Neighbor classifications)
PARTUNKS (problem identifying a multiparty interaction participant)
POSTURES
PROGRAMIDS (Program used on the device)
SAMPLES_COLLECTION_SYSTEMS
SETUPIDS (Setup files used in a data collection program)
STYPES (Focal Sample Types)
STYPES_ACTIVITIES (Activity values that are used with each SType)
STYPES_NCODES (Ncodes that are used with each SType)
STYPES_POSTURES (Postures that are used with each SType)
SUCKLES (infant suckling activity)
Sexual Cycles and The Sexual Cycle Day-By-Day Tables
PCSCOLORS (ParaCallosal Skin Colors)
Darting
DART_SAMPLE_CATS (Darting Sample Categories)
DART_SAMPLE_TYPES (Sample Types)
DRUGS (darting anesthetics)
LYMPHSTATES (Lymph node conditions)
PARASITES (Parasites and their indicators)
TCONDITIONS (Tooth Conditions)
TICKSTATUSES (parasite count classifications)
TOOTHCODES (kinds of teeth)
TOOTHSITES (Locations of deciduous or adult teeth)
TSTATES (State of Tooth existence)
Inventory
INSTITUTIONS
MISID_STATUSES (MISIDentification STATUSES)
NUCACID_CONC_METHODS (NUCleic ACID CONCentration quantification METHODS)
NUCACID_CREATION_METHODS (NUCleic ACID CREATION METHODS)
NUCACID_TYPES (NUCleic ACID TYPES)
STORAGE_MEDIA
TISSUE_TYPES
SWERB Data
ADCODES (SWERB Ascent and Descent relationships)
PLACE_TYPES (codes for various landscape features)
PREDATORS (codes for observed predators)
SWERB_LOC_CONFIDENCES (SWERB Location Confidence Values)
SWERB_LOC_STATUSES (SWERB Location Statuses)
SWERB_TIME_SOURCES (SWERB Time Sources)
SWERB_XYSOURCES (SWERB Time Sources)
Weather Data
WEATHER_SOFTWARES (Programs used for digital weather data reporting)
WSTATIONS (Weather Stations)

The support tables are those tables that define various codes used as data values in other tables. They define the controlled vocabulary used elsewhere in the system. The formulation of the available vocabulary is, for the most part, up to the users of Babase. This provides a great deal of flexibility in the information Babase records without requiring any programmatic or other alteration to the Babase system itself. New code values can be added to the system and used in the data by adding new rows to the support tables. The system validates the new code values in the data tables against the rows of the support tables allowing new types of data to be recorded without requiring changes to the Babase system.

Caution

Some of the vocabulary in the support tables has special meaning to Babase. All values that have a special meaning to Babase are noted in each table's documentation. Care must be taken when making changes in these cases or Babase will break. See the Special Values section for further information.

Most support tables contain only two columns (not counting the Sys_Period column): a key or id column that usually has the same name as the column in the tables for which the support table defines vocabulary, and a column called Descr. The key column contains the valid code values, and the Descr column contains a short description of the code. Both the key column and the Descr column must contain values that are unique among all the values of all the rows in the respective column. Neither the key column nor the Descr column may be NULL. Neither the key column nor the Descr column may be empty, contain no characters. Neither the key column nor the Descr column may contain nothing but spaces.

As with nearly every other table in Babase, every support table has a Sys_Period column that shows the range of time during which the row's data is considered valid. See The Sys_Period Column for more information.

Some support tables contain one or more additional columns. These are described in the section devoted to the table at hand.


Page generated: 2024-10-29T13:28:52-04:00.