ROLES

Each row represents a participant in an event that occurred. Events occur during a watch period. The watch periods may be a follow, which may involve the focal of a follow or not, may be attendance taking of an individual at the feeding station, may be some variety of ad-hoc pantgrunt record, or may be some other type of watch period. Events may have zero or more participants involved; rows on EVENTS may have zero or more related rows on ROLES. Usually, there will be at least one participant. But this is not true of all events, for example events that are no more than a record of the presence of other species sighted during a follow.

The participant in the event is required to be under study on the date of the follow, for follow related events. This means that, when the event occurs during a follow, the WATCHES.Date related to the event must be between the Participant’s BIOGRAPHY_DATA.EntryDate and their BIOGRAPHY_DATA.DepartDate, inclusive of endpoints. If this is not the case the system will immediately raise an error. When the event occurs during attendance taking at the feeding station, the ATTENDANCE.Date related to the event should be between the Participant’s BIOGRAPHY_DATA.EntryDate and their BIOGRAPHY_DATA.DepartDate, inclusive of endpoints. If this is not the case the system will generate a warning.

The system will generate a warning if a participant is not present in the follow at the time of the given event. This means that, when the event occurred during a follow, the 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 starting time[1] of the given event and an EVENTS.Stop that is the same as or after the given event’s ending time[2]. When the event occurred during attendance taking at the feeding station, the ROLES.Participant must have been recorded at the feeding station as an arriving individual and the EVENTS row related to the arrival has an EVENTS.Start that is the same as or before the starting time[1] of the given event and an EVENTS.Stop that is the same as or after the given event’s ending time[2].

An individual can only be a participant once, in any given event. This means that the combination of Participant and EID must be unique.

The Role values of Actor and Actee are special. They are used in dyadic interactions, where they must be paired.

The Role value of Mutual is special. It is used in dyadic interactions, where their must be 2 rows in ROLES each of which uses this role.

For further information on the required, and expected, relationship between ROLES, EVENTS, and other tables see the documentation of the EVENTS table.

PID (Participant ID)

The EVENTS.EID that identifies the event in which the Participant played a role. The value of this column cannot be changed. This column may not be NULL.

EID (Event ID)

The EVENTS.EID that identifies the event in which the Participant played a role. The value of this column cannot be changed. This column may not be NULL.

Role

A code indicating the role played by the Participant in the event; a ROLE_CODES.Role value. The role code broadly describes the participants role in a behavioral event. For further detail the EVENTS.Behavior column must be examined. Depending on the behavior, there may be additional information found in other tables related to the event.

The value of this column cannot be changed. This column may not be NULL.

Participant

A AnimID identifying the individual participating in the event. This column may not be NULL.

Footnotes

[1] (1,2)

The given event’s EVENTS.Start value.

[2] (1,2)

The given event’s EVENTS.Stop value.

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