Social And Multiparty Interactions

ACTIVITIES

The activities distinguished during in focal point observation data collection. This table restricts which activities can be used with which sampling protocol (SAMPLES.Stype).

Vocabulary For

ACTIVITIES defines values for the Activity of the POINT_DATA table.

Key Name: Activity

Activity

Special Values

The value F has a special meaning to the system. It indicates feeding and triggers a required Foodcode in POINT_DATA.Foodcode.

The Juvenile Column

When TRUE the activity can be used in focal points sample data, POINT_DATA rows, collected using the juvenile/infant focal point sampling protocol -- when the related SAMPLES.Stype is J. When FALSE the activity value may not be used in focal point observation data collected using the juvenile focal point sampling protocol.

This column may not be NULL.

The Female Column

When TRUE the activity can be used in focal points sample data, POINT_DATA rows, collected using the female focal point sampling protocol -- when the related SAMPLES.Stype is F. When FALSE the activity value may not be used in focal point observation data collected using the female focal point sampling protocol.

This column may not be NULL.

ACTS (Interaction Types)

The different kinds of (non-multiparty) interactions between individuals which may be recorded.

The various kinds of interactions may be grouped together into larger categories, which are themselves valid kinds of interactions. The Class column is used for this purpose. The Class column contains an Act value identifying the larger class of interactions to which the interaction belongs. If the interaction does not belong to a larger category, the Class should contain the row's own Act value. Only 1 level of classification hierarchy is allowed -- the ACTS row referenced in the Class column must have a Class value equal to its Act value.

Rows that contain a TRUE value in the Retired column may not be referred to by newly created database rows, although, presumably older, pre-existing rows may contain the Act values of these retired rows. Should it be necessary to create such new rows, retired ACTS may be temporarily un-retired.

Vocabulary For

ACTS defines values for the Act column of INTERACT_DATA.

Key Name: Act

Act

Special Values

All of the Class codes on ACTS have a special meaning to the system's programs. New Class codes may not be created and rows that represent the classifications, have an Act equal to their Class, cannot have their Act, Class, or Descr values changed.[235]

The Class column

The ACTS row of interaction classification. (See above.) This column may not be NULL.

The Retired column

A TRUE value in this column indicates that the Act value may not be used in new rows added to Babase. This column must contain either TRUE or FALSE.

DATA_STRUCTURES (Data structures produced by the palmtop)

One row for each version of data structure produced by the palmtops.

Note

The primary purpose of this table is to ensure that the data coming off the palmtop is correctly interpreted and loaded into the right tables. The structure and semantics of the data collected by the palmtop is determined by the setup file, but various setup files can produce the same output. The DATA_STRUCTURES table contains only one row for every data layout produced by the palmtops.

For further comments see the SETUPIDS file.

Vocabulary For

DATA_STRUCTURES defines vocabulary for SETUPIDS.Data_Structure.

Key Name: Data_Structure

Data_Structure

An integer.

Special Values

The Data_Structure value 1 is the data structure understood by the Psionload program.

CONTEXT_TYPES (multiparty Interaction Context Categories)

The social contexts in which multiparty interactions occur.

Vocabulary For

CONTEXT_TYPES defines values for MPIS.Context_type.

Key Name: Context_type

A 1 character code identifying the social context.

Special Values

Special CONTEXT_TYPES

N

No context. The MPIS.MPIS-Context column must be NULL when this code is used.

C

Consortship. The multiparty interaction occurred in the context of a consortship.

The MPIS.MPIS-Context column must be NULL when this code is used. The MPIS.Context_type column must be C when a related CONSORTS row exists. The system will generate a warning when the MPIS.Context_type column is C and there is no related CONSORTS row.

FOODCODES (Food item Codes)

The different food items eaten by baboons.

Vocabulary For

FOODCODES defines values for POINT_DATA.Foodcode.

Key Name: Foodcode

Foodcode

The Ftype column

Food items are themselves categorized into types. This column contains the type of the food item. Valid food type values are those stored in the FOODTYPES.Ftype column.

Special Values

There are no special FOODCODE values, however it is worth remarking on the POINT_DATA.Activity F value, which has special meaning to the system. The POINT_DATA.Foodcode column must contain a value when and only when POINT_DATA.Activity is F, otherwise POINT_DATA.Foodcode must be NULL.

FOODTYPES (Food Types)

Food items are categorized into broader classifications using the codes defined on the FOODTYPES tables.

Vocabulary For

FOODTYPES defines vocabulary for the Ftype column of the FOODCODES table.

Key Name: Ftype

Ftype

Special Values

None.

KIDCONTACTS (spatial relationship between mother and infant)

The different spatial relationships between mother and infant recorded during adult female all-occurrences point sampling.

Vocabulary For

KIDCONTACTS defines vocabulary for the Kidcontact column of the FPOINTS table.

Key Name: Kidcontact

Kidcontact

Special Values

None.

MPIACTS (Multiparty Interaction Types)

The different kinds of dyadic interactions which may be recorded as interactions occurring during a multiparty interaction event. There are 4 mutually exclusive categories of interactions: Agnoisims, Requests for help, Help given, and Other.

The Decided column cannot be TRUE unless the kind of the act is an agonism -- the Kind column is A.

Because the first interaction of a multiparty interaction must be an agonism Multi_first cannot be TRUE unless Kind is A.

Note

Although Babase stores multiparty interactions using a data structure similar to that used to store non-multiparty interactions the data sets are separate, different kinds of interactions are recorded using different codes, and the interactions are never recorded in both data sets.

Vocabulary For

MPIACTS defines values for the MPIAct column of MPI_DATA.

Key Name: MPIAct

MPIAct

Special Values

The value AH must be the code used to indicate the giving of active help. The value PH must be the code used to indicate the giving of passive help. These codes are tested for in the process of generating warnings indicating that the MPI_DATA.Active value may be incorrect.

Some values have special meaning to the Upmpi program, in that the program changes act values in the uploaded file to particular values. See the documentation on this for more detail.

The Kind of act column

This column classifies the kind of interaction into one of 4 distinct types, as listed below.

MPIACTS.Kind values

A

An Agonism interaction.

R

A Request for help.

H

Help given.

O

Other.

This column may not be NULL.

The Decided column

A TRUE value in this column indicates that the action was an agonism resulting in a definite winner and loser, FALSE indicates otherwise.

This column may not be NULL.

The Multi_first column

A TRUE value in this column indicates that the MPIAct code can be used as a MPI_DATA.MPIAct value when there is more than one MPI_DATA row for a multiparty interaction having a Seq value of 1 -- such interactions which initiate a collection of multiparty interactions need not be dyadic, they can occur between more than 2 individuals.[236] All other interactions (those where Multi_first is FALSE) which begin a collection of multiparty interactions (those having a Seq value of 1) must involve just 2 individuals.

This column may not be NULL.

NCODES (Neighbor classifications)

The different classification of neighbor distinguished during in focal point observation data collection. This table restricts which neighbor classifications can be used with which sampling protocol (SAMPLES.Stype).[237]

A NCODES row may not have a Requires of NULL and a Nsex value of O.

Vocabulary For

NCODES defines vocabulary for the Ncode column of the NEIGHBORS table.

Key Name: Ncode

Ncode. The value of this column may not be changed.

Special Values

None.

The Juvenile Column

When TRUE the neighbor classification can be used in focal points sample data, POINT_DATA rows, collected using the juvenile/infant focal point sampling protocol -- when the related SAMPLES.Stype is J. When FALSE the neighbor classification value may not be used in focal point sample data collected using the juvenile focal point sampling protocol.

This column may not be NULL.

The Female Column

When TRUE the neighbor classification can be used in focal points sample data, POINT_DATA rows, collected using the female focal point sampling protocol -- when the related SAMPLES.Stype is F. When FALSE the neighbor classification value may not be used in focal point sample data collected using the female focal point sampling protocol.

This column may not be NULL.

Requires (Requires another neighbor)

A Ncode. When a Ncode has a value in this column then the Ncode cannot be used unless the point observation (POINT_DATA row) already has another NEIGHBORS row that uses the referenced value. For example, supposing Ncode 2 is the second nearest neighbor and Ncode 1 is the nearest neighbor.[238]When Ncode 1 is placed in in Ncode 2's Requires column, Babase will not allow a sample to have a second nearest neighbor without first having a nearest neighbor.

This column may be NULL, in which case the only requirement is that the same Ncode not be used twice in one point observation.

Nsex (Neighbor Sex requirement)

The sex that the neighbor must have. This is complicated because it may rely on the sex of the neighbor with the Ncode specified in the Requires column. The values the Nsex column may contain and their meanings are:

The NCODES.Nsex Values
Code Mnemonic Definition
A Any The neighbor with this Ncode may be of any sex.
M Male The neighbor with this Ncode must be male.[239]
O Opposite The neighbor with this Ncode must be of a different sex than the neighbor with the Requires Ncode. Note that because there are 3 sexes, male, female, and unknown, this does not strictly conform with the field monitoring guide which only takes males and females into account. If this is a problem then we need to do something about it.

Caution

Neighbors with a Unksname rather than a Sname are always considered to be of the opposite sex -- they satisfy the O Nsex code.

This column must not be NULL.

Nunique (Neighbor must be Unique)

A boolean value. When TRUE then the Sname must be unique among all the neighbors of a particular point observation (POINT_DATA). When FALSE the Sname need not be unique.

This column must not be NULL.

PALMTOPS (the Palmtop hand-held data collection units)

One row for each Palmtop hand-held computer.[240]

Note

From a research perspective there is no particular reason why this information would ever be useful as what is important is the software that is running on the Palmtop.

Vocabulary For

PALMTOPS defines vocabulary for SAMPLES.Palmtop.

Key Name: Palmtop

Palmtop

An integer.

Special Values

None.

PARTUNKS (problem identifying a multiparty interaction participant)

The different reasons why a participant in a multiparty interaction is unable to be identified during data collection.

A Unksname value must not appear as a BIOGRAPH.Sname value.

Vocabulary For

PARTUNKS defines vocabulary for the Unksname column of the MPI_PARTS table. It is also used by the Upmpi program to test the uploaded data for unknown participants in a consortship interaction.

Key Name: Unksname

Unksname

Special Values

None.

POSTURES

The postures distinguished in focal point observation data collection.

Vocabulary For

POSTURES defines values for POINT_DATA.Posture.

Key Name: Posture

Posture

Special Values

None.

The Juvonly Column

When TRUE the posture value can only be used in focal points sample data, POINT_DATA rows, collected using the juvenile focal point sampling protocol -- when the related SAMPLES.Stype is J. When FALSE the posture value may be used in any focal point sampling protocol.

This column may not be NULL.

PROGRAMIDS (Program versions used on the palmtop)

One row for each version of each program used for data collection on the palmtop hand-held computers.

Note

It is the setup file that determines the operation of the data collection program. See SETUPIDS.

Note

Although not every setup file can be used with every version of every program, Babase makes no attempt to validate the setup files against the program files, or vice versa. This is because the data are expected to be generated by the palmtop programs and, unless they lie about the program they are running and the setup file used, whatever program id is reported must, ipso facto, work with the reported setup file.

Note

The primary purpose of this table is to avoid storing relatively lengthy identical strings on the SAMPLES table. This table would probably not be worth having were not the program ID strings reported by the palmtops so long, and did we not need the SETUPIDS table, which is very similar to this table.

Vocabulary For

PROGRAMIDS defines vocabulary for SAMPLES.Programid.

Key Name: Programid

Programid

An integer.

Special Values

None.

PID_String (ProgramID String)

The string the palmtop reports as its program id.

This column may not be NULL. This column may not be empty, it must contain characters, and it must contain at least one non-whitespace character.

SETUPIDS (Setup files used on the palmtop)

One row for each setup file used for data collection on the palmtop hand-held computers.

Note

The primary purpose of this table is to ensure, via its relation with the DATA_STRUCTURES table, that the data coming off the palmtop is correctly interpreted and loaded into the right tables. The table also allows Babase to save space on the SAMPLES table by storing the small Setupid integer rather than the relatively long setup ID strings reported by the palmtops.

Warning

The setupid should determine the structure and semantics of the palmtop data files. If this assumption is violated, e.g. by having two different Psion programs produce different results from the same setup file, then the Psionload program may do bad things to the database.

For further comments see the PROGRAMIDS file.

Vocabulary For

SETUPIDS defines vocabulary for SAMPLES.Setupid.

Key Name: Setupid

Setupid

An integer.

Special Values

None.

SID_String (SetupID String)

The string the palmtop reports as its setup id.

Data_Structure

The version of the data structure produced by the palmtops using the setup file. Valid Data_Structure values are those given by the values stored in the DATA_STRUCTURES.Data_Structure column.

This column may not be NULL. This column may not be empty, it must contain characters, and it must contain at least one non-whitespace character.

SUCKLES (infant suckling activity)

Vocabulary describing the nature of an infant's suckling activity.

Vocabulary For

Suckles defines the vocabulary for the Kidsuckle column of the FPOINTS table.

Key Name: Suckle

Suckle

Special Values

None.



[235] Except by suitably privileged individuals. See Special Values.

[236] Although they are still recorded as dyadic pairs, there can be more than one pair with a sequence number of 1

[237] It seems easiest at this time to create the columns Juvenile and Female rather than add another table and have a fully normalized database.

[238] As is indeed the case as of this writing.

[239] There is no code for female because at present the protocols do not require one.

[240] Although all the computers used for data entry in the field are Psions, this will not always be the case. Hence, the generic name PALMTOPS.


Page generated: 2021-09-17T11:16:36-04:00.