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.

The Start time cannot be after the Stop time.

Each of the Behavior codes 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 row must exist on AGGRESSIONS.

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 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.

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 futher 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. 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.

Stop

The time the event stopped. The value of this column cannot be after 20: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.

Certainty

A CERTAINTIES.Certainty code designating the certainty of the event observervation. This column may not be NULL.

Notes

Free form textual notes regarding the event. This column may be empty text. It need not contain characters, but it may not contain only whitespace characters. This column may not be NULL.

Page last generated: 2025-10-10 18:53:13 UTC