EVENTS ¶

Each row represents an event that occurred during a follow, whether involving the focal or not. All recorded observations that occur during a follow are events.

Each Behavior code has a one-to-one association with a table in the database. An AGG Behavior code is associated with the AGGRESSIONS table. An ARR Behavior code is associated with the ARRIVALS table. And so forth. The system will generate a warning when an EVENTS row exists and there is no related row in the table that corresponds to the row’s Behavior code.

Each Behavior code has its own rules regarding what other information must or should be present in the database in order to retain data validity, and what each code implies about the meaning of related data. The following table lists these rules and implications:

AGG (Aggression)

A related row should exist on AGGRESSIONS; there should be a row on AGGRESSIONS with an EID value of the event’s EID. There may be at most one of these related AGGRESSIONS rows. The system will generate a warning when there is no AGGRESSIONS row related to the aggression event.

The ROLES rows related to the event, the rows with a EID value equal to the EID value, designates the individuals involved in the aggression event. The ROLES.Role code of each individual that the ROLES table relates to the aggression event describes whether that individual aggressed or was aggressed upon during the aggression event.

There should be exactly two ROLES row related to the aggression event. The only two ROLES.Role codes allowed are Actor and Actee. One of those two roles must be Actor and the other must be Actee. The system will generate a warning when there are not exactly two ROLES rows related to an aggression event.

The two participants in an aggression event must be different individuals. This means that their ROLES.Participant values must differ.

Both the EVENTS.Start and EVENTS.Stop columns record the time of the aggression event. This means the value of the EVENTS.Start column must equal the value of the EVENTS.Stop column.

For aggression events, the EVENTS.Certainty column records the certainty of the identity of the recipient, that is to say, the certainty of the individual with the role of Actee.

ARR (Arrival)

A related row should exist on ARRIVALS; there should be a row on ARRIVALS with an EID value of the event’s EID. There may be at most one of these related ARRIVALS rows. The system will generate a warning when there is no ARRIVALS row related to the arrival event.

The ROLES row related to the event, the row with a EID value equal to the EID value, designates the arriving/departing individual. There may be at most one ROLES row related to the arrival event. The system will generate a warning when there is no ROLES row related to the arrival event.

The EVENTS.Start column contains the arrival time of the individual identified in the related ROLES row.

The EVENTS.Stop column contains the departure time of the the individual identified in the related ROLES row.

FOOD (Food)

A related row should exist on FOOD_EVENTS; there should be a row on FOOD_EVENTS with an EID value of the event’s EID. The system will generate a warning when there is no FOOD_EVENTS row related to the food event. There may be more than one of these related FOOD_EVENTS rows, one for every food category/food part pairing observed.

The ROLES row related to the event, the row with a EID value equal to the EID value, designates the individual that consumed the food. There may be at most one ROLES row related to the food event. The system will generate a warning when there is no ROLES row related to the food event.

The EVENTS.Start column contains the time the food bout began.

The EVENTS.Stop column contains the time the food bout finished.

GROOM (Grooming): A row must exist on GROOMINGS.

MATE (Mating): A row must exist on MATINGS.

OS (Other Species): A row must exist on SPECIES_PRESENT and/or on HUMANS.

PG (Pantgrunt): A row must exist on PANTGRUNTS.

The Start time cannot be after the Stop time.

EID (Event ID)¶

A unique, automatically generated, positive integer which serves to identify the row. The value of this column cannot be changed. This column may not be NULL.

FID (Follow IDentifier)¶

The FOLLOWS.FID that identifies the follow during which the event was recorded. The value of this column cannot be changed. This column may not be NULL.

Behavior ¶

A code indicating the kind of event recorded. These codes usually represent chimpanzee behaviors, but may otherwise classify the event.

Each code has special meaning to SokweDB, controlling what additional information may, or must, be related to the event. In other words, what other tables may, or must, contain additional information about the event.

The following list summarizes the available codes:

AGG (Aggression): A row must exist on AGGRESSIONS.
ARR (Arrival): A row must exist on ARRIVALS.
FOOD (Food): A row must exist on FOOD_EVENTS.
GROOM (Grooming): A row must exist on GROOMINGS.
MATE (Mating): A row must exist on MATINGS.
OS (Other Species): A row must exist on SPECIES_PRESENT and/or on HUMANS.
PG (Pantgrunt): A row must exist on PANTGRUNTS.

See above for further detail regarding what related data each code requires, or is expected to have.

The value of this column cannot be changed. This column may not be NULL.

Start ¶

The time the event started. As with many other time values, this value is precise to the minute. The “starting minute” recorded in this column is an “inclusive endpoint”, the event occurred (or began occurring), and was ongoing, during the designated minute.

The value of this column cannot be before 4:00. This column must contain values that fall on one minute intervals; it may not contain values having seconds or fractions of seconds. This column may not be NULL.

EVENTS ¶

EID (Event ID)¶

FID (Follow IDentifier)¶

Behavior ¶

Start ¶

Stop ¶

Certainty ¶

Notes ¶

SokweDB Technical Documentation

Navigation

Related Topics