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
{{ message }}
This repository has been archived by the owner on Jan 15, 2019. It is now read-only.
The only way to analyze survey results across multiple surveys is to download all of the JSON files and do some parsing. I want to be able to go to /s/results to see some statistics on all surveys. This could be just a simple table with the following columns:
Survey ID
Date
Survey title (or meeting title)
Number of responses
Clicking on the row should take me to the corresponding Results page. For example, clicking on the survey with ID of 1 will take me to /s/1/results.
Design Considerations
This should be a JSON API as well. For example, I might want to get every single response to "How did you find out about this event" from every survey in the past year. There should be some JSON endpoint which will get me this information.
The /s/results page should basically be a shallow wrapper around this API that presents the information in a nice HTML table.
The text was updated successfully, but these errors were encountered:
The only way to analyze survey results across multiple surveys is to download all of the JSON files and do some parsing. I want to be able to go to
/s/results
to see some statistics on all surveys. This could be just a simple table with the following columns:Clicking on the row should take me to the corresponding Results page. For example, clicking on the survey with ID of 1 will take me to
/s/1/results
.Design Considerations
This should be a JSON API as well. For example, I might want to get every single response to "How did you find out about this event" from every survey in the past year. There should be some JSON endpoint which will get me this information.
The
/s/results
page should basically be a shallow wrapper around this API that presents the information in a nice HTML table.The text was updated successfully, but these errors were encountered: