AGGRESSIONS

Each row, taken together with the related EVENTS row, represents an aggression event recording during a follow. Aggressions are recorded as dyadic pairs.

When there are multiple individuals, whether aggressor or recipient, involved in simultaneous aggressive behavior, there should be multiple rows in the AGGRESSIONS table. There should be one row for each dyad. When multiple individuals are involved in aggressive behavior this is flagged in the MultiAggressors and MultiRecipients columns. The system generates a warning when either of these columns are TRUE and there are not multiple dyads present, having identical follow and time information, and sharing one of the individuals involved.

Caution

The system’s design cannot distinguish between multiple multi-party aggression events that are recorded as part of a single follow and occur at a given time, and a single, larger, multi-party aggression event recorded in the given follow at the given time.[1] [2]

The related EVENTS row must be an aggression event; it must have an EVENTS.Behavior value of AGG. This related EVENTS row supplies the time of the aggression and relates to the follow, and the ROLES role related to the event supplies information on the individual arriving and departing.

The system will generate a warning if a participant in the aggression is not present at the time of the aggression. This means that the related ROLES.Participant must have been recorded in the follow as an arriving individual and the EVENTS row related to the arrival has an EVENTS.Start that is the same as or before the aggression time and an EVENTS.Stop that is the same or after the aggression time.

The system will generate a warning if the community of the follow is not the community associated with the aggression event. This means, if the AGGRESSIONS.Community is not the FOLLOWS.Community of the follow.

For further information, including additional data integrity rules, see the documentation of the EVENTS table.

The AggressorBehavior and RecipientBehavior columns are extracted from the FullAccount column, which is itself sometimes extracted from other sources. Care must be taken to ensure consistently between these columns and their sources.

AgID (Aggression 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.

EID (Event ID)

The EVENTS.EID identifying the aggression event. The related event contains information on the time of the aggression and is related to the participants in the aggression event.

This column may not be NULL.

Decided

A boolean, TRUE when there was a clear winner or loser. FALSE when there was not, or when there is no data. See the AGGRESSION_EVENT_LOG table for information as to whether or not this column contains useful information.

This column may not be NULL.

MultiAggressors

A boolean, whether or not there were multiple aggressors. True when there were multiple aggressors. False when there were not multiple aggressors. This column may not be NULL.

MultiRecipients

A boolean, whether or not there were multiple recipients of aggression. True when there were multiple recipients of aggression. False when there were not multiple recipients of aggression, and for rows representing record-keeping before the tracking of multiple recipients was systematized. This column is only valid from 1994 onward, with the exception of female-to-female decided aggression. This column may not be NULL.

BadObs (BAD OBserversion)

A boolean, whether or not the record of the observation was complete. This column may not be NULL.

Bristle

A boolean, whether or not the one of the participants was recorded as bristling. True when bristling occurred. False when bristling did not occur, and for rows representing record-keeping before the tracking of bristling was systematized. This column is only valid from 1994 onward. This column may not be NULL.

Display

A boolean, whether or not the one of the participants was recorded as displaying. True when a display occurred. False when a display did not occur, and for rows representing record-keeping before display tracking was systematized. This column is only valid from 1994 onward. This column may not be NULL.

Chase

A boolean, whether or not the one of the participants was recorded as chasing. True when a chase occurred. False when a chase did not occur, and for rows representing record-keeping before the tracking of chasing was systematized. This column is only valid from 1994 onward. This column may not be NULL.

Contact

A boolean, whether or not the one of the participants was recorded as contacting. True when contact occurred. False when contact did not occur, and for rows representing record-keeping before the tracking of contact was systematized. This column is only valid from 1994 onward. This column may not be NULL.

Vocal

A boolean, whether or not the one of the participants was recorded as vocalizing. True when vocalization occurred. False when vocalization did not occur, and for rows representing record-keeping before the tracking of vocalization was systematized. This column is only valid from 1994 onward. This column may not be NULL.

Severity

A value indicating the severity of the aggression. AN AGG_SEVERITIES.Severity value.

This column may not be NULL.

AggressorBehavior

Text describing the behavior exhibited by the aggressor.

This is extracted from the FullAccount column.

This column may not be NULL.

RecipientBehavior

Text describing the behavior exhibited by the recipient of the aggression.

This is extracted from the FullAccount column.

This column may not be NULL.

FullAccount

Text providing an account of the aggression event.

This column may not be NULL.

Community

The community of the follow, retained as part of the data collected on aggression for historical purposes. The COMM_IDS.CommID of the of the focal.

Note

This is not the canonical source of information on the focal’s community at the time of observation or the community under observation when the data was collected. It may, in fact, differ from the community recorded elsewhere.

This column may not be NULL.

Extractedby

The person who extracted the aggression information from the written records and prepared it for data entry into the database. This column may not be NULL.

[1]

This is because this information has not been systematically entered into a computerized database, so the cost/benefit ratio does not warrant designing SokweDB in a manner that allows it to track such information.

[2]

Individual aggression events recorded within a single follow that occur at the same time as other individual aggression events occurring at the given time in the given follow are distinguished from each other, and from multi-party aggression events occurring at the given time in the given follow, only because their MultiAggressors and MultiRecipients values are FALSE.

Page last generated: 2026-05-14 16:59:14 UTC