Improved look of Staff List

1 Initial Problem

The current page for displaying the Staff of a superios needs to be moved to kitchen sink.

2 Conceptual Summary

All elements will be moved to kitchen sink. To accomplish that, the legacy table will be exchanged by the UI Standard Listing Panel (see mockups).

3 User Interface Modifications

3.1 List of Affected Views

• Organisation > Staff List

3.2 User Interface Details

Filter and export are not provided automatically in the panel, like it was in the legacy table before. These functions will be added manually above the panel.

The panel offers a viewcontrol for pagination and sortation (not included in the mockup). The sortation can be done by first name, last name and login.

Which properties are displayed for the users depends on which User Fields have been ticked with "Visible in Staff" (see «Visible in Staff» for User Standard Fields) in the administration. It will no longer be possible for users to choose this themselves, like it was before in the legacy table.

3.3 New User Interface Concepts

No new UI elements

3.4 Accessibility Implications

No accessibility implications

4 Technical Information

None

5 Privacy

No privacy issues

6 Security

No security issues

7 Contact

• Author of the Request: Spirou, Ilias [ispirou], Famula, Thomas [tfamula]
• Maintainer: Famula, Thomas [tfamula]
• Implementation of the feature is done by: Famula, Thomas [tfamula]

8 Funding

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

• …

9 Discussion

JourFixe, ILIAS [jourfixe], 22 JUL 2024: We highly appreciate this suggestion and accept the feature for ILIAS 10. As the presentation of the staff members is in the main focus of this presentation, the listing panel seems to be a better solution than a data table.

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}

Privacy

Information in privacy.md of component: updated on {date} by {user} | no change required

Approval

Approved at {date} by {user}.