Users can choose a question block in a feedback-survey

If you need any help in filling out this wiki page, please visit our ILIAS Community FAQ. And please complete the metadata information in the right column after having created the page.

1 Initial Problem

Currently questions for feedback-surveys can be created and managed only by admins. This leads to following difficulties:

• Survey participants cannot choose questions they want to get an answer to by requesting  a feedback
• A new survey must be created for each feedback-focus (question block), even if there are only slight differencies between single questions in these blocks

2 Conceptual Summary

We propose to extend the permissions of survey participants and let users to choose the question blocks themselves. To reach this goal two ILIAS-Objects should be modified.

ILIAS Question-Pools Survey:

• gets a new tab Question Blocks
• a new question block can be created by admin - unlimited number of question blocks can be created here
• single questions should be previously created in the Questions-tab in order to move them to question blocks
• one question can be used many times in different question blocks
• competence service should be activated for Question Pool Survey in order to assign each question to one competence

• gets a new option in the settingstab -  appraisees can choose a question block, which lets participants to choose one question block. Note: single questions as well as question order should be inherited from Question Pools Survey automatically. Appraisees  cannot add or create new questions themselves.
• a question block can be selected in Question- Tab

3 User Interface Modifications

3.1 List of Affected Views

New Object - Survey - Settings
New Object - Question Pool Survey - Settings

3.2 User Interface Details

3.3 New User Interface Concepts

{If the proposal introduces any completely new user interface elements, you might consult UI Kitchen Sink in order to find the necessary information to propose new UI-Concepts. Note that any maintainer might gladly assist you with this.}

4 Technical Information

{The maintainer has to provide necessary technical information, e.g. dependencies on other ILIAS components, necessary modifications in general services/architecture, potential security or performance issues.}

5 Contact

• Author of the Request: 
• Maintainer: {Please add your name before applying for an initial workshop or a Jour Fixe meeting.}
• Implementation of the feature is done by: {The maintainer must add the name of the implementing developer.}

6 Funding

If you are interest in funding this feature, please add your name and institution to this list.

• …

7 Discussion

8 Implementation

{The maintainer has to give a description of the final implementation and add screenshots if possible.}

Test Cases

Test cases completed at {date} by {user}

• {Test case number linked to Testrail} : {test case title}

Approval

Approved at {date} by {user}.