Splitup ECS Participant View

If you need any help in filling out this wiki page, please visit our ILIAS Community FAQ. And please complete the metadata information in the right column after having created the page.

1 Initial Problem

The ECS Participants view is one big table containing a kind of different information.

2 Conceptual Summary

The view contains the following information:

• Members of the corresponding community
• Metadata for each participant
• The in and exported resources for each participant
• The role of the corresponding participant

This information should be split up into different pages containing the different settings, which also depend on each other.

• For each participant, it should be set if is enabled and only then, there should be the abillity in the settings tab to set the in and export settings for this participant
• The should be one global setting for the diffent role, as there can only be one global campus management system

3 User Interface Modifications

3.1 List of Affected Views

• … { Please list titles of 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. }

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

No personal data is stored in this feature. It only reorganises the currently available information.

6 Security

Only the currently available screens will be revised. The security will increase, as the new UI framework and the Refinery framework will be used

7

• ContactAuthor of the Request: Seeland, Per Pascal [PerPascalSeeland]
• Maintainer: Seeland, Per Pascal [PerPascalSeeland] 
• Implementation of the feature is done by: Seeland, Per Pascal [PerPascalSeeland]

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