Related changes

Enter a page name to see changes on pages linked to or from that page. (To see members of a category, enter Category:Name of category). Changes to pages on your Watchlist are in bold.

Recent changes options Show last 50 | 100 | 250 | 500 changes in last 1 | 3 | 7 | 14 | 30 days
Hide registered users | Hide anonymous users | Hide my edits | Show bots | Hide minor edits
Show new changes starting from 19:23, 5 July 2026

List of abbreviations:

N: This edit created a new page (also see list of new pages)
m: This is a minor edit
b: This edit was performed by a bot
(±123): The page size changed by this number of bytes

5 July 2026

18:43

Conversion Progress‎ diffhist -30‎ KarlPinc talk contribs →‎Data Tables: Mating events now allow same-sex matings

4 July 2026

			21:17		Conversion Progress‎‎ 2 changes history +14‎ [KarlPinc‎ (2×)]
					21:17 (cur \| prev) -19‎ KarlPinc talk contribs →‎Data Tables: GROOMINGS had it's changes pushed
					19:10 (cur \| prev) +33‎ KarlPinc talk contribs →‎Data Tables: Locations tables name changes done

3 July 2026

			22:49		Conversion Progress‎‎ 2 changes history -8‎ [KarlPinc‎ (2×)]
					22:49 (cur \| prev) +11‎ KarlPinc talk contribs →‎Data Tables: Clarify(ish)
					22:48 (cur \| prev) -19‎ KarlPinc talk contribs →‎Data Tables: WATCHES.Focal changed to WATCHES.AnimID

			22:33		Conversion Data Issues‎‎ 45 changes history +7,995‎ [IanGilby‎ (16×); KarlPinc‎ (29×)]
					22:33 (cur \| prev) +431‎ KarlPinc talk contribs →‎SOLUTION: Uh, maybe this should not be fixed in MS Access.
					22:29 (cur \| prev) +55‎ KarlPinc talk contribs →‎SOLUTION: Same as problem #81
					22:26 (cur \| prev) +1‎ KarlPinc talk contribs →‎= SOLUTION: Fix heading
					22:24 (cur \| prev) +161‎ KarlPinc talk contribs →‎SOLUTION: Normalize in the clean schema and see what's left
					22:19 (cur \| prev) +123‎ KarlPinc talk contribs →‎SOLUTION: Fair nuff
					22:17 (cur \| prev) +180‎ KarlPinc talk contribs →‎SOLUTION: Ok, if that's what you want
					22:12 (cur \| prev) +269‎ KarlPinc talk contribs →‎SOLUTION: Hack around to solve
					22:08 (cur \| prev) +58‎ KarlPinc talk contribs →‎SOLUTION: Fix in the clean schema
					22:07 (cur \| prev) +276‎ KarlPinc talk contribs →‎SOLUTION: Allowing would be un-good.
					22:03 (cur \| prev) +257‎ KarlPinc talk contribs →‎SOLUTION: Ok fix in clean.
					21:56 (cur \| prev) +341‎ KarlPinc talk contribs →‎Karl's comment: Poop emoji
					21:52 (cur \| prev) +421‎ KarlPinc talk contribs →‎Karl's comment: Changing back is not-so-easy.
					21:45 (cur \| prev) +217‎ KarlPinc talk contribs →‎SOLUTION: Ok. This affects all time values, everywhere.
					21:41 (cur \| prev) +91‎ KarlPinc talk contribs →‎SOLUTION
					21:40 (cur \| prev) +92‎ KarlPinc talk contribs →‎SOLUTION: Fix in clean
					21:38 (cur \| prev) +138‎ KarlPinc talk contribs →‎Karl comment: Or, don't convert the problematic data
					21:37 (cur \| prev) +200‎ KarlPinc talk contribs →‎SOLUTION: Allowing for now does not work well.
					21:33 (cur \| prev) +105‎ KarlPinc talk contribs →‎SOLUTION: Remove NULL values in clean
					21:26 (cur \| prev) +597‎ KarlPinc talk contribs →‎SOLUTION: Uh, that means a lot of new BIOGRAPHY_DATA rows
					21:18 (cur \| prev) +324‎ KarlPinc talk contribs →‎SOLUTION: Yes, make new people.
					21:05 (cur \| prev) +365‎ KarlPinc talk contribs →‎SOLUTION: Use UNK?
					20:59 (cur \| prev) +59‎ KarlPinc talk contribs →‎Solution: Fix in clean schema
					20:56 (cur \| prev) +80‎ KarlPinc talk contribs →‎SOLUTION: Waiting for implementation
					20:50 (cur \| prev) +47‎ KarlPinc talk contribs →‎Solution: Fix in the clean schema
					20:49 (cur \| prev) +110‎ KarlPinc talk contribs →‎Solution: Fix in the clean schema
					20:47 (cur \| prev) +162‎ KarlPinc talk contribs →‎Solution: Do you really want to alter the original data?
					20:43 (cur \| prev) +102‎ KarlPinc talk contribs →‎Solution: Ok. A warning.
					20:25 (cur \| prev) +890‎ KarlPinc talk contribs →‎* (#45) The follow_arrival.fa_update column is not preserved
					19:55 (cur \| prev) +949‎ KarlPinc talk contribs →‎Solution: Allowing these rows is hard
					18:49 (cur \| prev) +55‎ IanGilby talk contribs →‎* (#95) There is at least one food_bout rows where the start or stop time has a seconds value.
					18:46 (cur \| prev) +15‎ IanGilby talk contribs →‎* (#94) There are food_bout rows where the start or end of the observation is outside of allowable bounds.
					18:46 (cur \| prev) +28‎ IanGilby talk contribs →‎* (#94) There are food_bout rows where the start or end of the observation is outside of allowable bounds.
					18:45 (cur \| prev) +53‎ IanGilby talk contribs →‎* (#93) Need to address how we treat behaviours for the second value of food parts AND how they are derived.
					18:44 (cur \| prev) +104‎ IanGilby talk contribs →‎* (#92) There are food_bout rows that do not have a corresponding follow.
					18:43 (cur \| prev) -1‎ IanGilby talk contribs →‎* (#92) There are food_bout rows that do not have a corresponding follow.
					18:42 (cur \| prev) +38‎ IanGilby talk contribs →‎* (#91) There are food_bout rows that have fb_begin_feed_time > fb_end_feed_time.
					18:41 (cur \| prev) +75‎ IanGilby talk contribs →‎* (#90) There are food_bout rows for which the fb_fpl_local_food_part or fb_fpl_local_food_part2 does not have a matching value in codes.food_parts.
					18:40 (cur \| prev) +36‎ IanGilby talk contribs →‎* (#89) There is a food_bout row that has both a compound fb_fpl_local_food_part value and where fb_fpl_local_food_part2 is not null.
					18:38 (cur \| prev) +112‎ IanGilby talk contribs →‎* (#88) There are food_bout rows for which there is not a corresponding food name.
					18:37 (cur \| prev) +54‎ IanGilby talk contribs →‎* (#87) There are numerous duplicate fl_sci_food_name_gen values in food_lookup.
					18:34 (cur \| prev) +68‎ IanGilby talk contribs →‎* (#86) There are numerous instances in the food_part_lookup that that conflate name, initial, and/or the english translation.
					18:31 (cur \| prev) +72‎ IanGilby talk contribs →‎* (#85) There are numerous instances of local food names that translate to multiple scientific food names.
					18:29 (cur \| prev) +31‎ IanGilby talk contribs →‎* (#84) Some follows have a community with trailing spaces
					18:28 (cur \| prev) +74‎ IanGilby talk contribs →‎* (#83) There are AGGRESSION_EVENT rows where the Actor and Actee have the same animal ID.
					18:27 (cur \| prev) +80‎ IanGilby talk contribs →‎* (#82) There are AGGRESSION_EVENT rows where severity (ae_fight_category) is not an allowable value.

Namespace:	Invert selection Associated namespace
Tag filter:
Page name:	Show changes to pages linked to the given page instead

			22:33		Conversion Data Issues‎‎ 45 changes history +7,995‎ [IanGilby‎ (16×); KarlPinc‎ (29×)]
					22:33 (cur \| prev) +431‎ KarlPinc talk contribs →‎SOLUTION: Uh, maybe this should not be fixed in MS Access.
					22:29 (cur \| prev) +55‎ KarlPinc talk contribs →‎SOLUTION: Same as problem #81
					22:26 (cur \| prev) +1‎ KarlPinc talk contribs →‎= SOLUTION: Fix heading
					22:24 (cur \| prev) +161‎ KarlPinc talk contribs →‎SOLUTION: Normalize in the clean schema and see what's left
					22:19 (cur \| prev) +123‎ KarlPinc talk contribs →‎SOLUTION: Fair nuff
					22:17 (cur \| prev) +180‎ KarlPinc talk contribs →‎SOLUTION: Ok, if that's what you want
					22:12 (cur \| prev) +269‎ KarlPinc talk contribs →‎SOLUTION: Hack around to solve
					22:08 (cur \| prev) +58‎ KarlPinc talk contribs →‎SOLUTION: Fix in the clean schema
					22:07 (cur \| prev) +276‎ KarlPinc talk contribs →‎SOLUTION: Allowing would be un-good.
					22:03 (cur \| prev) +257‎ KarlPinc talk contribs →‎SOLUTION: Ok fix in clean.
					21:56 (cur \| prev) +341‎ KarlPinc talk contribs →‎Karl's comment: Poop emoji
					21:52 (cur \| prev) +421‎ KarlPinc talk contribs →‎Karl's comment: Changing back is not-so-easy.
					21:45 (cur \| prev) +217‎ KarlPinc talk contribs →‎SOLUTION: Ok. This affects all time values, everywhere.
					21:41 (cur \| prev) +91‎ KarlPinc talk contribs →‎SOLUTION
					21:40 (cur \| prev) +92‎ KarlPinc talk contribs →‎SOLUTION: Fix in clean
					21:38 (cur \| prev) +138‎ KarlPinc talk contribs →‎Karl comment: Or, don't convert the problematic data
					21:37 (cur \| prev) +200‎ KarlPinc talk contribs →‎SOLUTION: Allowing for now does not work well.
					21:33 (cur \| prev) +105‎ KarlPinc talk contribs →‎SOLUTION: Remove NULL values in clean
					21:26 (cur \| prev) +597‎ KarlPinc talk contribs →‎SOLUTION: Uh, that means a lot of new BIOGRAPHY_DATA rows
					21:18 (cur \| prev) +324‎ KarlPinc talk contribs →‎SOLUTION: Yes, make new people.
					21:05 (cur \| prev) +365‎ KarlPinc talk contribs →‎SOLUTION: Use UNK?
					20:59 (cur \| prev) +59‎ KarlPinc talk contribs →‎Solution: Fix in clean schema
					20:56 (cur \| prev) +80‎ KarlPinc talk contribs →‎SOLUTION: Waiting for implementation
					20:50 (cur \| prev) +47‎ KarlPinc talk contribs →‎Solution: Fix in the clean schema
					20:49 (cur \| prev) +110‎ KarlPinc talk contribs →‎Solution: Fix in the clean schema
					20:47 (cur \| prev) +162‎ KarlPinc talk contribs →‎Solution: Do you really want to alter the original data?
					20:43 (cur \| prev) +102‎ KarlPinc talk contribs →‎Solution: Ok. A warning.
					20:25 (cur \| prev) +890‎ KarlPinc talk contribs →‎* (#45) The follow_arrival.fa_update column is not preserved
					19:55 (cur \| prev) +949‎ KarlPinc talk contribs →‎Solution: Allowing these rows is hard
					18:49 (cur \| prev) +55‎ IanGilby talk contribs →‎* (#95) There is at least one food_bout rows where the start or stop time has a seconds value.
					18:46 (cur \| prev) +15‎ IanGilby talk contribs →‎* (#94) There are food_bout rows where the start or end of the observation is outside of allowable bounds.
					18:46 (cur \| prev) +28‎ IanGilby talk contribs →‎* (#94) There are food_bout rows where the start or end of the observation is outside of allowable bounds.
					18:45 (cur \| prev) +53‎ IanGilby talk contribs →‎* (#93) Need to address how we treat behaviours for the second value of food parts AND how they are derived.
					18:44 (cur \| prev) +104‎ IanGilby talk contribs →‎* (#92) There are food_bout rows that do not have a corresponding follow.
					18:43 (cur \| prev) -1‎ IanGilby talk contribs →‎* (#92) There are food_bout rows that do not have a corresponding follow.
					18:42 (cur \| prev) +38‎ IanGilby talk contribs →‎* (#91) There are food_bout rows that have fb_begin_feed_time > fb_end_feed_time.
					18:41 (cur \| prev) +75‎ IanGilby talk contribs →‎* (#90) There are food_bout rows for which the fb_fpl_local_food_part or fb_fpl_local_food_part2 does not have a matching value in codes.food_parts.
					18:40 (cur \| prev) +36‎ IanGilby talk contribs →‎* (#89) There is a food_bout row that has both a compound fb_fpl_local_food_part value and where fb_fpl_local_food_part2 is not null.
					18:38 (cur \| prev) +112‎ IanGilby talk contribs →‎* (#88) There are food_bout rows for which there is not a corresponding food name.
					18:37 (cur \| prev) +54‎ IanGilby talk contribs →‎* (#87) There are numerous duplicate fl_sci_food_name_gen values in food_lookup.
					18:34 (cur \| prev) +68‎ IanGilby talk contribs →‎* (#86) There are numerous instances in the food_part_lookup that that conflate name, initial, and/or the english translation.
					18:31 (cur \| prev) +72‎ IanGilby talk contribs →‎* (#85) There are numerous instances of local food names that translate to multiple scientific food names.
					18:29 (cur \| prev) +31‎ IanGilby talk contribs →‎* (#84) Some follows have a community with trailing spaces
					18:28 (cur \| prev) +74‎ IanGilby talk contribs →‎* (#83) There are AGGRESSION_EVENT rows where the Actor and Actee have the same animal ID.
					18:27 (cur \| prev) +80‎ IanGilby talk contribs →‎* (#82) There are AGGRESSION_EVENT rows where severity (ae_fight_category) is not an allowable value.

Related changes

5 July 2026

4 July 2026

3 July 2026

Navigation menu

Search