Revamp Course Relevant User Data

1 Initial Problem

The feature «Course Relevant User Data/ User Agreement» is not easy to understand:

• The presentation of privacy relevant data upon joining courses is activated in Administration > Privacy.
  • The labeling is weired, typically it is "join" not "entering".
• Settings of the User Object govern what data is always entailed in the presentation of privacy relevant data upon joining courses 
  • Course / group administrators must have in-depth knowledge to check what is presented to their members to be. This should be presented in a much clearer fashion. 

User Confirmation off, no course relevant fields

User Confirmation on

User Confirmation off, but some course relevant fields

2 Conceptual Summary

• The relations of the settings in the administration and the settings on course specific field should be clarified and straightend out. 

3 User Interface Modifications

3.1 List of Affected Views

• Course > Settings > Course Relevant User Data 
• Course > Join > User Agreement
• Group  > Settings > Group Relevant User Data 
• Group > Join > User Agreement
• Administration > Users and Roles > Privacy and Security > Protection of User Profile Data
• Administration > Users and Roles > Settings > Standard Fields > Access
• Administration > Users and Roles > Settings > Custom Fields > Access

3.2 User Interface Details

3.3 New User Interface Concepts

No new interface concepts are used.

3.4 Accessibility Implications

There are no accessibility implications. 

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

No additional personal data is stored. This feature merely shows it in one new place (Course Revelant User Data) to users with "Edit Settings" permission. 

6 Security

There are no known security issues implications. 

7 Contact

• Author of the Request: Tödt, Alexandra [atoedt]
• Maintainer: Meyer, Stefan [smeyer]
• 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}.