PANTGRUNTS_VIEW¶

Each row represents a dyadic pantgrunt interaction between two individuals. Rows resemble the MS Access database structure, which may make the data easier to work with.

The view puts the individual performing the pantgrunt and the individual receiving the pantgrunt in separate columns. There is a flag to indicate whether the pantgrunting is mutual; when TRUE ,there is not meaning to the placement of the interacting individuals into these two columns.

Definition¶

CREATE OR REPLACE VIEW pantgrunts_view (
  date
 ,animid
 ,time
 ,actor
 ,recipient
 ,multiactors
 ,multirecipients
 ,twosided
 ,commid
 ,pg_commid
 ,source
 ,enteredby
 ,notes
 ,event_notes
  -- Administrative information
 ,type
 ,wid
 ,eid
 ,actor_pid
 ,recipient_pid
  )
  AS
    SELECT
      dyads.date AS date
     ,dyads.animid AS animid
     ,dyads.start AS time
     ,dyads.actor AS actor
     ,dyads.recipient AS recipient
     ,pantgrunts.multiactors AS multiactors
     ,pantgrunts.multirecipients AS multirecipients
     ,dyads.twosided AS twosided
     ,dyads.commid AS commid
     ,pantgrunts.commid AS pg_commid
     ,pantgrunts.source AS source
     ,pantgrunts.enteredby AS enteredby
     ,dyads.notes AS notes
     ,dyads.event_notes AS event_notes
     ,dyads.type AS type
     ,dyads.wid AS wid
     ,dyads.eid AS eid
     ,dyads.actor_pid AS actor_pid
     ,dyads.recipient_pid AS recipient_pid
     FROM dyads
       JOIN pantgrunts
            ON (pantgrunts.eid = dyads.eid);

ER Diagram¶

PANTGRUNTS_VIEW Entity-Relationship Diagram — PANTGRUNTS_VIEW¶

Columns of the PANTGRUNTS_VIEW View¶

The columns of the PANTGRUNTS_VIEW view¶
Column	From	Description
Date	WATCHES.Date	Date of pantgrunt
AnimID	WATCHES.AnimID	Focal of follow, or focal of a non-existant follow, or an un-interesting AnimID
Time	EVENTS.Start	Time of pantgrunt
Actor	ROLES.Participant	The BIOGRAPHY_DATA.AnimID of the individual pantgrunting, or mutually pantgrunting
Recipient	ROLES.Participant	The BIOGRAPHY_DATA.AnimID of the individual receiving the pantgrunt, or mutually pantgrunting
MultiActors	PANTGRUNTS.MultiActors	Boolean, `TRUE` when there were multiple pantgrunters
MultiRecipients	PANTGRUNTS.MultiRecipients	Boolean, `TRUE` when there were mulitple recipients of a pantgrunt
TwoSided	An expression based on ROLES.Role	Boolean, `TRUE` when both the Actor and the Recipient were pantgrunting to each other
CommID	WATCHES.CommID	The community identifier associated either with the follow or with the ad-hoc recording of the pantgrunt
PG_CommID	PANTGRUNTS.CommID	The community identifier associated with the record of the pantgrunt
Source	PANTGRUNTS.Source	Code for the source of the pantgrunt information
Notes	WATCHES.Notes	Textual notes on the follow or the ad-hoc observation of the pantgrunt
Event_Notes	EVENTS.Notes	Textual notes on the pantgrunt event
EnteredBy	PANTGRUNTS.EnteredBy	Code for the person who extracted the pantgrunt information from the written records
Type	WATCHES.Type	Type, reporting whether or not the pantgrunt was observed during a follow
WID	WATCHES.WID	Identifier of the related WATCHES row
EID	EVENTS.EID	Identifier of the related EVENTS and PANTGRUNTS rows
Actor_PID	ROLES.PID	Identifier of the ROLES row containing the individual performing the pantgrunt, or mutually pantgrunting
Recipient_PID	ROLES.PID	Identifier of the ROLES row containig the individual receiving the pantgrunt, or mutually pantgrunting

Operations Allowed¶

INSERT

INSERTing a row into PANTGRUNTS_VIEW inserts a row into PANTGRUNTS and two rows into into ROLES. One row may be inserted into EVENTS, and one may be inserted into WATCHES.

The columns EID, WID, AnimID, Date, and Time may all be used, in the various combinations described below, to relate new PANTGRUNTS and ROLES rows to existing EVENTS rows, or to create new EVENTS and WATCHES rows when they do not already exist.

If an EID is supplied, that is all that is required. The identified EVENTS row must already exist.

If an EID is not supplied, the columns WID, Date, and Time are used to query OBS to discover if a matching EVENTS row exists or if there is no match and a new one must be inserted. The Time column must be supplied in this case.

If a WID is supplied it is used, along with Time, to match against database content. If a WID is not supplied, the AnimID and Date columns must be supplied. Then they are used, along with Time, to match against database content.

If an existing EVENTS row matches, the new PANTGRUNTS row and the new ROLES rows are related to the EVENTS row so discovered. Otherwise they are related to the newly created EVENTS row.

INSERTing into PANTGRUNTS_VIEW inserts a row into DYADS. This means the rules regarding what data must be supplied when INSERTing into DYADS, and when DYADS re-uses existing rows or creates new rows, also apply to PANTGRUNTS_VIEW.

When existing rows are found in the database, all (non-NULL) data values supplied must match the data values that already exist.

The WID, EID, Actor_PID, and Recipient_PID columns do not have their values inserted into new rows. If non-NULL values are supplied for these columns they must match the values already existing in, or inserted into, the database.

UPDATE: This operation is not allowed.
DELETE: This operation is not allowed.

Page last generated: 2026-07-20 23:28:52 UTC