sokwedb - Recent changes [en]

Conversion Progress

KarlPinc — Mon, 20 Jul 2026 23:46:37 GMT

Housekeeping: All tables are implemented

Conversion Data Issues

StevanEarl — Sun, 19 Jul 2026 23:36:06 GMT

Update Problem #83 row count

Show changes

Conversion Data Issues

KarlPinc — Sat, 18 Jul 2026 15:34:15 GMT

* (#45) The follow_arrival.fa_update column is not preserved: Resolve

Conversion Progress

KarlPinc — Thu, 16 Jul 2026 03:06:06 GMT

Data Tables: ARRIVALS_A is supposed to generate warnings instead of having hard errors

Conversion Data Issues

KarlPinc — Wed, 15 Jul 2026 17:21:34 GMT

Bad data: Data is fixed in clean. Query easy to find the problem rows.

@@ Line 74: / Line 74: @@
 ! Table !! State !! Remarks
 |-
-| ELO_RANKS_DAILY_KK_F || Not started, no table yet ||
+| ELO_RANKS_DAILY_KK_F || Coded ||
 |-
-| ELO_RANKS_DAILY_KK_M || Not started, no table yet ||
+| ELO_RANKS_DAILY_KK_M || Coded ||
 |-
-| ELO_RANKS_DAILY_MT_F || Not started, no table yet ||
+| ELO_RANKS_DAILY_MT_F || Coded ||
 |-
-| ELO_RANKS_DAILY_MT_M || Not started, no table yet ||
+| ELO_RANKS_DAILY_MT_M || Coded ||
 |-
-| FERTILITY || Not started, no table yet ||
+| FERTILITY || Coded ||
 |-
 | REPRO_STATES || Coded ||
@@ Line 97: / Line 97: @@
 ! Table !! State !! Remarks
 |-
-| CHIMPS_ON_TIKIS_LOOKUP || Not started, no table yet ||
+| CHIMPS_ON_TIKIS_LOOKUP || Coded ||
 |-
-| COMMUNITY_MEMBERSHIP_UPDATE_LOG || Not started, no table yet ||
+| COMMUNITY_MEMBERSHIP_UPDATE_LOG || Coded ||
 |-
-| FOOD_VARIATIONS || Not started, no table yet ||
+| FOOD_VARIATIONS || Coded ||
 |-
-| PANTGRUNT_EVENT_LOG || Not started, no table yet ||
+| PANTGRUNT_EVENT_LOG || Coded ||
 |-
-| SIV_STATUS_BOUT || Not started, no table yet ||
+| SIV_STATUS_BOUT || Coded ||
 |-
-| SUBADULT_ARRIVALS_LOG || Not started, no table yet ||
+| SUBADULT_ARRIVALS_LOG || Coded ||
 |-
-| TLK_BRECORD_NOTES_CODES || Not started, no table yet ||
+| TLK_BRECORD_NOTES_CODES || Coded ||
 |}

@@ Line 1,138: / Line 1,138: @@
 RESOLVED
-== * (#45) The follow_arrival.fa_update column is not preserved ==
+== (#45) The follow_arrival.fa_update column is not preserved ==
 === Problem ===
@@ Line 1,153: / Line 1,153: @@
 ASK KARL WHY THIS COLUMN CAN'T GO IN
+There is now a ARRIVALS.Updated column.  This provides a place to put the existing
+data.  Going forward, a PG extension (see below) can be installed for more functionality.
 Wouldn't you rather have a [https://en.wikipedia.org/wiki/Temporal_database temporal database]?  (Simple description in the top paragraph [https://wiki.postgresql.org/wiki/Temporal_Extensions here].)  This would allow you to "time travel" and look at the database content at any point in time.  And, it puts a "last changed" timestamp on every row, of every table you say to track temporally, automatically.

@@ Line 17: / Line 17: @@
 | AGGRESSION_EVENT_LOG || Coded ||
 |-
-| AGGRESSIONS || Coded -- changes pending ||
+| AGGRESSIONS || Coded ||
 |-
-| ARRIVALS || Coded -- changes pending ||
+| ARRIVALS || Coded ||
 |-
-| ARRIVALS_A || Coded -- changes pending ||
+| ARRIVALS_A || Coded ||
 |-
 | BIOGRAPHY_DATA || Done ||
@@ Line 27: / Line 27: @@
 | BIOGRAPHY_LOG || Done ||
 |-
-| BRECORD_NOTES || Coded -- changes pending ||
+| BRECORD_NOTES || Coded ||
 |-
-| COLOBUS (COLOBUS hunts) || Coded -- changes pending ||
+| COLOBUS (COLOBUS encounters) || Coded ||
 |-
 | COMM_MEMBS || Coded ||
@@ Line 35: / Line 35: @@
 | COMM_MEMB_LOG || Done ||
 |-
-| EVENTS || In progress, per WATCHES.Type ||
+| EVENTS || Coded ||
 |-
 | FOLLOW_OBSERVERS || Done ||
@@ Line 41: / Line 41: @@
 | FOLLOW_STUDIES || Done ||
 |-
-| FOOD_EVENTS || Coded -- changes pending ||
+| FOOD_EVENTS || Coded ||
 |-
-| GROOM_SCANS_B || Coded -- changes pending ||
+| GROOM_SCANS_B || Coded ||
 |-
-| GROOMINGS || Coded -- changes pending ||
+| GROOMINGS || Coded ||
 |-
 | HUMANS || Coded No conversion needed -- not in MS Access ||
 |-
-| LOCATIONS_PAPER (spatial LOCATIONS in map numbers) || Coded -- changes pending ||
+| LOCATIONS_PAPER (spatial LOCATIONS in map numbers) || Coded ||
 |-
-| LOCATIONS_UTM (spatial LOCATIONS in UTM coordinates) || Coded -- changes pending ||
+| LOCATIONS_UTM (spatial LOCATIONS in UTM coordinates) || Coded ||
 |-
-| MATINGS || Coded -- changes pending ||
+| MATINGS || Coded ||
 |-
-| PANTGRUNTS || Coded -- changes pending ||
+| PANTGRUNTS || Coded ||
 |-
-| ROLES || In progress, per WATCHES.Type ||
+| ROLES || Coded ||
 |-
 | NON_BREC_SIGHTING_SOURCES || Coded ||
@@ Line 65: / Line 65: @@
 | SWELLING_SOURCES || Coded ||
 |-
+| WATCHES || Coded ||
-| WATCHES || Follows and others are done, other WATCHES.Type values are in progress ||
 |}
@@ Line 84: / Line 84: @@
 | FERTILITY || Not started, no table yet ||
 |-
-| REPRO_STATES || Not started ||
+| REPRO_STATES || Coded ||
 |-
-| SWELLING_STATES || No conversion needed, no code written to (re)generate table content ||
+| SWELLING_STATES || Coded. No conversion needed, no code written to (re)generate table content ||
 |-
+| SIGHTINGS || Coded, and done because no conversion needed.  Needs function written to populate it. ||
-| SIGHTINGS || Not started ||
 |}
 == Housekeeping ==

@@ Line 1,887: / Line 1,887: @@
 SHOULD BE SOLVED BY WATCHES TABLE
+This means, aggressions can have a row on WATCHES, and go into the database, without there being a follow.
 I will mark resolved when I get the changes to aggression events done.  (Karl)
@@ Line 3,533: / Line 3,534: @@
 ==== Karl's comment ====
-Stevan, this is supposed to be fixed in the transition from the <code>raw</code> schema to the <code>tidy</schema>.  At least this is where the date and time intervals are normalized.
+Stevan, this is supposed to be fixed in the transition from the <code>raw</code> schema to the <code>tidy</code> schema.  At least this is where the date and time intervals are normalized.
 Maybe it got missed, or just needed bringing up as an issue.  No real point in fixing it in MS Access.  Doing so feels like losing information, and possibly being inconsistent in the way time intervals are normalized.
 == * (#97) There are GROOMINGS rows that have direction values that do not match to mappable values. ==
@@ Line 3,711: / Line 3,711: @@
 ORDER BY gb.grm_fol_date, gb.grm_fol_b_focal_animid, gb.grm_b_partner_animid;
 </pre>
+== * (#101) There are AGGRESSION_EVENT rows that have NULL focals, a NULL ae_fol_b_focal_id value ==
+=== Problem ===
+There are  144 aggression_event rows that have NULL for the focal.
+=== Bad data ===
+<pre>
+SELECT *
+  FROM easy.aggression_event
+  WHERE ae_fol_b_focal_id IS NULL;
+</pre>
+=== Solution ===
+Change these values to the unknown individual, <code>UNK</code>.
+This means that these rows are converted to WATCHES rows with a Type of <code>B</code>, and <code>UNK</code> as the focal.
+The data needs to be reviewed to see if this is appropriate.  See also problem #102.
+== * (#102) There are AGGRESSION_EVENT rows that have NULL times, a NULL ae_time value ==
+=== Problem ===
+There are  107 aggression_event rows that have NULL for the time.
+Note that all of these rows also have NULL for the focal, problem #101.
+=== Bad data ===
+<pre>
+SELECT *
+  FROM easy.aggression_event
+  WHERE ae_time IS NULL;
+</pre>
+=== Solution ===
+Change these values to the unknown time, midnight, <code>00:00</code>.
+These need to be reviewed to ensure the change is appropriate.
+Meeting discussions indicate the many, ideally all, of these rows are the result of perusal of a book's content, where aggressions were mentioned but these aggressions did not otherwise appear in the data.