If the questions are changed to a JSON schema, where a set of questions is stored as some predefined types with relevant attributes - each group would have more freedom regarding what questions they ask. Especially useful for backup and revue admissions, but might be useful for committees as well - who knows.
The idea is to allow certain types of questions (e.g. long text, short text, email, number, descriptive text), and then store the questions as a JSON list of those questions.
Current approach: use pydantic for validation
Will first do it for header_fields, then extend to group applications if that is successful.
TODO(: Top down
If the questions are changed to a JSON schema, where a set of questions is stored as some predefined types with relevant attributes - each group would have more freedom regarding what questions they ask. Especially useful for backup and revue admissions, but might be useful for committees as well - who knows.
The idea is to allow certain types of questions (e.g. long text, short text, email, number, descriptive text), and then store the questions as a JSON list of those questions.
Current approach: use pydantic for validation
Will first do it for header_fields, then extend to group applications if that is successful.
TODO(: Top down