You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The data handler currently saves preset observational questions as JSON strings, which winds up displaying strangely in the Collected Data view:
There are two ways we could fix this:
Update the data handler to save each key/value pair as a separate SurveyComponent
Pros:
Semantically matches the purpose of this question (to create common groups of SurveyComponents)
Maintains the same representation of the data between storage, display, and export
Cons:
Unclear how much we'd have to refactor the DAD source data selector in order to group the separate SurveyComponents properly
We'd have to save a display name that would make sense as a column name
Update the frontend code to format the JSON as columns in DataTables
Pros:
Relatively simple refactor from the current state of the code
Cons:
Creates representational mismatch between storage, display, and export
Further complicates frontend data processing, which is already complicated
Requires either transforming the data for both DataTables display and data export, or tightly coupling these two systems with the same transformation logic
The text was updated successfully, but these errors were encountered:
I've been thinking about this a little more as I implement ACS data comparisons. Let's hold off for now; it may turn out to be much easier to use JSON for ACS data purposes.
The data handler currently saves preset observational questions as JSON strings, which winds up displaying strangely in the Collected Data view:
There are two ways we could fix this:
Update the data handler to save each key/value pair as a separate SurveyComponent
Update the frontend code to format the JSON as columns in DataTables
The text was updated successfully, but these errors were encountered: