Feature Wiki

Information about planned and released features

Tabs

ILIAS page editor for info page - basic implementation

Page Overview

[Hide]

1 Initial Problem

While the Info tab is intended as a kind of cover or teaser page for an object, it falls short of this intention:

  • Most Info tabs do not offer any way to add information on target group or educational purpose or similar. The Info tab offers metadata to users that is irrelevant or confusing.
  • In courses Tutorial support can add texts for the Info-tab at Settings » Course Information » General Information. However this text cannot be formatted or layouted, there is no possibility to link. 

2 Conceptual Summary

  • The Info page allows adding ILIAS page editor content. User with "Edit Settings" permission get an "Edit Page" Buton on the Info-tab.
  • Clicking the "Edit Page"- Button opens the Page Editor. The metadata sections like General, Additional Information or the Tags section are NOT displayed within the Editor.
  • The created page content will be dispayed above the metadata sections.

3 User Interface Modifications

3.1 List of Affected Views

  • info page (e.g. course, file, learning module, ...)

3.2 User Interface Details

3.3 New User Interface Concepts

none

3.4 Accessibility Implications

none

4 Technical Information

No technical issues.

5 Privacy

For general information on the service, see the InfoScreen PRIVACY.md.

This feature request integrates the COPage service into the InfoScreen service. For personal data being stored, presented and deleted by the COPage service, see the COPage PRIVACY.md file.

No additional personal data related functionality is implemented.

6 Security

no forseen issues

7 Contact

8 Funding

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

  • …

9 Discussion

  • Kergomard, Stephan [skergomard], 26 APR 2022: As I already commeted on the "advanced" Version of this article, I believe we should clarify the role and future of the Info-Tab first, before we start adding features to it. I would suggest to have a workshop on this and then make a decision for the Info-Tab that MUST be implemented for all Modules, before we go on with this.

Seiler, Yvonne [yvseiler], 13 JUN 2022: +1 swiniker. I also recommend that the direction and perspective of the info page should be clarified in a workshop. There seems to be several perspectives (show individual data, no info-screen at all, place where users get if they have no access, place everything we don't have a better place for it,...)

There is currently another FW article improve metadata sections on info page on the UI Clinic agenda that also deals with the info page, where the same questions need to be clarified. In addition, there is also the idea of a start page (e.g. for test and survey) and therefore the question of how the two could relate to each other.

In the workshop, questions can be clarified such as:

  • To whom will it be displayed in which context and which information should it contain and why (goal and purpose)? 
  • What do we want to achieve with the info page in the future (requirements, needs)?
  • What does the manual adaptation of individual info pages entail, what purpose does it serve? Is the info page the right place for this?

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

Last edited: 13. Jun 2022, 08:49, Seiler, Yvonne [yvseiler]