Feature Wiki
Tabs
Usability Improvement for Columns Control in Table Views
Page Overview
[Hide]1 Initial Problem
The Column Selection for table views has the following issues
- The initial table presentation does not reveal if the table supports additional columns (beyond those already display) - you need to click "Columns" to see the full list of columns
- For tables with many columns the Dropdown is hard to use and may even break the layout
![](./data/docu/mobs/mm_91810/2022-03-13_18_39_50-test7_Benutzerverwaltung.png?il_wac_token=0f5cbce5aedb5bbbd57d86c536c69dcf20182f74&il_wac_ttl=5&il_wac_ts=1725755891)
2 Conceptual Summary
The following Mockup gives an illustration of how the "Columns" control is optimized for a large number of columns
![](./data/docu/mobs/mm_91811/2022-03-13_18_27_29-test7_Benutzerverwaltung_100_0.png?il_wac_token=0f5cbce5aedb5bbbd57d86c536c69dcf20182f74&il_wac_ttl=5&il_wac_ts=1725755891)
3 User Interface Modifications
3.1 List of Affected Views
- All Table views which have the "Columns" control element
3.2 User Interface Details
- The "Columns"-Control shows 2 counters within brackets: ([Active Columns]/[Available Columns]) - c.f. the mockup
- The Dropdown gets a max-height (potentially adapted to the current screensize) and a vertical scrollbar if the number of columns exceeds the available height
- the scrollbar only scrolls the available columns
- the footer of the dropdown is fixed and contains a "Select all" check-box + "Update" button + "Reset" Button
- The "Select all" toggles between selecting all or none of the columns (note: from my experience the first column of a table cannot be de/selected - like "username" for the user administration)
- The "Reset" button resets to the default selection
3.3 New User Interface Concepts
-
3.4 Accessibility Implications
-
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: Kiegel, Colin [kiegel]
- 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}.
Last edited: 13. Mar 2022, 19:00, Kiegel, Colin [kiegel]