EVENTS

Each row represents an event that occurred. Typically, events involve one or more chimpanzees. Events may be recorded during a follow, whether involving a focal or not, events may be recorded at the feeding station, or events may be recorded as ad-hoc observations such as records of pantgrunts recorded opportunisticly.

Whether an event is related to a follow or to an attendance record or to something else is dependent upon the event’s Behavior code.

Each Behavior code can have a one-to-one association with a table in the database, a table that contains additional event detail. 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:

AARR (Arrival at the feeding station)

The EVENTS row must be associated with a record of attendance at the feeding station. This means the WID column must reference a WATCHES row with a WATCHES.Type value of A.

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

The ROLES row related to the event, the row with a ROLES.EID value equal to the EVENTS.EID value, designates the arriving/departing individual in the ROLES.Participant column. 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.

For records of attendance at the feeding station, the EVENTS.Certainty column must be 1.

An individual should not be recorded as being at the feeding station more than once during any given time period. The system will generate a warning when there are overlaps in an individual’s presence at the feeding station. This means that for any given EVENTS row, with a given WID value, there should not be another EVENTS row with that WID value, with an Start value less than or equal to the given EVENTS row’s start time, when the other row’s Stop value is greater than or equal to the given EVENTS row’s start time. A similar rule applies to the given EVENTS row’s stop time. Which means, for any given EVENTS row, with a given WID value, there should not be another EVENTS row with that WID value, with an Start value less than or equal to the given EVENTS row’s stop time, when the other row’s Stop value is greater than or equal to the given EVENTS row’s stop time.

AGG (Aggression)

The EVENTS row must be associated with a follow. This means the WID column must reference a WATCHES row with a WATCHES.Type value of F.

A related row should exist on AGGRESSIONS; there should be a row on AGGRESSIONS with an AGGRESSIONS.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 ROLES.EID value equal to the EVENTS.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.

AGSCAN (Attendance SCAN interval Groomings)

The EVENTS row must be associated with a interval scan for grooming done at the feeding station. This means the WID column must reference a WATCHES row with a WATCHES.Type value of G.

The ROLES rows related to the event, the rows with a ROLES.EID value equal to the EVENTS.EID value, designates the individuals involved in the grooming event. The ROLES.Role code of each individual that the ROLES table relates to the grooming event describes whether that individual groomed or was groomed during the attendance grooming interval sampling event.

There should be exactly two ROLES row related to the attendance grooming interval sampling event. Only the codes Actor, Actee, and Mutual may be used as ROLES.Role code values. The system will generate a warning when there are not exactly two ROLES rows related to a attendance grooming event.

The two participants in a attendance grooming 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 scan when the attendance grooming was observed. This means the value of the EVENTS.Start column must equal the value of the EVENTS.Stop column.

For attendance grooming interval sampling events, the EVENTS.Certainty column must be 1.

ARR (Arrival)

The EVENTS row must be associated with a follow. This means the WID column must reference a WATCHES row with a WATCHES.Type value of F.

A related row should exist on ARRIVALS; there should be a row on ARRIVALS with an ARRIVALS.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 ROLES.EID value equal to the EVENTS.EID value, designates the arriving/departing individual. There must be at most one 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.

BREC (B-RECord note translation)

The EVENTS row must be associated with a WATCHES row representing either a follow or a B-Record taking. This means the WID column must reference a WATCHES row with a WATCHES.Type value of either F or B. Further, as explained in the WATCHES documentation, if there is a follow for a given individual on a given day then the EVENTS row must be associated with the follow.

A related row should exist on BRECORD_NOTES; there should be a row on BRECORD_NOTES with a BRECORD_NOTES.EID value of the event’s EID. There may be at most one of these related BRECORD_NOTES rows. The system will generate a warning when there is no BRECORD_NOTES row related to the B-Record note taking event.

An individual should have only one B-Record note taken at any given time. This means that the system will generate a warning when the combination of WID and Start is not unique.

There can be no ROLES rows related to the event. The concept behind this is that, even though B-Record notes are associated with an individual, the related WATCHES.AnimID, B-Record note translations are an administrative record. The focal of the B-Record follow, therefore, is not playing a paricular role in some behavioral category and so there should be no row on ROLES for the individual.

Both the EVENTS.Start and EVENTS.Stop columns record the time the note was taken. This means the value of the EVENTS.Start column must equal the value of the EVENTS.Stop column.

For B-Record note taking events, the EVENTS.Certainty column must be 1.

For B-Record note taking events, the EVENTS.Notes column is expected to be empty. (The expectation is that notes on the record-taking belong in the BRECORD_NOTES.Comments column.) The system will generate a warning when EVENTS.Notes is not the empty string.

COL (COLOBUS monkey hunt data)

There is one row for each record of colobus monkey hunting.

The EVENTS row must be associated with a follow. This means the WID column must reference a WATCHES row with a WATCHES.Type value of F.

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

There can be no ROLES rows related to the event.

The EVENTS.Start column contains the time the colobus monkey hunting encounter began.

The EVENTS.Stop column contains the time the colobus monkey hunting encounter ended. If a kill was made, this is the time that the first kill was made.

For colobus monkey hunting events, the EVENTS.Certainty column must be 1.

For colobus monkey hunting events, the EVENTS.Notes column contains comments and/or a description of the encounter.

FOOD (Food)

The EVENTS row must be associated with a follow. This means the WID column must reference a WATCHES row with a WATCHES.Type value of F.

A related row should exist on FOOD_EVENTS; there should be a row on FOOD_EVENTS with a FOOD_EVENTS.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 ROLES.EID value equal to the EVENTS.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 individual consuming the food must be the the focal of the follow. This means that the ROLES row related to the event must have a ROLES.Participant value equal to the WATCHES.AnimID of the follow that is 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.

UTM (UTM Location)

A record of an individual’s location recorded in UTM coordinates.

An individual can be located in only one place at any given time.[1] This means that the combination of WID and Start must be unique.

The EVENTS row must be associated with a WATCHES row representing either a follow or a location. This means the WID column must reference a WATCHES row with a WATCHES.Type value of either F or L. Further, as explained in the WATCHES documentation, if there is a follow for a given individual on a given day then the EVENTS row must be associated with the follow.

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

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

The individual located must be the the focal of the follow, when the related WATCHES row represents a follow, and must be located individual when the related WATCHES row records the date of a spatial location. This means that the ROLES row related to the event must have a ROLES.Participant value equal to the WATCHES.AnimID of the WATCHES row related to the GPS location event.

Both the EVENTS.Start and EVENTS.Stop columns record the time the individual was at the recorded location. This means the value of the EVENTS.Start column must equal the value of the EVENTS.Stop column.

When the located individual is the focal of a follow – when the related WATCHES.Type value is F – the time of the spatial recording should occur when the focal was under observation. The system will generate a warning when there is not an ARRIVALS related row that records the presence of the focal at the time the spatial observation occurred. This means that a warning will be generated when there is no related EVENTS row where the Behavior code is ARR and the EVENTS.Start value is less than or equal to the time of the GPS location event value and the EVENTS.Stop value is greater than or equal to the time of the location event, and the event has a related ROLES row where the ROLES.Participant is the located individual.

For GPS location events, the EVENTS.Certainty column must be 1.

GROOM (Grooming)

The EVENTS row must be associated with a follow. This means the WID column must reference a WATCHES row with a WATCHES.Type value of F.

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

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

There should be exactly two ROLES row related to the attendance grooming interval sampling event. Only the codes Actor, Actee, Mutual, and UNKPair may be used as ROLES.Role code values. The system will generate a warning when there are less than two ROLES rows related to an grooming event.

The participants in a grooming event must be different individuals. This means that their ROLES.Participant values must differ.

One of the individuals in a grooming event must be the focal individual. This means that on of the the ROLES rows related to the event must have a Participant value equal to the WATCHES.AnimID of the follow that is related to the grooming event.

For grooming events, the EVENTS.Certainty column records the certainty of the duration of the grooming event. When this column is TRUE, either the time of the start of the grooming event or the time of the end of the grooming event, or both, are uncertain.

GSCAN (SCAN interval Groomings)

The EVENTS row must be associated with a follow. This means the WID column must reference a WATCHES row with a WATCHES.Type value of F.

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

The ROLES rows related to the event, the rows with a ROLES.EID value equal to the EVENTS.EID value, designates the individuals involved in the grooming event. The ROLES.Role code of each individual that the ROLES table relates to the grooming event describes whether that individual groomed or was groomed during the groom interval sampling event.

There should be exactly two ROLES row related to the grooming interval sampling 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 grooming event.

The two participants in a grooming interval sampling 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 scan when the grooming was observed. This means the value of the EVENTS.Start column must equal the value of the EVENTS.Stop column.

For grooming interval sampling events, the EVENTS.Certainty column must be 1.

PAPER (PAPER map location)

A record of an individual’s location recorded using map sequence numbers.

An individual can be located in only one place at any given time.[1] This means that the combination of WID and Start must be unique.

The EVENTS row must be associated with a WATCHES row representing either a follow or a location. This means the WID column must reference a WATCHES row with a WATCHES.Type value of either F or L. Further, as explained in the WATCHES documentation, if there is a follow for a given individual on a given day then the EVENTS row must be associated with the follow.

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

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

The individual located must be the the focal of the follow, when the related WATCHES row represents a follow, and must be located individual when the related WATCHES row records the date of a spatial location. This means that the ROLES row related to the event must have a ROLES.Participant value equal to the WATCHES.AnimID of the WATCHES row related to the map location event.

Both the EVENTS.Start and EVENTS.Stop columns record the time the individual was at the recorded location. This means the value of the EVENTS.Start column must equal the value of the EVENTS.Stop column.

When the located individual is the focal of a follow – when the related WATCHES.Type value is F – the time of the spatial recording should occur when the focal was under observation. The system will generate a warning when there is not an ARRIVALS related row that records the presence of the focal at the time the spatial observation occurred. This means that a warning will be generated when there is no related EVENTS row where the Behavior code is ARR and the EVENTS.Start value is less than or equal to the time of the map location event value and the EVENTS.Stop value is greater than or equal to the time of the location event, and the event has a related ROLES row where the ROLES.Participant is the located individual.

For map location events, the EVENTS.Certainty column must be 1.

MATE (Mating)

The EVENTS row must be associated with either a follow or an non-follow mating observervation. This means the WID column must reference a WATCHES row with either a WATCHES.Type value of F or a WATCHES.Type value of M.

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

The ROLES rows related to the event, the rows with a ROLES.EID value equal to the EVENTS.EID value, designates the individuals involved in the mating event. The ROLES.Role code of each individual that the ROLES table relates to the mating event describes whether that individual was male or female.

There should be exactly two ROLES row related to the mating event. Only the codes Actor and Actee may be used as ROLES.Role code values. The system will generate a warning when there are not exactly two ROLES rows related to a mating event. The ROLES.Participant should be male, must have a BIOGRAPHY_DATA.Sex value of M, when the ROLES.Role value is Actor. The system will generate a warning when the male is not the actor. The ROLES.Participant should be female, must have a BIOGRAPHY_DATA.Sex value of M, when the ROLES.Role value is Actee. The system will generate a warning when the female is not the recipient.

Both the EVENTS.Start and EVENTS.Stop columns record the time the mating was observed. This means the value of the EVENTS.Start column must equal the value of the EVENTS.Stop column.

For mating events, the EVENTS.Certainty column must be 1.

OS (Other Species)

The EVENTS row must be associated with a follow. This means the WID column must reference a WATCHES row with a WATCHES.Type value of F.

A related row should exist on either SPECIES_PRESENT or on HUMANS. This means, there should either be a row on HUMANS with an HUMANS.EID value of the event’s EID, or there should be a row on SPECIES_PRESENT with a SPECIES_PRESENT.EID value of the event’s EID. The system will generate a warning when there is neither a HUMANS nor a SPECIES_PRESENT row related to this type of event. There can be at most one of these related HUMANS or SPECIES_PRESENT rows.

There can be no ROLES rows related to the event.

For other species events, the EVENTS.Certainty column must be 1.

PG (Pantgrunt)

The EVENTS row must be associated with either a follow or an non-follow pantgrunt observervation. This means the WID column must reference a WATCHES row with either a WATCHES.Type value of F or a WATCHES.Type value of P.

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

The ROLES rows related to the event, the rows with a ROLES.EID value equal to the EVENTS.EID value, designates the individuals involved in the pantgrunt event. The ROLES.Role code of each individual that the ROLES table relates to the pantgrunt event describes whether that individual gave or received the pantgrunt.

There should be exactly two ROLES row related to the pantgrunt event. Only the codes Actor, Actee, and Mutual may be used as ROLES.Role code values. The system will generate a warning when there are not exactly two ROLES rows related to a pantgrunt event.

The participants in a pantgrunt 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 the pantgrunt was observed. This means the value of the EVENTS.Start column must equal the value of the EVENTS.Stop column.

For pantgrunt events, the EVENTS.Certainty column must be 1.

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.

WID (Watch period IDentifier)

The WATCHES.WID that identifies the follow during which the event was recorded. The value of this column cannot be changed.

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:

AARR (Arrival at the feeding station)

A row must exist on ARRIVALS_A

AGG (Aggression)

A row must exist on AGGRESSIONS.

AGSCAN (attendance SCAN interval Groomings)

There is no event-specific table containing further detail.

ARR (Arrival)

A row must exist on ARRIVALS.

BREC (B-RECord note)

A row must exist on BRECORD_NOTES.

UTM (UTM Location)

A row must exist on LOCATIONS_UTM.

FOOD (Food)

A row must exist on FOOD_EVENTS.

GROOM (Grooming)

A row must exist on GROOMINGS.

GSCAN (follow SCAN interval Groomings)

A row must exist on GROOM_SCANS_B.

MATE (Mating)

A row must exist on MATINGS.

PAPER (PAPER map location)

A row must exist on LOCATIONS_PAPER.

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.

That said, the precise semantics of this column depend on the type of event being recorded – the EVENTS.Behavior value.

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. As with many other time values, this value is precise to the minute. The “ending minute” recorded in this column is an “inclusive endpoint”, the event finished occurring, but was ongoing, during the designated minute.

That said, the precise semantics of this column depend on the type of event being recorded – the EVENTS.Behavior value.

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 observation. This column has no meaning for some Behavior values. The semantics of this column changes, depending on the type of event that is recorded – depending on the EVENTS.Behavior value.

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.

Footnotes

[1] (1,2)

With the caveat that there are two ways to record a focal’s location, by map sequence number and by UTM coordinates and an individual may have their location at a given time recorded using both methods. These two methods are not required to be in-sync.

Page last generated: 2026-07-05 18:38:43 UTC