[Babase] Documentation with Cathrine's comments incorporated
Karl O. Pinc
babase@www.eco.princeton.edu
Sat, 30 Jul 2005 22:41:02 +0000
Hi,
I've updated the documentation sent out the other
day to incorporate Cathrine's comments.
Here again are the sections I'd like reviewed.
In addition to the previous sections I've also
included the URLs where the whole section
is not on one page (the appendix), and I've
added a new section "this document"
that I went and updated after speaking
with Cathrine.
The sections I want review of are, in order:
This Document
https://papio.biology.duke.edu/babase_system_html/index.html#tablenames
BIOGRAPH (Baboon Biographical Data)
Column Descriptions
https://papio.biology.duke.edu/babase_system_html/ar01s05.html
MEMBERS (Group Membership)
Column Descriptions
https://papio.biology.duke.edu/babase_system_html/ar01s14.html
CENSUS
Column Descriptions
https://papio.biology.duke.edu/babase_system_html/ar01s15.html
DEMOG (Demography Notes)
Column Descriptions
https://papio.biology.duke.edu/babase_system_html/ar01s16.html
Interpolation
Interpolation's 3 Fundamentals
Interpolation Visualized
The Interpolation Rules
Expectations and Implications
https://papio.biology.duke.edu/babase_system_html/ar01s24.html
A. Changes to Babase between 1.0 and 2.0
Changes to .Statdate
Changes To Interpolation and MEMBERS
Changes To The Sexual Cycle Information
https://papio.biology.duke.edu/babase_system_html/apa.html
https://papio.biology.duke.edu/babase_system_html/apas02.html
https://papio.biology.duke.edu/babase_system_html/apas03.html
Those who would like to email comments in the
context of the documentation text can
get the thin.txt file from papio.
I've appended a diff of the changes made
to the documentation. Note that many of the
changes are because the footnote numbers changed.
Karl <kop@meme.com>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
--------------<snip>--------------------
--- thin.txt.old 2005-07-29 02:53:43.000000000 -0500
+++ thin.txt 2005-07-30 16:35:01.000000000 -0500
@@ -232,27 +232,13 @@
design of the system, and procedures for maintaining the
data management system itself. This document does not
include the procedures actually used to enter data into the
- system,or the details of how to operate the systems
+ system ,or the details of how to operate the systems
programs. Neither does it include any instructions on the
operation or administration of the computer itself. Further
information on the topics not covered in this document can
be found in the Protocol for Data Management: Amboseli
Baboon Project document.
- All TABLE NAMES are in UPPER CASE letters while the columns
- are in lower case.
-
- Anyone who is changing or adding programs to the system
- should read this entire document. Section III The Master
- Tables is particularly important for all those using the
- system. Section V The Dataset Tables is of little interest
- to those who only want to retrieve information from the
- system. Section VI.B Useful Programs and Functions is of
- interest to the more sophisticated user. People who will
- not be programming need not read section VIII Standards,
- although sections VIII.A General Program Standards and
- VIII.B User Interface Standards may prove interesting.
-
The Protocol for Data Management: Amboseli Baboon Project
document is an important adjunct to the BABASE system, but
it is not considered part of the system itself because it
@@ -271,6 +257,90 @@
should be discussed with the project director and may God
have mercy on your souls.
+ Conventions Used In This Document
+
+ All TABLE NAMES are written in UPPER CASE. Column Names are
+ in lower case with Initial Capitals.
+
+ When the reader should take care, particularly when the
+ system might do something unexpected in a given
+ circumstance, this is noted in a caution. Cautions are set
+ off from the surrounding text like this:
+
+ Babase will reject your change if you try to do something
+ that is not allowed, like giving a male an onset of
+ turgesence date.
+
+ Caution
+
+ When the rejected change is one of a number of changes
+ bundled into a transaction none of the changes will make
+ it into the database.
+
+ When a mis-use of the system will lead to incorrect
+ results, particularly when such results are not obvious,
+ this document contains a warning. Warnings are set off from
+ the surrounding text like this:
+
+ Warning
+
+ Babase cannot detect when an Sname is mis-typed, so it is
+ possible to inadvertently assign a female's sexual cycle
+ to the wrong female.
+
+ To otherwise draw the readers attention to material some
+ text is marked important. Important text is set off from
+ the surrounding material like this:
+
+ Babase has a number of components, many of them, like the
+ SQL web interface, are third party tools, not written by
+ the Babase developers.
+
+ Important
+
+ When the third party tools are upgraded their "look" may
+ change but the features they provide should remain. As
+ Babase is composed of Free Software the Babase project
+ always has the option of customizing any of it's third
+ party tools and can contribute it's improvements back to
+ the program's developers for inclusion into future
+ releases.
+
+ Suggestions as to how to use Babase are noted in tips, as
+ are remarks on how data is presently entered in Babase or
+ recorded in the field. These are set off from the regular
+ text of the document like this:
+
+ Tip
+
+ Lick all the chocolate off your fingers before beginning
+ data entry.
+
+ Often, the tips are the result of best practice developed
+ from considered experience and so document how Babase is
+ used at the time of this writing. However, as best practice
+ continues to develop and field protocols change, the
+ Protocol For Data Management and the field protocol
+ documentation should always be consulted. Those documents
+ have precedence over the tips presented herein should there
+ be conflicting advice.
+
+ Supplemental and cross referential material is presented in
+ footnotes.
+
+ A Guide for the Reader
+
+ Anyone who is changing or adding programs to the system
+ should read this entire document. Section III The Master
+ Tables is particularly important for all those using the
+ system. Section V The Dataset Tables is of little interest
+ to those who only want to retrieve information from the
+ system. Section VI.B Useful Programs and Functions is of
+ interest to the more sophisticated user. People who will
+ not be programming need not read section VIII Standards,
+ although sections VIII.A General Program Standards and
+ VIII.B User Interface Standards may prove interesting.
+
System Designs
The BABASE system is designed to facilitate the retrieval,
@@ -624,23 +694,26 @@
This table records the basic biographical data on the
baboons. It contains one row for each baboon, including
- aborted fetuses and fetal deaths (collectively, fetal
- losses), on which any data have been collected. All
- individuals with an Sname, i.e., those which aren't fetal
- losses, should have a Name and should have rows on MEMBERS.
- Those rows that record data on fetal losses should maintain
- the following relations between their data values: the
- Sname and Name values should be NULL; the Statdate should
- be the same as the birth date (Birth); the Status should be
- 1 (definitely dead); and the Dcause should be 7 (unknown)
- or 5 (loss of mother). Jeanne needs to confirm that this is
- still the case since her changes to DCAUSES. Because the
- fetal losses have no Sname, there will not be any record of
- their group membership in MEMBERS. The Statdate value
- should not be less than the Birth value. Live animals
- should not have a recorded cause of death. Live animals
- that have no associated CENSUS rows (absences excepted)
- must have a Statdate equal to their Birth date.
+ aborted fetuses and fetal deathsCathrine sez: Shouldn't
+ this be "still births"? (collectively, fetal losses), on
+ which any data have been collected. Those rows that record
+ data on fetal losses must maintain the following relations
+ between their data values: the Sname and Name values must
+ be NULL; the Statdate must be the same as the birth date
+ (Birth); the Status must be 1 (definitely dead); and the
+ Dcause must be 7 (unknown) or 5 (loss of mother). Jeanne
+ needs to confirm that this is still the case since her
+ changes to DCAUSES. In all cases the Statdate value must
+ not be less than the Birth value. Live animals must not
+ have a recorded cause of death. Live animals that have no
+ associated CENSUS rows (absences excepted) must have a
+ Statdate equal to their Birth date.
+
+ All individuals with an Sname, i.e., those which aren't
+ fetal losses, must have a Name and will have rows on
+ MEMBERS. Because the fetal losses have no Sname they cannot
+ have corresponding CENSUS rows and so there will not be any
+ record of their group membership in MEMBERS.
Column Descriptions
@@ -648,23 +721,22 @@
The short name of the individual. This is an exactly three
character long name abbreviation which is used to identify
- the individual and so should be a unique data value. This
+ the individual and so must be a unique data value. This
value appears in many other places in the system and so
should not be changed without changing all the other places
in the database where the abbreviation appears; really,
once established, the only reason to change this column is
because the short name had already been used.^[5] The Sname
- is always composed of capital letters (and may not contain
- a space). This column should only be NULL if the row
- represents an aborted fetus.
+ is always composed of capital letters and may not contain a
+ space. This column should only be NULL if the row
+ represents a fetal loss.
Name
The name of the individual. This is a textual column used
- for descriptive purposes. This value should be unique when
- a comparison is done in a case insensitive fashion. This
- column should only be NULL if the row records an aborted
- fetus.
+ for descriptive purposes. This value must be unique when a
+ comparison is done in a case insensitive fashion. This
+ column should only be NULL if the row records a fetal loss.
Pid
@@ -747,15 +819,14 @@
alive, then the Statdate is the birth date. This column is
automatically updated when CENSUS is updated to ensure the
these relationship remain true. When the individual is not
- alive the Statdate is the date of death, disappearance,
- etc.
+ alive the Statdate is the date of death.
Caution
Living individuals, unlike dead ones, can have MEMBERS rows
created by the interpolation procedure that locate the
individual in a group on a date later than the individual's
- Statdate. For further information see: Interpolation At The
+ Statdate. For further information see: Interpolation at the
Statdate .
Statdate (almost, given the preceding caveat) provides a
@@ -1349,10 +1420,11 @@
(individuals with no Sname). There is a row in MEMBERS for
every individual for every day between Birth and Statdate,
inclusive, including periods during which the whereabouts
- of an individual are unknown or assumed unknown. (See: the
+ of an individual are either recorded as being unknown or
+ assumed unknown by the interpolation procedure. (See: the
unknown group.) Some living individuals have MEMBERS rows
after their Statdate, for more information see the section:
- Interpolation At The Statdate . MEMBERS is most useful when
+ Interpolation at the Statdate . MEMBERS is most useful when
one is interested in an individual's location on a
particular date. Simply check MEMBERS for the individual on
that date. To find all the individuals in a group on a
@@ -1421,33 +1493,34 @@
information. This information is derived from, and has the
same values as, the Status column of CENSUS, although
MEMBERS.Origin contains the I (interpolated) value not
- found in CENSUS. The codes are as follows: C (CENSUS)
- values represent census data points, I (interpolated)
- values are derived from the census data points, D
- (demography) values represent demography notes not present
- in the census sheets, M and N (manual) values represent
- census data points due to operator intervention in CENSUS .
- The S, E, F, B, G, T, L, and R codes are derived from
- analysis of historical data. See the CENSUS section for
- further information.
+ found in CENSUS, and does not contain the A (absent) value.
+ The codes are as follows: C (CENSUS) values represent
+ census data points, I (interpolated) values are derived
+ from the census data points, D (demography) values
+ represent demography notes not present in the census
+ sheets, M and N (manual) values represent census data
+ points due to operator intervention in CENSUS . The S, E,
+ F, B, G, T, L, and R codes are derived from analysis of
+ historical data. See the CENSUS section for further
+ information.
This column may not be NULL.
Interp
- The distance, in days, from the date in which an individual
- was previously observed to be in a group (censused --
- automatic placement in the unknown group does not count) to
- the date of the MEMBERS row. So the value is 0 on those
- days on which the individuals are censused, 1 on those
- (non-census) days immediately before or after the census
- days, etc. For those MEMBERS rows that the interpolation
- procedure has placed in the unknown group for lack of a
- better place to put them, the Interp column is the number
- of days "distant" from the interpolating CENSUS row, or the
- birth date, that determined the group membership. Note that
- the CENSUS row that determined that the MEMBERS.Grp should
- be unknown may record an absence.
+ The time interval, in days, from the date in which an
+ individual was previously observed to be in a group
+ (censused -- automatic placement in the unknown group does
+ not count) to the date of the MEMBERS row. So the value is
+ 0 on those days on which the individuals are censused, 1 on
+ those (non-census) days immediately before or after the
+ census days, etc. For those MEMBERS rows that the
+ interpolation procedure has placed in the unknown group for
+ lack of a better place to put them, the Interp column is
+ the number of days "distant" from the interpolating CENSUS
+ row, or the birth date, that determined the group
+ membership. Note that the CENSUS row that determined that
+ the MEMBERS.Grp should be unknown may record an absence.
Important
@@ -1473,13 +1546,13 @@
Tip
- The way to record that an individual is alone is to create
- a row in GROUPS (Groups) meaning alone, and then to assign
- individuals who are alone to this group. The "alone-ness"
- of an individual can then be tracked in the same fashion as
- group membership, although the Babase user does then need
- to be aware that the members of the "alone" group are not
- actually proximate to one another.
+ One way to have Babase record that an individual is alone
+ is to first create a row in GROUPS (Groups) meaning alone,
+ and then to assign individuals who are alone to this group.
+ The "alone-ness" of an individual can then be tracked in
+ the same fashion as group membership, although the Babase
+ user does then need to be aware that the members of the
+ "alone" group are not actually proximate to one another.
As noted in the MEMBERS documentation, Babase does not
allow an individual to be in more than one group on a given
@@ -1488,16 +1561,16 @@
The original field census data sheets can be recovered from
CENSUS, with one exception. Data is lost when an individual
is actually censused in two groups on the same day because
- of movement between groups and the timing of the censuses.
- In this situation a decision should be made as to which
- group CENSUS should record the individual's presence on
- that day.. A demography note should then be added to DEMOG,
- with text that notes the individual's presence in the
- second group. Although it is technically true that this
- does put into the database all of the information from the
- censuses in the field, as the information regarding the
- second census is in textual information it is not readily
- available to automated tools.
+ of movement between groups and the timing of the
+ censuses.^[9] In this situation a decision should be made
+ as to which group CENSUS should record the individual's
+ presence on that day. A demography note should then be
+ added to DEMOG, with text that notes the individual's
+ presence in the second group. Although it is technically
+ true that this does put into the database all of the
+ information from the censuses in the field, as the
+ information regarding the second census is in textual
+ information it is not readily available to automated tools.
Caution
@@ -1567,6 +1640,11 @@
(There may or may not be a corresponding demography
note on DEMOG as well.)
+ Tip
+
+ A C Status is marked on the census data sheet as an
+ "X".
+
A
(absent) The animal was not found in the group on a
@@ -1575,15 +1653,26 @@
group on the same day, s/he may be absent from
several groups on any given day.
+ Tip
+
+ An A Status is marked on the census data sheet as
+ an "0".
+
D
- (demography) The animal was noted in the field
- notebooks or elsewhere to be in a group but was not
- marked present in a field census on that day. There
- is an associated DEMOG row associated with the
- CENSUS row. The individual may or may not have been
- marked "absent" on the same group's field census
- for the day.^[9]
+ (demography) The animal was noted, in the field
+ notebooks or elsewhere, to be in a group but was
+ not marked present in a field census on that day.
+ There is an associated DEMOG row associated with
+ the CENSUS row. The individual may or may not have
+ been marked "absent" on the same group's field
+ census for the day.^[10]
+
+ Tip
+
+ A D Status is marked on the census data sheet as an
+ "0", when there exists a corresponding place on the
+ census data sheet.
M
@@ -1658,10 +1747,6 @@
sub-group as censused on 15/4/92, and the
time-adjacent locations were not 1.0.
- A C Status is marked on the census data sheet as an "X" .
- An A or D Status is marked on the census data sheet as a
- "0".
-
This column may not be NULL.
Cen
@@ -1677,29 +1762,33 @@
DEMOG (Demography Notes)
- This table holds group membership related text from the
- field demography notes, especially that which records group
- membership information not otherwise written on the regular
- field census sheets. DEMOG provides a means of notating
- CENSUS rows, and thus facilitates management of additional
- "free form" CENSUS rows, rows that do not directly
- correspond with the field census sheets.^[10] It contains
- one row for every individual for every date for every group
- where the individual was noted present in the field
- demography notes. The DEMOG row holds the textual
- information. There is always exactly one corresponding
- CENSUS row which holds the corresponding group membership
- information in the usual coded and structured form. (Note
- that only some CENSUS rows will have DEMOG rows; CENSUS
- rows that originate entirely in the regular censuses of
- groups will not, in general, have an associated DEMOG row).
- A single field note referring to more than one individual
- must appear in DEMOG as two (or more) separate rows, one
- row per individual. Multiple field notes pertaining to a
- single individual on a single date must be combined into
- one piece of text and entered in a single DEMOG row. (See
- Protocol notes for structure of the demography data as
- entered by the operator.)
+ This table holds the text which records group membership
+ information not written on the regular field census sheets,
+ especially that from the field demography notes. DEMOG
+ provides a means of notating CENSUS rows, and thus
+ facilitates management of additional "free form" CENSUS
+ rows, rows that do not directly correspond with the field
+ census sheets.^[11] Thus, in conjunction with these
+ corresponding CENSUS rows, the DEMOG rows capture group
+ membership information that otherwise would not appear in
+ the CENSUS table.
+
+ DEMOG contains one row for every individual for every date
+ for every group where the individual was noted present in
+ the free form textual field notes. The DEMOG row holds
+ textual information. There is always exactly one
+ corresponding CENSUS row which holds the corresponding
+ group membership information in the usual coded and
+ structured form. (Note that only some CENSUS rows will have
+ DEMOG rows; CENSUS rows that originate entirely in the
+ regular censuses of groups will not, in general, have an
+ associated DEMOG row). A single field note referring to
+ more than one individual must appear in DEMOG as two (or
+ more) separate rows, one row per individual. Multiple field
+ notes pertaining to a single individual on a single date
+ must be combined into one piece of text and entered in a
+ single DEMOG row. (See Protocol notes for structure of the
+ demography data as entered by the operator.)
Column Descriptions
@@ -1878,7 +1967,7 @@
interactions between animals. Each record in the table
records a participant. Each interaction is represented as
though it occurs between two ordered individuals designated
- "actor" and "actee" ^[11] interactions between multiple
+ "actor" and "actee" ^[12] interactions between multiple
individuals are broken down into interactions between pairs
according to rules described elsewhere. Therefore, this
table contains two rows for every record of an interaction,
@@ -2547,13 +2636,24 @@
MEMBERS. Thus, MEMBERS always has a row recording group
membership for every day of every individual's life.
+ This section is comprised of 3 sub-sections. The first
+ section introduces interpolation incrementally. Rules are
+ presented in an informal fashion and examples and
+ exceptions progressively developed. The second section is a
+ formal specification of interpolation. The third section
+ supplements the formal specification with expectations
+ regarding the use of interpolation and brief descriptions
+ of interpolation's implications. Most of the third section
+ is a restatement of material already presented in the first
+ section.
+
Interpolation's 3 Fundamentals
It is primarily by census records that Babase tracks group
membership. The CENSUS table is the source of all group
membership information. Babase places rows in the CENSUS
table to indicate presence in a group whenever demography
- information is stored other tables.^[12][13] Throughout
+ information is stored other tables.^[13][14] Throughout
this section it is to be understood that any sort of
demographic information which results in CENSUS data is
implied when the term census, or it's plural, is used.
@@ -2826,9 +2926,9 @@
An individual is placed in his Matgrp on his birth date
even when a regular census has an absence recorded for the
- individual on the date of birth.^[14]
+ individual on the date of birth.^[15]
- Interpolation At The Statdate
+ Interpolation at the Statdate
Another exception to the rules, or rather two exceptions,
occur at the Statdate. You might expect that interpolation
@@ -2837,7 +2937,7 @@
dead. When an individual is alive, interpolation will place
a row after the individual's Statdate, but only when there
is a subsequent absence from the same group as the group in
- which the individual was censused.^[15][16] While at first
+ which the individual was censused.^[16][17] While at first
this may seem odd, the reasoning behind this behavior is
clear -- the Statdate is not the last date on which there
is data for the individual. This is elaborated below.
@@ -2855,7 +2955,7 @@
period of data entry, as there will always be a large
number of living individuals found in their groups on the
last census entered. The solution is to not create the
- rows.^[17] When a living individual has no later absences
+ rows.^[18] When a living individual has no later absences
from the group where last located, no absences from the
group of his last locating census that post-date his last
locating census, this is taken to mean that there is
@@ -2895,9 +2995,9 @@
Notice that there are no MEMBERS rows created after day 7.
When interpolating a living individual, after the Statdate
there is no default placement of the individual into the
- unknown group.^[18]
+ unknown group.^[19]
- Figure 12. Alive and Absent in Last Census^[19]
+ Figure 12. Alive and Absent in Last Census^[20]
Living individual with Statdate of 5
CENSUS: C A C A A
@@ -3208,13 +3308,13 @@
this method is applied to the data first seen in Figure 16.
For clarity the intervals surrounding the censuses that
belong to one group are shown separately from those
- belonging to the other group.^[20] The lines labeled
+ belonging to the other group.^[21] The lines labeled
Presence show the intervals that are halfway from each
census to the nearest census that finds the individual in
any group. The lines labeled Absence show the intervals
that are halfway from each census to the nearest absence in
the same group. Censuses with no neighboring absence do not
- have this latter sort of interval shown.^[21]
+ have this latter sort of interval shown.^[22]
Figure 19. Presence and Absence Interpolated Separately
@@ -3246,7 +3346,7 @@
and "absence" intervals by choosing the shorter of the two
to as the period during which the individual is assumed to
be in the group where censused. The line labeled Used
- contains the shorter of each census's two intervals.^[22]
+ contains the shorter of each census's two intervals.^[23]
Figure 20. Combining Presence and Absence Intervals
@@ -3321,7 +3421,7 @@
| Interval endpoint
- By now it should be clear that interpolation^[23] is a
+ By now it should be clear that interpolation^[24] is a
function over CENSUS row sets. It is a function, for every
input you get exactly one output. It takes sets of CENSUS
rows as input. Because sets are unordered you can put
@@ -3350,7 +3450,7 @@
locating censuses into those which interpolate and those
which do not. Those CENSUS rows that record observational
data are interpolating censuses; those with Status values
- of C, D and, M.^[24] (All of the previous examples have
+ of C, D and, M.^[25] (All of the previous examples have
concerned CENSUS rows of this type.) The remaining
CENSUS.Status values indicate that the CENSUS row is the
result of analysis, all of the "old style", that is
@@ -3380,7 +3480,7 @@
could be there for any reason at all, and there's no point
in pretending it's not there either. What interpolation
does is give up. It interpolates up to the offending data
- point and then stops.^[25] After that it still creates rows
+ point and then stops.^[26] After that it still creates rows
in MEMBERS, but it does not attempt to make guesses about
where to place an individual or what the interpolated row
means.
@@ -3517,7 +3617,7 @@
non-interpolating census until the point is reached at
which counting back down to the next interpolating census
begins, at which point the count downward resumes as though
- never interrupted.^[27]
+ never interrupted.^[28]
The approach interpolation takes, in some sense, attempts
to minimize the disturbance created when already analyzed
@@ -3687,7 +3787,7 @@
unknown group. The resulting MEMBERS rows have an
Origin of I and an Interp value of the number of days
difference between the MEMBERS row's Date and the date
- of individual's nearest interpolating census.^[28]
+ of individual's nearest interpolating census.^[29]
VII. Birth stops interpolation
@@ -3706,7 +3806,7 @@
rows after the individual's last locating census only
when there are subsequent absences; absences, that is,
from the group in which the individual was
- censused.^[29] In this case, unlike above, no data does
+ censused.^[30] In this case, unlike above, no data does
not imply unknown group membership; such rows are
created only so long as the individual is interpolated
into the group of his last locating census. When a
@@ -3734,7 +3834,7 @@
The MEMBERS Interp column is fixed at NULL on the
interval from the non-interpolating census row through
the "midpoint" end of The Halfway to Census Interval,
- endpoints included.^[30] Here we are speaking of The
+ endpoints included.^[31] Here we are speaking of The
Halfway to Census Interval as computed, not a Halfway to
Census Interval shortened in the preceding paragraph.
@@ -3763,7 +3863,7 @@
o Living individuals, but not dead ones, can have MEMBERS
rows created by the interpolation procedure that locate
the individual in a group on a date later than the
- individual's Statdate.^[31]
+ individual's Statdate.^[32]
o So long as an individual is alive the last CENSUS to
locate the individual ought be followed by a record of
@@ -4261,7 +4361,7 @@
All things Docbook can be found at The Docbook Project. The
basic Docbook reference is Docbook: The Definitive
- Guide.^[32] While this book describes how to write Docbook,
+ Guide.^[33] While this book describes how to write Docbook,
it does not describe how to generate output or how to vary
the "look", the term-of-art is style, of the generated
output. A more gentle introduction can be found in Writing
@@ -4308,6 +4408,11 @@
^[4] Presently group 9.0. This hardcoded at present.
+ Individuals are generally put in the unknown group when
+ interapolation does not know their group membership, but it
+ is also possible for an individual to be explicitly placed
+ in the unknown group.
+
^[5] This is unlikely as the database will not allow entry
of a duplicate Sname.
@@ -4323,14 +4428,17 @@
gaps in the recorded data during the time period in which
the peak turgesence probably occured.
- ^[9] D usually occurs when a male is seen alone or in a
+ ^[9] This is termed a visit in the Protocol for Data
+ Management, which should be consulted for further details.
+
+ ^[10] D usually occurs when a male is seen alone or in a
non-census group.
- ^[10] DEMOG nearly makes the M CENSUS Status code obsolete,
+ ^[11] DEMOG nearly makes the M CENSUS Status code obsolete,
were it not so hard to search on textual data. Indeed, it
was created in response to difficulties with the M code.
- ^[11] One would think that, in order to maintain perfect
+ ^[12] One would think that, in order to maintain perfect
database consistency, the actor and actee participants in
an interaction should be in the same Supergroup, according
to the MEMBERS table. The database consistency checker
@@ -4362,41 +4470,41 @@
actual location of the individual. (See the MEMBERS
documentation.)
- ^[12] At this time only DEMOG, the demography notes table,
+ ^[13] At this time only DEMOG, the demography notes table,
contributes to CENSUS any information regarding group
membership.
- ^[13] Sometimes, when demography information is added into
+ ^[14] Sometimes, when demography information is added into
other tables, CENSUS rows are altered rather than removed.
Likewise, CENSUS rows are removed (or altered as necessary)
when demography information is removed from other tables.
- ^[14] This is the one exception, if you wish to consider it
+ ^[15] This is the one exception, if you wish to consider it
so, to the rule that an individual cannot be censused both
present and absent in the same group on the same day.
- ^[15] The "same group" condition is one that must be met
+ ^[16] The "same group" condition is one that must be met
whenever interpolation examines intervals between presence
and absence.
- ^[16] As the individual is alive, every census that
+ ^[17] As the individual is alive, every census that
post-dates the individual's Statdate must record an
absence, else the Statdate would be adjusted to reflect the
date of last census.
- ^[17] This is a heuristic. While it should work well enough
+ ^[18] This is a heuristic. While it should work well enough
most of the time the Babase user must be aware of the
pitfalls in this approach. These are explained below.
- ^[18] Without this restriction interpolation would have to
+ ^[19] Without this restriction interpolation would have to
insert rows forever, placing the individual in the unknown
group off into the indefinite future.
- ^[19] Notice that interpolation does not bother analyzing
+ ^[20] Notice that interpolation does not bother analyzing
absences, such as the last-most, that are not neighbor to
censuses.
- ^[20] As locating censuses are interpolated individually
+ ^[21] As locating censuses are interpolated individually
the figure could diagram the intervals associated with each
census separately, as in Figure 18, work out group
membership from that, and then combine the results; the
@@ -4407,25 +4515,25 @@
accurately depicted, and that the order in which locating
censuses are interpolated does indeed make no difference.
- ^[21] Figure 18: " A Closer Look at Intervals" makes clear
+ ^[22] Figure 18: " A Closer Look at Intervals" makes clear
that it is not necessary to show these intervals. By
definition, the omitted intervals will always be longer
than the "halfway to census" interval of the census being
interpolated. As the shorter interval is the one used the
longer may be ignored.
- ^[22] When there are two intervals. When there's no
+ ^[23] When there are two intervals. When there's no
"absence" interval the "Used:" line shows the "presence"
interval.
- ^[23] The proper term is "The Glorious Interpolation
+ ^[24] The proper term is "The Glorious Interpolation
Procedure", but we don't tell this to just anybody.
- ^[24] See MEMBERS.Origin.
+ ^[25] See MEMBERS.Origin.
- ^[25] It might be better if interpolation did not
+ ^[26] It might be better if interpolation did not
interpolate at all on those intervals between interpolating
- censuses that contain a non-interpolating census^[25] -- if
+ censuses that contain a non-interpolating census^[26] -- if
it put the individual in the unknown group, with an Interp
of 0 and an Origin of NULL whenever there was no locating
census. However, this could easily cause problems because
@@ -4435,24 +4543,24 @@
situations and changes should not be made to interpolation
which break the database.
- ^[2525] I have not thought this through. At first glance it
+ ^[2626] I have not thought this through. At first glance it
seems the code would be simpler, but perhaps not. And the
effect on data analysis is unclear. It is probably best to
adopt one of the solutions presented in the note below.
- ^[27] Although in this example we "count up" traversing the
+ ^[28] Although in this example we "count up" traversing the
timeline from left to right, had the N census had been
closer to the right side of the diagram than the left we
would be "counting up" the interval by traversing the
timeline in the opposite direction, from right to left.
- ^[28] The same method is used to compute Interp values when
+ ^[29] The same method is used to compute Interp values when
interpolation uses The 3 Interpolation Intervals, above.
- ^[29] This "same group" criteria corresponds with the
+ ^[30] This "same group" criteria corresponds with the
criteria found in The Halfway to Absence Interval.
- ^[30] Interp is fixed at 0 over the portion of The Halfway
+ ^[31] Interp is fixed at 0 over the portion of The Halfway
to Census Interval that was truncated in the preceding
paragraph. Effectively, as MEMBERS Interp counts up with
increasing distance from the interpolating census, the
@@ -4462,9 +4570,9 @@
begins, at which point the count downward resumes as though
never interrupted.
- ^[31] This is examined in detail in Interpolation At The
+ ^[32] This is examined in detail in Interpolation at the
Statdate .
- ^[32] Be sure to read the edition that describes the
+ ^[33] Be sure to read the edition that describes the
version of Docbook you're using. This text was written for
Docbook 4.3.