Integration of survey questions in ILIAS learning modules

1 Initial Problem

Only test questions can be integrated into ILIAS learning modules. Often users want to collect feedback within a learning module and/or enable users to enter text. This is not possible with the test questions,

2 Conceptual Summary

Survey questions should be available as page elements in the page editor of ILIAS Learning Modules. Survey questions and test questions are strictly separated. The Page Editor offers the actions "Insert Test Question" and "Insert Survey Question".

After users click on "Insert Survey Question", you will be taken to the question type selection and then to a form "Create Question". Instead of creating the question in the learning module, questions can also be created from question pools.

The results of test and survey questions are also managed separately. The "Questions" tab, which until now has been the result view for test questions, is renamed "Test Questions". An additional tab "Survey Questions" is introduced. The tab "Survey Questions" contains two sub-tabs "Statistic" and "Details".

• The sub-tab "Statistic" corresponds to the "Overview" tab in the survey, but provides additional information about the chapter/page in which the question was inserted.
• The "Details" sub-tab corresponds to the "Details" tab in the survey, but provides additional information about the chapter/page in which the question was inserted

Weitere Anforderungen und Ideen:

3 User Interface Modifications

3.1 List of Affected Views

• Edit ILIAS Learning Module > Insert Survey Question
• ILIAS LEarning Module > Tab "Survey Questions"
• ILIAS Learning Moduel > Tab "Test Questons"

3.2 User Interface Details

3.3 New User Interface Concepts

none

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 Privacy Information

{ Please list all personal data that will need to be stored or processed to implement this feature. For each date give a short explanation why it is necessary to use that date. }

6 Security Implications

{ Does the feature include any special security relevant changes, e.g. the introducion of new endpoints or other new possible attack vectors. If yes, please explain these implications and include a commitment to deliver a written security concept as part of the feature development. This concept will need an additional approvement by the JourFixe. }

7 Contact

• Author of the Request: Zenzen, Enrico [ezenzen]
• Maintainer: Killing, Alexander [alex]
• Implementation of the feature is done by: {The maintainer must add the name of the implementing developer.}

8 Funding

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

• …

9 Discussion

10 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}.