(3 intermediate revisions by the same user not shown)

Line 1,113:

Will re-review this should a temporal extension be out of budget, etc.

== * (#46) There are follow_arrivals where non-females have a cycle code that is other than <code>n/a</code> ==

== (#46) There are follow_arrivals where non-females have a cycle code that is other than <code>n/a</code> ==

=== Problem ===

Line 1,150:

Change non-females (INCLUDING UNKNOWN SEX) who have a cycle code of <code>0</code> to a cycle code of <code>n/a</code>. IAN TO FIX IN ACCESS

IAN FIXED IN ACCESS 3/25/2026

== (#47) There are follow_arrivals where females that are too young have a cycle code of <code>U</code> ==

Line 1,587:

Line 1,589:

This is a brute-force, but adequate, solution because it does not validate anything concerning the rows affected.

== * (#60) Invalid biography_update_log.made_by values ==

== (#60) Invalid biography_update_log.made_by values ==

=== Problem ===

Line 1,602:

Line 1,604:

WHERE people.person = biography_update_log.made_by);</pre>

=== SOLUTION ===

IAN ~~TO CHANGE~~ THE SINGLE ENTRY TO EVL

IAN CHANGED THE SINGLE SF/EVL ENTRY TO EVL IN ACCESS 3/25/2026

== * (#61) Invalid follow date/focals pairs in follow_arrival ==

Line 1,665:

Line 1,667:

Create a <code>none</code> value in ARRIVAL_SOURCES, and use that value instead of <code>NULL</code> in follow_arrival table in the <code>clean</code> schema.

== * (#64) There are follow_arrival rows with <code>NULL</code> fa_type_of_certainty values ==

== (#64) There are follow_arrival rows with <code>NULL</code> fa_type_of_certainty values ==

=== Problem ===

Line 1,683:

Line 1,685:

=== Solution ===

IAN fixed in Access 3/25/2026

IAN TO FIX

sokwedb - Recent changes [en]

Conversion Data Issues

@@ Line 1,113: / Line 1,113: @@
 Will re-review this should a temporal extension be out of budget, etc.
-== * (#46) There are follow_arrivals where non-females have a cycle code that is other than <code>n/a</code>  ==
+== (#46) There are follow_arrivals where non-females have a cycle code that is other than <code>n/a</code>  ==
 === Problem ===
@@ Line 1,150: / Line 1,150: @@
 Change non-females (INCLUDING UNKNOWN SEX) who have a cycle code of <code>0</code> to a cycle code of <code>n/a</code>. IAN TO FIX IN ACCESS
+IAN FIXED IN ACCESS 3/25/2026
 == (#47) There are follow_arrivals where females that are too young have a cycle code of <code>U</code>  ==
@@ Line 1,587: / Line 1,589: @@
 This is a brute-force, but adequate, solution because it does not validate anything concerning the rows affected.
-== * (#60) Invalid biography_update_log.made_by values ==
+== (#60) Invalid biography_update_log.made_by values ==
 === Problem ===
@@ Line 1,602: / Line 1,604: @@
                           WHERE people.person = biography_update_log.made_by);</pre>
 === SOLUTION ===
-IAN TO CHANGE THE SINGLE ENTRY TO EVL
+IAN CHANGED THE SINGLE SF/EVL ENTRY TO EVL IN ACCESS 3/25/2026
 == * (#61) Invalid follow date/focals pairs in follow_arrival ==
@@ Line 1,665: / Line 1,667: @@
 Create a <code>none</code> value in ARRIVAL_SOURCES, and use that value instead of <code>NULL</code> in follow_arrival table in the <code>clean</code> schema.
-== * (#64) There are follow_arrival rows with <code>NULL</code> fa_type_of_certainty values ==
+== (#64) There are follow_arrival rows with <code>NULL</code> fa_type_of_certainty values ==
 === Problem ===
@@ Line 1,683: / Line 1,685: @@
 === Solution ===
+IAN fixed in Access 3/25/2026
-IAN TO FIX