Rationale: Difference between revisions
From MoodleDocs
Created page with "The idea standing after the development of this module is to provide answers to the more frequent requirements of end users. Their frequent requirements are: * conditional branc..." |
m Note about intent to not migrate this page to moodledev.io |
||
| (7 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
{{Template:obsolete}} | |||
The idea standing after the development of this module is to provide answers to the more frequent requirements of end users. | The idea standing after the development of this module is to provide answers to the more frequent requirements of end users. | ||
Their frequent requirements are: | Their frequent requirements are: | ||
* | ==at element level== | ||
* possibility to add custom question type matching specific needs | |||
* question predefined value | * question predefined value | ||
* question level validation | * question level validation | ||
* reduce, as much as possible, the range of possible answers | * reduce, as much as possible, the range of possible answers | ||
* mandatory questions | * mandatory questions | ||
* have some typographic option to display elements in different ways | |||
* tools to quickly reuse set a specific questions that never change in each survey | |||
==at survey level== | |||
* conditional branching | |||
* force the user to provide a his/her own answer | * force the user to provide a his/her own answer | ||
* | * subset of questions available to teachers ONLY | ||
* include permission management for groups of users submitting surveys in behalf of the same institution | |||
* use captcha | * use captcha | ||
* | * allow/deny submitted survey modification (including deletion) | ||
* allow a backup copy of submitted surveys each time they are modified in order to preserve their history | |||
* speed up form fill as much as it is possible | |||
==at report level== | |||
* possibility to add custom reports | |||
* export of submitted surveys | |||
Latest revision as of 16:27, 30 April 2024
| Warning: This page is no longer in use. The information contained on the page should NOT be seen as relevant or reliable. |
The idea standing after the development of this module is to provide answers to the more frequent requirements of end users.
Their frequent requirements are:
at element level
- possibility to add custom question type matching specific needs
- question predefined value
- question level validation
- reduce, as much as possible, the range of possible answers
- mandatory questions
- have some typographic option to display elements in different ways
- tools to quickly reuse set a specific questions that never change in each survey
at survey level
- conditional branching
- force the user to provide a his/her own answer
- subset of questions available to teachers ONLY
- include permission management for groups of users submitting surveys in behalf of the same institution
- use captcha
- allow/deny submitted survey modification (including deletion)
- allow a backup copy of submitted surveys each time they are modified in order to preserve their history
- speed up form fill as much as it is possible
at report level
- possibility to add custom reports
- export of submitted surveys
