Study Programme: Quota-Report for all Study Programmes

1 Initial Problem

The memberlist of Study Programmes allows to get an overview about the users and their progress for one programme on a single user basis. The feature Study Programme: Filters and More Columns for Member List will improve that list for reporting purpose. It still won't be possible to get an overall view on all programmes in the system. Such an overview, however, would be beneficial from a high level management perspective, e.g. to plan future programmes or resources or to get an overview over where people spend their time in education.

2 Conceptual Summary

The Administration of the Study Programmes gets a new Tab "Reports" that will contain a report that presents agregated data over the Study Programmes in the system. For every Study Programme that has a member or that is the root node of a programme

• the number of memberships
• the number of distinct users that are members
• the number of completed failed, in progress, memberships
• the relative amount of completed/failed/in progress regarding memberships in percent and
• the relative amount of distinct user that have a valid qualification

3 User Interface Modifications

3.1 List of Affected Views

{Please list all views (screens) of ILIAS that should be modified, newly introduced or removed.}

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

{If the proposal introduces any completely new user interface elements, you might consult UI Kitchen Sink in order to find the necessary information to propose new UI-Concepts. Note that any maintainer might gladly assist you with this.}

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: {Please add your name.}
• 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.

• …

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