| 3 | | Use this page to document use-cases. |
| | 3 | == Surveys == |
| | 4 | |
| | 5 | Survey is a sequence of questions, with possible images, headers |
| | 6 | |
| | 7 | == Conducting == |
| | 8 | |
| | 9 | * Personalized questionnaire. A limited amount of surveys is conducted, instantiated in advance. They can have e.g. unique response URL's. |
| | 10 | * Bulk questionnaire. Multiple respondents can fill in one questionnaire. |
| | 11 | |
| | 12 | * A facilitator can add properties/answers to a survey instance. Any metadata that is relevant for later understanding of the data. E.g. Veerkracht, instantiate a bulkQ for every manager, adding him as metadata. The link for that Q can be send to his lackies. |
| | 13 | * Continuate a Q started earlier. Use cookies, generate a continuation URL that people can bookmark or something like that. |
| | 14 | |
| | 15 | === Types of questions === |
| | 16 | |
| | 17 | * Free text questions, 'finish the sentence ...' questions |
| | 18 | * Free numerical/date/email/phone entry (possibly within range) |
| | 19 | * Yes/No, Agree/Disagree, Checkbox+Description |
| | 20 | * ++/+/0/-/--, labels for every option or at extremes, values 0...n or -m .. 0 .. m |
| | 21 | * Ordering questions (order several items, either by giving them unique values or really ordering them) |
| | 22 | * Fixed sum questions (divide amount n over several items) |
| | 23 | |
| | 24 | * Questions can have multiple items and multiple scales, resulting in a variable matrix (possibly and often size 1x1 though). |
| | 25 | |
| | 26 | == Data unification == |
| | 27 | |
| | 28 | An important goal is that survey data and game data are expressed in the same way, so their data series can be used together in statistics and reports. For RDF the Data Cube vocabulary seems fit for that. The system should be able to adapt for different structured game data, unknown in advance. |
