| Rev | Line | |
|---|
| [433] | 1 | Todo |
|---|
| 2 | ==== |
|---|
| 3 | |
|---|
| 4 | * scale with multiple questions/items |
|---|
| 5 | - create a configuration version of the widget (either built-in or |
|---|
| 6 | separate) with click-to-edit labels (indicate by border, hover text?) |
|---|
| 7 | and an extra 'Click to add row' in the text column. |
|---|
| 8 | - make items in configuration an object, so you can add meta-data |
|---|
| 9 | * export answers for a survey run |
|---|
| 10 | * write a spec for the codes |
|---|
| 11 | |
|---|
| 12 | Checklist |
|---|
| 13 | ========= |
|---|
| 14 | |
|---|
| 15 | * Form validation |
|---|
| 16 | * Input validation & escaping |
|---|
| 17 | * Output escaping |
|---|
| 18 | * Review current JSON formats, do they allow for extension or extra meta-data? |
|---|
| 19 | |
|---|
| 20 | Open issues |
|---|
| 21 | =========== |
|---|
| 22 | |
|---|
| 23 | * Do different inputs in one question get different codes? E.g. in |
|---|
| 24 | To ease exporting into other programs and easy communication, the codes |
|---|
| 25 | are important I think. It should be easy to pronounce, and easy to |
|---|
| 26 | find in the tool (people might get a dataset and not know where it |
|---|
| 27 | came from). |
|---|
| 28 | * What if a question is included in a survey multiple times. Use block |
|---|
| 29 | or allow a pre/post-fix on the code to differentiate it. |
|---|
| 30 | Should not be too much work, so if an scale with 5 items has 5 codes, |
|---|
| 31 | you should be able to set a prefix on all of them at once. |
|---|
Note: See
TracBrowser
for help on using the repository browser.
