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]
It may be more convenient to use the PANTGRUNTS_VIEW view, than to use the PANTGRUTS table.
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.
The system will generate a warning if the community of the follow related to the pantgrunt information, or that of the WATCHES row that exists to support the pantgrunt record, is not the community associated with the pantgrunt record. This means, if the PANTGRUNTS.CommID is not the WATCHES.CommID of the related WATCHES row.
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.
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 exists because of the way the community was recorded in the old MS Access database. There, the community was recorded twice, once in the follow and again with the pantgrunt information.
When there is no related follow, there is still a related WATCHES row that exists solely to provide information concerning pantgrunt data. In this case the community information in the WATCHES row was initially the same as the value of this column. But the data could change and become out of sync.
This column exists so no information was lost in the conversion of the MS Access data to SokweDB. At some point in the future, perhaps when all inconsistencies between the value of this column and the community information recorded elsewhere are resolved, this column may be removed from this table.
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¶
Code for the person who extracted the pantgrunt information from
the written records and prepared it for data entry into the
database.
A PEOPLE.Person value. This column may not be NULL.
Page last generated: 2026-07-05 18:38:43 UTC