Repeatedly filling in the same Self-Evaluation Survey with Competences

1 Initial Problem

Currently surveys can be filled out only once.

If a recipient has to take the survey more than once, it has to copied or the partcipation data needs to exported and then be deleted.

It is a problem, if survey is used for measuring the development of skills or competencies over time.

2 Conceptual Summary

This feature applies only to the "Self-Evaluation Only" Type of Survey.

Participants should be able to access the same survey repeatedly and create a kind of longitudinal survey.

Activation in Settings 

• We propose to add additional feature for survey "Activate repetition of a survey", which should enable repeatedly filling in the same survey. 
• If the box is checked, patricipants can fill in the same survey until the suvey would be closed or deleted. If the box is unchecked, the survey can be filled in only once (default setting).
• The numer of runs and the timing of runs is not limited or regulated. 
• The Access to Results remains the same. Participants can either have "No Access to Results", "Access to Own Self-Evaluations" or "Access to Self-Evaluations of All Participants"

Filling in the Survey

• An additional run can be started anytime once the prior run was ended by "Finish Survey" and the respective confirmation.
• The "Resume Survey" button changes to "Start Survey".  

Presentation of Results 

• Visualization of results (especially in the feedbackmode) - see already existing feature-request: https://docu.ilias.de/goto_docu_wiki_wpage_5259_1357.html
• Competence results and achieving competences (aggregation of results) - how many competency entries should be written and how often?

3 User Interface Modifications

3.1 List of Affected Views

Survey → Settings → Other

3.2 User Interface Details

3.3 New User Interface Concepts

Results Tab

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

No impact on privacy and security issues

6 Security Implications

We do not see any security issues

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

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