Split-Up Standard Fields Table and Move to DataTable

1 Initial Problem

With ILIAS 10 we will want and have to move the current table showing the list of Standard Fields for the user profile to a DataTable from UI-Components. This will lead to a few changes as the current implementation relies on form inputs inside the table. Additionally this table presently mixes Profile Fields and User Settings. 

2 Conceptual Summary

The Standard Fields will be Split-Up. The Profile Fields ("First Name", "Last Name", "Title, Birthday", "Salutation", "Avatar", "General Interests", "Offering Help", "Looking for Help", "Institution", "Department", "Street, Zip Code / Post Code", "City, State", "Country (Drop Down Selection)", "Phone, Office", "Phone, Home", "Phone, Mobile", "Fax", "E-Mail", "Second E-Mail", "Interests/Hobbies", "How did you hear about ILIAS?", "Matriculation Number", "Roles", "Organisational Units") will be shown together with the "Custom Fields" and the "User Profile Info" in a new Tab "User Profile".

The Remaining Fields ("Password", "Language", "Default Skin / Style", "Hits/Page", "Show your Account in "Who-is-Online", "Allow Contact Requests", "Allow On-Screen Chat Conversations", "Broadcast Typing", "Preferences", "Incoming Mail") will be kept in the Tab "Settings", but renamed to "User Default Settings".

We propose to get rid of the Field "Country (Free Text Input)" for new installations. For existing installations two migrations will be provided:

• You can either drop the field completely.
• Or you can move it to a Custom Field.

The two tables will be moved to a DataTable. The following changes will be made:

• The table will become read only.
• Each row will have the action "Edit".
• "Edit" will be opened in a RoundtripModal.

The table under "User Profile" >> "Standard Fields" will additionally have the following changes:

• The setting "Required", now under "Access" will receive its own column.
• The column "Export / Search" will be split up into two columns "Exportable" and "Visible in Certificates". All fields will have the option to be set as "Exportable" and/or "Searchable".
• The table will not need a column "Default".

The table under "Settings" >> "User Default Settings" will additionally have the following changes:

• The column "Export / Search" will be renamed to "Exportable". All fields will have the option to be set as "Exportable".
• The table will have a column "Default Value". This column will be of the type "Text".

3 User Interface Modifications

3.1 List of Affected Views

• Administration -> Users and Roles -> User Management -> Settings -> Standard Fields

3.2 User Interface Details

3.3 New User Interface Concepts

It is proposed to add a new column type `Listing` that only accepts listings.

3.4 Accessibility Implications

Ensuring accessibility will be simplified by moving to the 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 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

Ensuring security will be simplified by moving to the more consistent and standardized methods of data retrival provided by the DataTable.

7 Contact

• Author of the Request: Kergomard, Stephan [skergomard]
  
• Maintainer: Kergomard, Stephan [skergomard]
• Implementation of the feature is done by: Kergomard, Stephan [skergomard]

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 JAN 2024: Suggestion is highly appreciated and feature scheduled for ILIAS 10. The current suggestion violates the guideline from the KS and the Guideline for presenting Actions buttons in tables. There might be good reasons to always have a dropdown (also when only one action is available). Stephan will discuss the issue with the KS coordinators and UI/UX experts and probably suggest a change of the guideline(s).

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