sokwedb - Recent changes [en]

Conversion Data Issues

StevanEarl — Wed, 03 Jun 2026 00:29:53 GMT

minor edit to Problem #84 language

Show changes

Conversion Data Issues

IanGilby — Tue, 19 May 2026 19:27:53 GMT

* (#49) There are follow_arrivals where females that are too old have a cycle code of U

Conversion Data Issues

StevanEarl — Tue, 19 May 2026 18:47:01 GMT

Problem #78 there are AGGRESSION_EVENT rows where ae_full_description is NULL or an empty string.

Show changes

The Old Database

KarlPinc — Thu, 14 May 2026 16:07:03 GMT

Notes On Data Clean Up and Other Data Transformation Steps: FOOD_EVENTS.FoodPartWriiten and FOOD_EVENTS.FoodNameWritten

Conversion Data Issues

KarlPinc — Tue, 12 May 2026 21:03:16 GMT

(#68) There are AGGRESSION_EVENT rows that have a space as a ae_multiple_recipient_flag value

The Old Database

KarlPinc — Tue, 12 May 2026 17:10:16 GMT

The handling of the AGGRESSION_EVENT.ae_bad_observervation_flag: What about BadObs?

@@ Line 298: / Line 298: @@
 === Solution ===
+Talk to Karl about kk_P0 and kk_P1
 == * (#14) COMM_MEMBS rows place individuals in a community after their BIOGRAPHY.EndDate ==
@@ Line 1,104: / Line 1,105: @@
 === Solution ===
 Something is wrong with community entry date or biography
+SN1 fixed in MS Access ICG 5/19/2026
+Confirm CT and SG were with CA on 10/23/1980 from brec swahili
 == * (#45) The follow_arrival.fa_update column is not preserved ==
@@ Line 1,217: / Line 1,222: @@
 IAN TO FIX IN ACCESS - CHECK DATES OF FOLLOWS AND ACCURACY OF IDS
-== * (#49) There are follow_arrivals where females that are too old have a cycle code of <code>U</code>  ==
+== (#49) There are follow_arrivals where females that are too old have a cycle code of <code>U</code>  ==
 === Problem ===
@@ Line 1,258: / Line 1,263: @@
 /7/2026: ICG checked through 2003. When there was a "?" for swelling, I entered '0'. If there was actually a 'U' on the tiki itself, I left "U" in the FA table. Note that a lot of these females are MGF, so the U might be legit.
+/19/2026: MGFs have a dummy birthdate which is why the age is being flagged. The rest are what the observer recorded, so let them in.
 == (#50) There are follow_arrivals where females have a cycle code of <code>n/a</code>  ==

@@ Line 92: / Line 92: @@
 Trailing spaces are removed from the follow_arrival.fa_fol_b_focal_animid column.
-==== The handling of the AGGRESSION_EVENT.ae_bad_observervation_flag ====
-This flag is used to populate both EVENTS.Certainty and the AGGRESSIONS.BadObs column.
-When ae_bad_observation_flag is false-like, EVENTS.Certainty is <code>0</code>.
-(This raises the question of why the ARRIVALS.BadObs column exists, because we're putting the same information into two different places.)
-See also conversion problem #65.
 === conv_state ===
@@ Line 147: / Line 138: @@
 Otherwise, the original data value is used.
+=== FOOD_EVENTS.FoodPartWritten and FOOD_EVENTS.FoodNameWritten ===
+Only the first food event, the one with a <code>FOOD_EVENTS.Seq</code> value of <code>1</code>, has the <code>fb_local_food_part_written</code> and <code>fb_local_food_name_written</code> values from the MS Access data.  These values are expected to contain the "written" record of both foods, if more than one food was eaten -- if there is a related <code>FOOD_EVENTS</code> row with a <code>Seq</code> value of <code>2</code> the "written" columns contain the empty string.
 == Comparing Old Data to Current Data ==

@@ Line 1,705: / Line 1,705: @@
 <pre>SELECT COALESCE(ae.ae_bad_observation_flag, 'NULL'), count(*)
-  FROM clean.aggression_event AS ae
+  FROM easy.aggression_event AS ae
   GROUP BY ae.ae_bad_observation_flag;</pre>
 === Solution ===
 Treat spaces (along with <code>NULL</code>) as <code>FALSE</code>, and <code>YES</code> (along with <code>X</code>() as <code>TRUE</code>.
+== * (#66) There are AGGRESSION_EVENT rows that have a space as a ae_decided_flag value ==
+=== Problem ===
+There are 2,041 rows where the ae_decided_flag is a space.
+=== Bad data ===
+<pre>SELECT COALESCE(ae.ae_decided_flag, 'NULL'), count(*)
+  FROM easy.aggression_event AS ae
+  GROUP BY ae.ae_decided_flag;</pre>
+=== Solution ===
+Treat spaces (along with <code>NULL</code>) as <code>FALSE</code>.
+== * (#67) There are AGGRESSION_EVENT rows that have a space or an <code>x</code> as a ae_multiple_aggressor_flag value ==
+=== Problem ===
+There are 2,397 rows where the ae_multiple_aggressor_flag is a space and 2 rows where the value is an <code>x</code>.
+=== Bad data ===
+<pre>SELECT COALESCE(ae.ae_multiple_aggressor_flag, 'NULL'), count(*)
+  FROM easy.aggression_event AS ae
+  GROUP BY ae.ae_multiple_aggressor_flag;</pre>
+=== Solution ===
+Treat spaces (along with <code>NULL</code>) as <code>FALSE</code>, and <code>x</code> (along with <code>X</code>) as <code>TRUE</code>.
+== * (#68) There are AGGRESSION_EVENT rows that have a space as a ae_multiple_recipient_flag value ==
+=== Problem ===
+There are 2,528 rows where the ae_multiple_recipient_flag is a space.
+=== Bad data ===
+<pre>SELECT COALESCE(ae.ae_multiple_recipient_flag, 'NULL'), count(*)
+  FROM easy.aggression_event AS ae
+  GROUP BY ae.ae_multiple_recipient_flag;</pre>
+=== Solution ===
+Treat spaces (along with <code>NULL</code>) as <code>FALSE</code>.

@@ Line 97: / Line 97: @@
 This flag is used to populate both EVENTS.Certainty and the AGGRESSIONS.BadObs column.
 When ae_bad_observation_flag is false-like, EVENTS.Certainty is <code>0</code>.
+(This raises the question of why the ARRIVALS.BadObs column exists, because we're putting the same information into two different places.)
+See also conversion problem #65.
 === conv_state ===