GROOM_SCANS_B

Each row, taken together with the related EVENTS row, represents a grooming event recorded during a follow, over a regular, periodic, sampling interval, during which period all observed grooming pairs were recorded. Groomings are recorded as dyadic pairs.

In this data set, all groomings observed in periodic 5 minute intervals were recorded.

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

Caution

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

The related EVENTS row must be a grooming interval sampling event; it must have an EVENTS.Behavior value of GSCAN. This related EVENTS row supplies the time of the grooming 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 groom sampling 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 grooming and is related to the participants in the groom sampling event.

This column may not be NULL.

Others

A boolean value indicating whether others participated in the grooming. This column may not be NULL.

Duplicate

A boolean value indicating whether the grooming is duplicated due to overlapping follows of different focals. When there are duplicates only one of the duplicates is so marked. This column may not be NULL.

Extractedby

The person who extracted the grooming 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