Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create a new Form structure #273

Open
prashtx opened this issue Feb 10, 2015 · 4 comments
Open

Create a new Form structure #273

prashtx opened this issue Feb 10, 2015 · 4 comments
Assignees

Comments

@prashtx
Copy link
Contributor

prashtx commented Feb 10, 2015

The current Form document structure was pretty ad hoc, and it has resulted in some messy and fragile code. In particular, there's some lack of consistency among radio questions, checkboxes, and other types. We also tend not to process the form recursively (partly for mobile performance reasons), so the tree structure is not as helpful as intended.

@prashtx prashtx self-assigned this Feb 10, 2015
@prashtx
Copy link
Contributor Author

prashtx commented Feb 10, 2015

To what extend do we want to comingle layout with the data/structural aspects? Do we want to support spacers?

What's a future-proof way to support contextual help info that might contain imagery? Embedding data URIs removes any dependency on hosting and makes offline mode simpler, but we'd increase the size of a form document substantially.

@prashtx
Copy link
Contributor Author

prashtx commented Feb 10, 2015

Conditional questions should be triggered based on a simple but flexible DSL, so that we can condition on previous answers, aspects of the base data, or some future requirement (like time of day).

@hampelm
Copy link
Contributor

hampelm commented Feb 10, 2015

We might want to group questions into logical groups (like pages) at some point

@hampelm
Copy link
Contributor

hampelm commented Feb 10, 2015

This is much more on the UI / implementation side, but a very large percent of data quality problems come from changing question and answer names. Any question change creates a new column. Answer values can be absurdly long. Answer changes can bifurcate the data needlessly. We should find a way to stabilize these more. That might include exposing field names to users.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants