PANTGRUNTS

Each row, taken together with the related EVENTS row, represents a pantgrunt event recording during a watch period. The watch period may be a follow. Pantgrunts are recorded as dyadic pairs.

Should there be multiple individuals, whether the exhibitor or recipient, involved in simultaneous pantgrunt behavior, there should be multiple rows in the PANTGRUNTS table. There should be one row for each dyad.

Caution

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

The related EVENTS row must be a pantgrunt event; it must have an EVENTS.Behavior value of PG. This related EVENTS row supplies the time of the pantgrunt and relates to the follow, and the ROLES role related to the event supplies information on the individuals involved.

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

EID (Event ID)

The EVENTS.EID identifying the pantgrunt event. A unique, automatically generated, positive integer which serves to identify the row. The value of this column cannot be changed. The related event contains information on the time of the pantgrunt and is related to the participants in the pantgrunt event.

This column may not be NULL.

MultiActors

A boolean value. When TRUE, there were multiple actors performing pantgrunts. This column may not be NULL.

MultiRecipients

A boolean value. When TRUE, there were multiple recipients receiving pantgrunts. This column may not be NULL.

CommID

A code for the community involved in the pantgrunt event. A COMM_IDS.CommID value. This is not necessarily the community the focal is a member of. This column may not be NULL.

Source

A code for the source of the pantgrunt information. A PG_SOURCES.Code value. This column may not be NULL.

EnteredBy

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

[1]

More information related to this problem can be found in the documentation of the AGGRESSIONS table.

Page last generated: 2026-06-12 16:40:37 UTC