Feature Wiki

Information about planned and released features

Tabs

Revision of News Filter

1 Initial Problem

News can currently be filtered by favourites or individual courses or objects. Since with ILIAS 6 only manually added objects appear in the favourites, it is no longer possible to display all news of all objects. Especially news of all courses and groups are relevant for the teaching context, so that a user can see at a glance news of all courses and groups in which he/she is currently enrolled.

The aim of this feature is to provide the user with quick access and thus an overview of the collected news of all courses and groups.

Current Situation ILIAS 7

2 Conceptual Summary

The current filter "Context" is to be extended with a filter "My courses and groups". If this is selected, news of all courses and groups I am enrolled in (the same ones that are visible in the menu "Repository > My Courses and Groups) will be displayed.

Requirements:

  • The precondition for the news to be displayed to me is, of course, that the course or group has this option activated.
  • As with the other context filters, the news items displayed are listed chronologically one below the other.

To be discussed
What is the default? Favorites or News for all my courses and groups?

  • As this is a collection of different news sources, the entry should be default in the dropdown (if it has no performance issues). => Was passiert mit bisherigen Einstellungen, bleibt dies gleich? Allenfalls weiterhin Favoriten als default.

3 User Interface Modifications

3.1 List of Affected Views

  • Communication > News

3.2 User Interface Details

3.3 New User Interface Concepts

No new UI-elements.

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: Seiler, Yvonne [yvseiler] (Universität Bern)
  • 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}.

Last edited: 28. Apr 2021, 17:09, Seiler, Yvonne [yvseiler]