Set filter default on Registered Participants

This feature request is a part of the Calendar Revision III.

1 Initial Problem

By default, all course and group members are displayed in the "Participants" tab of a session. No distinction is made between registered and nonregistered participants.

Since otherwise only the actual members are displayed in courses and groups, it is confusing at first glance to see them all. Only if someone discovers the check mark "Registered" does an administrator recognize that a distinction has to be made here.

The filter could be used to filter for "Only Registered" people. To do this you would have to find "Show filter" and understand the pattern "more than just the actual participants are shown".

2 Conceptual Summary

Only those who actually attend the session should be displayed. Therefore only the "registered" participants should be displayed and not all of them. If necessary, the filter can be used to display all participants of the course or group.

In combination with the feature Set Registered Attribute for Registration Procedure No Registration Necessary: If no registration is required, all members will get the attribute "Registered" and will be displayed accordingly if by default only "Registered" are displayed.

3 User Interface Modifications

3.1 List of Affected Views

• Session > Participants

3.2 User Interface Details

{For each of these views please list all user interface elements that should be modified, added or removed. Please provide the textual appearance of the UI elements and their interactive behaviour.}

3.3 New User Interface Concepts

No new UI-components

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

6 Funding

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

• Universität Bern

7 Discussion

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