[JN-TBD] Refactoring pre-enroll surveys #1433
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
DESCRIPTION (include screenshots, and mobile screenshots for participant UX)
Updates pre-enrollment surveys to be a survey type, rather than have a dedicated data model attribute. this refactor will need to be done in two stages in order to avoid downtime. Stage 1 (this PR) migrates existing pre-enroll surveys and updates the frontend to read the migrated versions, but does not remove the data fields. Stage 2 would remove the data field
The big advantage of this is an overall simplification of our data model, and corresponding improvements in the UX. For example, this gives us the ability to publish pre-enroll surveys individually, which we did not have before. the downside is that this no longer enforces that a study env can only have a single pre-enrollment survey, so we'll have to think about what that means
TO TEST: (simple manual steps for confirming core behavior -- used for pre-release checks)