Show Advanced KnowledgeHide Advanced Knowledge

Revision of News Overview

Currently not being pursued because another concept (timeline) has been decided by the JF: Migrate News on Communication » News to Timeline

1 Initial Problem

The "News" Overview Page (Communication menu) consists of legacy components and cannot be accessed via the central Kitchensink components, nor does it benefit functionally from changes to the framework.

Currently, there are several places where news is collected and displayed. On the dashboard, these are partly displayed as aggregated collective entries (e.g. 4 postings). News Page does not recognise such aggregated collective entries, so these news displays look different and are sometimes interpreted by users as different news.

In addition, only news from objects that have been added to the favourites can currently be displayed. If a course is not on the favourites list, news (even though there is some) is not displayed in the news (see FR: Revision of News Filter).

2 Conceptual Summary

The News page is used to get an overview of all news in ILIAS. News from various ILIAS objects (courses, groups) are collected and displayed chronologically in this central location.

The following information is relevant for the display of the news:

• Icon (type news)
• Title (what is it about)
• Content
• Call-to-action (e.g. button)
• Path to the object where the news was generated
• Creation Date
• Author of the news
• Access?

2.1 Transfer to Presentation Table

News can be of different lengths. From other news readers, one is used to seeing a first teaser and being able to consult the whole content if desired. This allows you to get an overview of the incoming news in a first view and optionally to deepen the desired news and look at its details. These requirements are fulfilled by the Presentation Table.

The individual elements of the current news are transferred to the Presentation Table entries (see screenshots Migration).

Expanding the entries allows more information about each news item to be displayed on the News page:

• Course and Group News show the content of their news.
• Files should show a preview of themselves.
• Forum posts show the content of the post.

The possibility to show a preview or the content of a news item can be extended for the other news items in the future.

2.2 Extended filter context

Currently, only news from objects that are in the favourites list can be displayed. Since ILIAS 6, new course and group memberships no longer appear directly in the Favourites list (formerly Personal Desktop > Overview), news may be missed because current courses and groups are not in the Favourites list.

It should therefore be possible to display "All" news that concerns me regardless of whether it is news from the favourites or my courses and groups.

If for some reason there is something against a revision of the news page, at least the filters with "My courses and groups" should be added. See Revision of News Filter

To be discussed

• Which ViewControl??
  • All / Favorites / My Courses and Groups
  • Last Week / Last Month / Last Year
• Aktuell kann ich jedes Objekt auf der Favoritenliste einzeln auswählen, um mir News anzeigen zu lassen. Weiterhin?

2.3 Show collective entries

On the dashboard (depending on the selection of the time span of the news) collective entries are displayed (e.g. 4 postings). This should be adopted for the presentation table. If such a collective entry is opened, the individual news entries are displayed.

To be discussed

• beeinflussen die Settings nur Dashboard oder auch News unter Communication?
• sollte von News-Page auf Settings geführt werden? View Control abhängig?
• wie soll einzelner Eintrag in einem Sammeleintrag dargestellt werden (Item List?)?

3 User Interface Modifications

3.1 List of Affected Views

• Communication > News

3.2 User Interface Details

3.3 New User Interface Concepts

evt. neue View Control für Anzahl Zeitspanne (wie Listingpanel: Calendar > List View)

3.4 Accessibility Implications

{ If the proposal contains potential accessibility issues that are neither covered by existing UI components nor clarified by guidelines, please list them here. For every potential issue please either propose a solution or write down a short risk assessment about potential fallout if there would be no solution for the issue. }

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

{ 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

{ 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, Zenzen, Enrico [ezenzen]
• 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}.