BEHAVIOR_TRANS contains one row for every behavior code as written in the field, plus one row for every column representing an observed behavior. It is used by the UPLOAD_BEHAVIORS view to translate the codes and column markings made in the field to the behavior codes used within the Gombe-MI system.[32]
The BEHAVIOR_TRANS table is different from other Gombe-MI support tables in that its values are used only to support the behavioral data upload process, the values do not define a vocabulary used for Gombe-MI database content.
The GO_Self must be
NULL when Grooms_Other is
TRUE and otherwise must be non-NULL.
The With_Ma column is
only meaningful when Play_Val
and Ride_Val are NULL and
Grooms_Other and
Grooms_By are FALSE.
Further, it is meaningful only for those rows representing
behavioral codes which occur as values in columns, not for those
rows representing uploaded columns, and has no effect on the
mother's behavioral data.
The BEHAVIOR_TRANS table is keyed by the Old_Behavior column. This column indicates how the behavior is denoted in the field on the the data collection sheet. The values in this column are unusual in that they are of one of two different sorts. When the field data collector writes one or more behavior codes onto the data collection sheet each of the codes written should appear as a Old_Behavior value in a BEHAVIOR_TRANS row. When the field data collector makes check-marks or puts similar marks on the data collection sheet to represent the observation of a behavior then there should be a row in BEHAVIOR_TRANS with a Old_Behavior value which is the name of the column into which the check-mark is made. In this case the column name value in the Old_Behavior column should be one of the column names of the UPLOAD_BEHAVIORS view, written in lower case.[33]
Behavior code to be used within Gombe-MI. The legal values for this column are defined by the BEHAVIORS support table.
This column may not be NULL.
Position code to be used when the uploaded row contains no indication of what position within the canopy is associated with the behavior. The legal values for this column are defined by the POSITIONS support table.
This value must be NULL when a position value is not
required by the behavior.
A Boolean value indicating whether behavioral events deriving from the given old behavior code should always be denoted uncertain (EVENTS.Uncertain).
This column may not be NULL.
A Boolean value indicating whether another uploaded column contains the chimpids (animids) of individuals groomed by the focal. The actual referenced chimpid containing column and the treatment of its content is determined by the UPLOAD_BEHAVIORS view.
A Boolean value indicating whether self-grooming is
denoted by having the focal's own chimpid listed along with
the other individuals the focal is grooming. A value of
TRUE indicates that self-grooming is denoted by listing the
focal's chimpid along with the other groomed individuals. A
value of FALSE indicates that self-grooming is not denoted
in this fashion.
This value may be NULL. See above.
A Boolean value indicating whether another uploaded column contains the chimpids (animids) of individuals who groomed the focal. The actual referenced chimpid containing column and the treatment of its content is determined by the UPLOAD_BEHAVIORS view.
Play code to be used when the uploaded row contains no indication of what play code is associated with the behavior. The legal values for this column are defined by the PLAY_TYPES support table.
When this value is not NULL another uploaded column
contains the chimpids (animids) of individuals who played with the
focal. The actual referenced chimpid containing column and the
treatment of its content is determined by the
UPLOAD_BEHAVIORS view.
This value must be NULL when a play value is not
required/when the behavior is not a play behavior.
Resting posture code to be used when the uploaded row contains no indication of what resting posture code is associated with the behavior. The legal values for this column are defined by the RESTING_POSTURES support table.
This value must be NULL when a resting value is not
required/when the behavior is not a resting behavior.
Riding posture code to be used when the uploaded row contains no indication of what riding posture code is associated with the behavior. The legal values for this column are defined by the RIDING_POSTURES support table.
This value must be NULL when a riding value is not
required/when the behavior is not a riding behavior.
Vocalization code to be used when the uploaded row contains no indication of what vocalization code is associated with the behavior. The legal values for this column are defined by the RIDING_POSTURES support table.
This value must be NULL when a vocalization value is
not required/when the behavior is not a vocalization
behavior.
A Boolean value indicating whether another pair of uploaded columns contains the food parts and food kinds detailing the food eaten by the focal. The actual referenced columns containing food detail and the treatment of its content is determined by the UPLOAD_BEHAVIORS view.
A Boolean value indicating whether another pair of uploaded columns contains the food parts and food kinds detailing the food fished for by the focal. The actual referenced columns containing food detail and the treatment of its content is determined by the UPLOAD_BEHAVIORS view.
Default Foodpart code to be used when the uploaded row contains no indication of what foodpart code is associated with the fishing behavior. The legal values for this column are defined by the FOODPARTS support table.
This value must be NULL when a foodpart is not
required/when the behavior is not a fishing behavior.
Default Foodkind code to be used when the uploaded row contains no indication of what foodkind code is associated with the fishing behavior. The legal values for this column are defined by the FOODKINDS support table.
This value must be NULL when a foodpart is not
required/when the behavior is not a fishing behavior.
A Boolean value indicating whether or not the infant is
allowed to have this behavior code written into the
Inf_Behavior column. A
value of TRUE indicates the infant is allowed to have the
behavior code. A value of FALSE indicates the infant is not
allowed to have the behavior code. This column may not be NULL.
Do not rely on this column as a means of preventing the database from recording certain infant behaviors. The BEHAVIORS table should be used for that purpose. This column serves only to help ensure that uploaded data is not misinterpreted when transformed into database content.
A Boolean value indicating whether or not individuals
exhibiting this behavior are doing so in a directed fashion
with the mother. TRUE means the mother is a social partner,
the “actee”, even though there is no other
indication of this. FALSE means the mother is not
automatically made a social partner. This column may not be NULL.
A Boolean value indicating whether the behavior is recorded twice on the data collection sheet, once for each focal.
For further information see above.
In order to process the indicated columns the UPLOAD_BEHAVIORS view requires that BEHAVIOR_TRANS contain rows for the following Old_Behavior values:
ma_foodpart
ma_fishpart
ma_grooming
ma_groomed_by
ma_play
ma_voc
inf_foodpart
inf_fishpart
inf_nurse
inf_travel
inf_eat
inf_solitary_play
inf_rest
inf_ride_on_belly
inf_ride_on_back
inf_ride_on_unk
inf_dangle
inf_rejection
inf_touching_another
inf_grooming
inf_being_groomed
inf_social_play
inf_display
inf_cry
inf_voc
inf_beg
inf_assr
inf_sex_related
inf_tooluse
inf_directaggression
devbeh
sib_foodpart
sib_fishpart
sib_grooming
sib_groomed_by
sib_play
sib_voc
DISTANCE_TRANS contains one row for every distance code as written in the field, plus one row for every column representing an observed inter-focal distance. It is used by the UPLOAD_BEHAVIORS view to translate the codes and markings in columns which are made in the field to the distance codes used within the Gombe-MI system.[34]
The DISTANCE_TRANS table is different from other Gombe-MI support tables in that its values are used only to support the behavioral data upload process, the values do not define a vocabulary used for Gombe-MI database content.
The DISTANCE_TRANS table is keyed by the Old_Distance column. This column indicates how the distance is denoted in the field on the the data collection sheet. The values in this column are unusual in that they are of one of two different sorts. When the field data collector writes one or more distance codes onto the data collection sheet each of the codes written should appear as a Old_Distance value in a DISTANCE_TRANS row. When the field data collector makes check-marks or puts similar marks on the data collection sheet to represent the observation of a distance then there should be a row in DISTANCE_TRANS with a Old_Distance value which is the name of the column into which the check-mark is made. In this case the column name value in the Old_Distance column should be one of the column names of the UPLOAD_BEHAVIORS view, written in lower case.[35]
Distance code to be used within Gombe-MI. The legal values for this column are defined by the DISTANCECODES support table.
This column may not be NULL.
A Boolean value indicating whether inter-focal distance measurements deriving from the given old distance code should always be denoted uncertain (EVENTS.Uncertain).
This column may not be NULL.
In order to process the indicated columns the UPLOAD_BEHAVIORS view requires that DISTANCE_TRANS contain rows for the following Old_Distance values:
inf_distance_1
inf_distance_2
inf_distance_3
inf_distance_4
inf_distance_5
inf_distance_over_5m
FOLLOWROLES contains one row for every possible role of the individuals which are followed. E.g. Mother, Infant, Sibling, Twin1[36], etc.
The biological relationship of the role. Must be one of:
M
Mother
I
Infant
S
Sibling
The Function value cannot be changed. This column may not be NULL.
The Role may not have a value
of NF.
The NF code has the reserved
meaning “Not a focal in the follow”.
The Role
values M,
I,
and S have special meaning to
the UPLOAD_BEHAVIORS view. See the
documentation of the view for more information.
FOLLOWTYPES contains one row for every type of data entry
sheet (template) used in the field. For further information see
the templates.xlsx spreadsheet and related
documentation.
The Descr column is the appropriate place to put notes on the data collection protocol(s) or template sheets used with the given type of follow, as well as the list of templates which make up the type.[37]
A Boolean value indicating whether a behavior code is
always recorded on the sheet, for particular
mother/infant/sibling behaviors, or whether the behavior
code is implied by the presence of data in another column.
A value of TRUE means that the behavior code is implied by
the presence of data in certain columns. A value of FALSE
means that behavior codes are always present in the data for
these columns.
For further information on which behaviors and which columns are affected by the Implied_Behavior value see the documentation of the UPLOAD_BEHAVIORS view.
This column may not be NULL.
All columns but Type, Implied_Behavior, and Descr are Boolean.[38]True indicates that the data represented by the column name was collected using the data collection protocol associated with the data entry sheets of the given follow type. Note that the data may have been collected either as a column or in notes.
FOODPART_TRANS contains one row for every food part code as written in the field. It is used by the UPLOAD_BEHAVIORS program to translate the foodpart codes as written in the field to the food part codes used within the Gombe-MI system.[39]
The FOODPART_TRANS table is different from other Gombe-MI support tables in that its values are used only to support the behavioral data upload process, the values do not define a vocabulary used for Gombe-MI database content.
The FOODPART_TRANS table is keyed by the Old_Foodpart column. This column contains the foodpart codes written onto the data collection sheet in the field.
Foodpart code to be used within Gombe-MI. The legal values for this column are defined by the FOODPARTS support table.
This column may not be NULL.
GC_TRANS contains one row for every mark written in the field onto the group composition portion of the data collection sheets, in the cells of the columns which record chimpanzee or baboon presence. It is used by the Upload_GC program to translate the codes and markings in columns as made in the field to determine how the information is represented within the Gombe-MI system.[40]
The GC_TRANS table is different from other Gombe-MI support tables in that its values are used only to support the group composition data upload process, the values do not define a vocabulary used for Gombe-MI database content.
There can only be a swelling when the individual is in the
group composition -- the Swelling
value must be NULL when Present is
FALSE.
There must be a code indicating where the data came from
when the individual is present, and otherwise there must not --
the Origin column cannot be NULL
when Present is TRUE, and the
Origin column must be NULL when
Present is FALSE.
The GC_TRANS table is keyed by the Mark column. This
column indicates what marks are made in the cells of the
columns which correspond to chimpanzees. The Mark column may
not be NULL, but may be the empty string.
A Boolean value indicating whether the designated mark means the individual should be included in the group composition -- whether there should be a row on RAW_GROUPMEMBERS.
This column may not be NULL.
A Boolean value indicating the RAW_GROUPMEMBERS.Uncertain value to use when this mark appears on the group comp sheet.
This column may not be NULL.
Swelling value to be stored in the RAW_GROUPMEMBERS.Swelling when the designated mark is used.
This value may be NULL when the RAW_GROUPMEMBERS.Swelling value is to be NULL.
Origin value to be stored in the RAW_GROUPMEMBERS.Origin when the designated mark is used.
See the GC_TRANS description above for
when this value may and may not be NULL.
Notes on the GC_TRANS row and the
Mark value. Because it can be hard
to distinguish NULL from the empty string, no characters,
the Notes column is provided. Any notes on the row's
Mark value or anything else related
to the row may be be stored in this column.
This value may be NULL when notes are not needed.
PEOPLE contains one row for every person involved in data collection or data entry.
PLAY_TRANS contains one row for every play code as written in the field. It is used by the UPLOAD_BEHAVIORS view to translate the codes written in the field to the play codes used within the Gombe-MI system.
The PLAY_TRANS table is different from other Gombe-MI support tables in that it's values are used only to support the behavioral data upload process, the values do not define a vocabulary used for Gombe-MI database content.
Play code to be used within Gombe-MI. The legal values for this column are defined by the PLAY_TYPES support table.
This column may not be NULL.
VOC_TRANS contains one row for every vocalization code as written in the field. It is used by the UPLOAD_BEHAVIORS view to translate the codes written in the field to the vocalization codes used within the Gombe-MI system.
The VOC_TRANS table is different from other Gombe-MI support tables in that it's values are used only to support the behavioral data upload process, the values do not define a vocabulary used for Gombe-MI database content.
Vocalization code to be used within Gombe-MI. The legal values for this column are defined by the VOCALIZATIONS support table.
This column may not be NULL.
[32] This provides a degree of flexibility when it comes to adding to the behaviors observed in the field. In cases where the field data collector writes behavior codes onto the data collection sheet there (may) need to be no changes made to the Gombe-MI system's code to accommodate the new data. In cases where the field data collector puts check-marks (or similar) into columns the UPLOAD_BEHAVIORS view must have the names of these kinds of columns written into it's source code and so program changes are required to accommodate additional columns of this sort.
[33] The decision to use the names of the columns of the UPLOAD_BEHAVIORS view, in lower case, rather than an exact match of the names of the columns that are written on the field data collection sheets is somewhat arbitrary. The system as written does make it simpler to maintain the UPLOAD_BEHAVIORS view since the programmer can be less aware of the details of data entry as it occurs in the field.
[34] See the above footnote regarding the flexibility provided by the BEHAVIOR_TRANS table.
[35] See the above footnote in the BEHAVIOR_TRANS documentation regarding the design decisions surrounding the use of column names.
[36] Note that the system does not require a separate FOLLOWROLES row for, e.g., twins since when there are multiple infants or siblings they must have the same birth date.
[37] It might or might not make sense to have a separate textual column which lists the templates that make up the type.
[38] These Boolean columns are documented in a table, differently from the documentation of other columns in this document, due to their substantial similarity.
[39] See the above footnote regarding the flexibility provided by the BEHAVIOR_TRANS table.
[40] See the above footnote regarding the flexibility provided by the BEHAVIOR_TRANS table.