Duplicating surveys as part of participant enrollment caused substantial weirdnesses in the database for intake surveys. Because only the Assessments table was duplicated, and none of the other tables, and because impact surveys were duplicated to intake surveys, it caused the various relationships from Assessments to the other tables to be in odd states. With an impact being duplicated to intake, the baseline assessment ID is 0, and then cannot be updated when actually filling out the intake survey. Furthermore, if the assessment was not subsequently done, reports based on the other tables, such as in reports/assessments.php are inaccurate.
Fix needs a specialized script to clean up the data.
Related to Issue #234: Number of surveys used for assessment report
Related to Issue #219: Intake association
Duplicating surveys as part of participant enrollment caused substantial weirdnesses in the database for intake surveys. Because only the Assessments table was duplicated, and none of the other tables, and because impact surveys were duplicated to intake surveys, it caused the various relationships from Assessments to the other tables to be in odd states. With an impact being duplicated to intake, the baseline assessment ID is 0, and then cannot be updated when actually filling out the intake survey. Furthermore, if the assessment was not subsequently done, reports based on the other tables, such as in reports/assessments.php are inaccurate.
Fix needs a specialized script to clean up the data.
Related to Issue #234: Number of surveys used for assessment report Related to Issue #219: Intake association