WATCHES

WATCHES contains one row, per date, per individual, whenever there was an intention to observe a given individual on a given date. It also contains one row for every date there was an ad-hoc observation not associated with any particular individual. There is not a row for every day every individual was observed because SokweDB contains data on individuals collected due to proximity with the intended target of observation.

Examples of intended observations include the a follow of a focal and the regular observation of individuals at the feeding station. WATCHES contains one row for each follow, and contains one row per day, per individual observed at the feeding station.

Examples of ad-hoc observations not associated with any one individual are observations of pantgrunts or matings recorded during happenstance encounters.

The Type column is used to distinguish and identify the various important categories: follows, feeding station observations, etc.

The available Type values are:

A (Attendance)

Each row represents a day during which a chimpanzee was observed at the feeding station. When a given chimpanzee is observed at the feeding station more than once per-day, there are multiple EVENTS rows, with an EVENTS.Behavior value of AARR, related to the WATCHES row recording the presence of the individual at the feeding station on the given day.

The AnimID column contains the BIOGRAPHY_DATA.AnimID of the individual that appeared at the feeding station.

The CommID column contains the code for the community the observers recorded when the attendance was taken; the COMM_IDS.CommID of the community. This value is not validated against the arriving individual’s record of community membership as recorded in other database content.

The system will generate a warning when a WATCHES row that represents attendance does not have a record of attendance – an ARRIVALS_A related row – that records the presence of the individual. This means that a warning is generated when an individual does not have a related EVENTS row where the Behavior code is AARR, and a ROLES row, related to the event, where the ROLES.Participant has the same value as the AnimID column.

The system will generate a warning if the n/a code is assigned to a female, an individual with a BIOGRAPHY_DATA.Sex value of F.

The system will generate a warning if any code other than the n/a code is assigned to an individual who is not a female, an individual with a BIOGRAPHY_DATA.Sex value that is not F.

Except for the unknown female individuals, those with a BIOGRAPHY_DATA.AnimID of MGF, or MGF2, or MGF3, the system will generate a warning if the U code is assigned to a female less than 5 years old or more than 14 years old.

Except for the unknown female individuals, those with a BIOGRAPHY_DATA.AnimID of MGF, or MGF2, or MGF3, the system will generate a warning if a code that is not one of n/a, U, 0, and MISS is assigned to a female that is at least 8 years old and less than or equal to 60 years old.

For any given individual there may not be more than one record of daily attendance at the feeding station on any given day. This means, the combination of Type, AnimID and Date must be unique. If an individual arrives at and leaves the feeding station multiple times on a single day, the one WATCHES row has multiple related rows on the EVENTS table.

B (B-Record taken)

Each row represents a date on which an individual has B-Record notes translated into English, but there is no follow on record in the database.

The AnimID column contains the BIOGRAPHY_DATA.AnimID of the individual.

The CommID column contains the code for the community recorded along with the B-Record notes; the COMM_IDS.CommID of the community. This is not necessarily the community the individual is a member of, although it usually is.

There may only be one row on WATCHES per day to record an individual who has translated B-Record notes. This means, the combination of Type, AnimID and Date must be unique. If there were multiple times on a single day that B-Record notes were taken, the one WATCHES row is related to multiple rows on the EVENTS table.

F (Follow)

Each row represents a date during which observers were assigned to follow a focal individual.

A follow may or may not have any related observations, related EVENTS rows.

The AnimID column contains the BIOGRAPHY_DATA.AnimID of the focal of the follow.

The CommID column contains the code for the community the observers are associated with and intended to follow; the COMM_IDS.CommID of the community. This is not necessarily the community the focal is a member of, although it usually is.

The system will generate a warning when a WATCHES row that represents a follow does not have a ARRIVALS related row that records the presence of the focal. This means that warning is generated when a WATCHES row with a Type value of F does not have a related EVENTS row where the Behavior code is ARR, and a ROLES row, related to the event, where the ROLES.Participant has the same value as the follow’s AnimID column.

A follow must have at least one related FOLLOW_OBSERVERS rows, to record the observers scheduled to conduct the follow. This condition is checked on transaction commit.

There may only be one row on WATCHES to record a follow of any given individual on any given day. This means, the combination of Type, AnimID and Date must be unique.

G (Attendance Groom scan)

Each row records a date on which groomings were scanned for on periodic intervals. There is one WATCHES row of this type per date.

The expectation is that the individual associated with the scan (not the grooming), the individual recorded in the AnimID column, will always be UNK. The system will generate a warning when the associated individual is not UNK, when AnimID is not UNK.

The AnimID column contains little information that is useful, because feeding station groom scans were not associated with any type of observation that specifically targeted a particular individual.

The CommID column contains the code for the community recorded at along with the pantgrunt; the COMM_IDS.CommID of the community. This is not necessarily the community the individual(s) involved in the grooming is(are) a member of, although it usually is.

There may only be one row on WATCHES per day to record interval scans for grooming at the feeding station. This means, the combination of Type and Date must be unique. When multiple individuals were found to be grooming, during interval scans for grooming conducted at the feeding station on any given day, the one WATCHES row has multiple related rows on the EVENTS table.

L (Location)

Each row represents a date on which an individual was spatially located.

The AnimID column contains the BIOGRAPHY_DATA.AnimID of the spatially located individual.

The CommID column contains the code for the community recorded when the location was recorded in the field; the COMM_IDS.CommID of the community. This is not necessarily the community the located individual is a member of, although it usually is.

There may only be one row on WATCHES per day to record an individual who was spatially located. This means, the combination of Type, AnimID and Date must be unique. If an individual’s location is recorded multiple times on a single day, the one WATCHES row is related to multiple rows on the EVENTS table.

M (Mating)

Each row records a date on which individuals were observed to mate, when there is no follow assocated with the mating. There is one WATCHES row of this type per date, per some usually non-meaningful BIOGRAPHY_DATA.AnimID – often UNK.

The AnimID column contains little information that is useful. The AnimID column contains the BIOGRAPHY_DATA.AnimID of the individual that was purportedly the focal of a follow, but no such follow of the individual exists. When there is no focal on record, for whatever reason, the special BIOGRAPHY_DATA.AnimID value of UNK, representing an unknown individual – or, in this case, “no individual”, is expected to be the AnimID value.

The CommID column contains the code for the community recorded at along with the mating; the COMM_IDS.CommID of the community. This is not necessarily the community the mating individuals are a member of, although it usually is.

There may only be one row on WATCHES per day, per individual recorded along with the mating data. This means, the combination of Type, AnimID and Date must be unique. When multiple matings are recorded in a follow, or are recorded on some day when there is no follow, the one WATCHES row has multiple related rows on the EVENTS table.

P (Pantgrunt)

Each row records a date on which an individual was observed to pantgrunt, when there is no follow assocated with the pantgrunt. There is one WATCHES row of this type per date, per some usually non-meaningful BIOGRAPHY_DATA.AnimID – often UNK.

The AnimID column contains little information that is useful. The AnimID column contains the BIOGRAPHY_DATA.AnimID of the individual that was purportedly the focal of a follow, but no such follow of the individual exists. When there is no focal on record, for whatever reason, the special BIOGRAPHY_DATA.AnimID value of UNK, representing an unknown individual – or, in this case, “no individual”, is expected to be the AnimID value.

The CommID column contains the code for the community recorded at along with the pantgrunt; the COMM_IDS.CommID of the community. This is not necessarily the community the pantgrunting individual(s) is(are) a member of, although it usually is.

There may only be one row on WATCHES per day, per individual recorded along with the pantgrunt data. This means, the combination of Type, AnimID and Date must be unique. When multiple pantgrunts are recorded in a follow, or are recorded on some day when there is no follow, the one WATCHES row has multiple related rows on the EVENTS table.

WATCHES rows of the B-Record type, Type = B, may only exist when there is not a follow-type row, Type = F, for the individual on the given date. This means that if an individual has translated B-Records on a day they are followed, there cannot be a row on WATCHES for that individual for that day with a Type of B, and vice-versa.

WATCHES rows of the location type, Type = L, may only exist when there is not a follow-type row, Type = F, for the individual on the given date. This means that if an individual is spatially located on a day they are followed there cannot be a row on WATCHES for that individual for that day with a Type of L, and vice-versa.

WATCHES rows of the mating type, Type = M, may only exist when there is not a follow-type row, Type = F, for the individual on the given date. This means that if an individual is a participates in a mating event on a day they are followed there cannot be a row on WATCHES for that individual for that day with a Type of M, and vice-versa.

WATCHES rows of the pantgrunt type, Type = P, may only exist when there is not a follow-type row, Type = F, for the individual on the given date. This means that if an individual pantrgunts on a day they are followed there cannot be a row on WATCHES for that individual for that day with a Type of P, and vice-versa.

The intention is that follows, WATCHES rows where the Type = F, be used where data on a focal is recorded. The system will generate a warning when there is a follow for which there are only B-Record related events. The system will generate a warning when there is a follow for which there are only location related events. The system will generate a warning when there is a follow for which there are only mating related events. The system will generate a warning when there is a follow for which there are only pantgrunt related events.

The Date must be during a period when the watched individual was under study. This means that Date must be on or after the watched individual’s – the AnimID’s – BIOGRAPHY_DATA.EntryDate and on or before the watched individual’s BIOGRAPHY_DATA.DepartDate.

WID (Watch period 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.

AnimID (focal or other watched ANIMal ID)

The BIOGRAPHY_DATA.AnimID identifying the individual under observation.

The designated individual that is the focal of a follow, or the individual observed at the feeding station, or UNK – the unknown individual –, etc., depending on the Type value.

This column may not be NULL.

CommID

A code for the community the observers have recorded for association with the watch period. This is not necessarily the community the AnimID is a member of, although it usually is. This column may not be NULL.

Date

The date when the watch period was conducted. This date may not be before 1960-07-14. This column may not be NULL.

Type

The type of watch period. This column categories kinds of observation made and is loosely tied to the data collection protocol used.

One of the following values:

A (Attendance)

B (B-Record)

F (Follow)

G (Attendance Groom Scan)

L (Location)

Only used when there is no follow to use.

P (Pantgrunt)

Only used when there is no follow to use.

See overview of the WATCHES table, above, for more information.

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

Notes

Free form textual notes on the watch period. This column may be empty text. It need not contain characters, but it may not contain only whitespace characters. This column may not be NULL.

Page last generated: 2026-07-05 18:38:43 UTC