Declutter Course «Info-Page»

1 Initial Problem

The Info Page displays some terrible defaults. Please check the Course screenshot:

• Language is derived from user setting. This may well be wrong and is not helpful. 
• Coypright is derived from default and may well be wrong. There is no need to state all rights reserved unless it is true. 
• In the Course the user is set as tutorial support without consent. This violates privacy expectations. 
• The Description is presented without an Identifier, but thats just doubling the description under the course title. 

Screenshot

2 Conceptual Summary

1. On the Info Page the Langue Field the Metadata should no longer be displayed to any user. Oftentimes the "Language" field clutters the Info-tab and is not very helpful. Especially if the object is multi-lingual. 
2. Copyright should not be automatically set unless done manually.
3. Tutorial support should not be set unless the person consented. 

3 User Interface Modifications

3.1 List of Affected Views

• info page of any objects (e.g. file, course, ...)

3.2 User Interface Details

3.3 New User Interface Concepts

None

3.4 Accessibility Implications

No known issues.

4 Technical Information

No technical issues.

5 Privacy

See Info Screen PRIVACY.md. Some data like owners/creation date is already presented to users with "Edit" permission only.

6 Security

No foreseen security issues. 

7 Contact

• Author of the Request: Tödt, Alexandra [atoedt]
• 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

This article was separated from Some Data on Info Page is only presented with «Edit Settings» upon request of the project manager. 

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