Enforcing Guideline for Top Actions

1 Initial Problem

With ILIAS 4.2 we introduced a new navigation area on the top right side of an object's title and called it "Top Actions" [1]. With this new UI element we also introduced a Top Actions Guideline and declared it effective from release 4.2. This means that all new repository objects that were introduced with 4.3 and newer have to implement this navigation element. And existing components could introduce this element as a bugfix (generally financed).

Unfortunately, we lost sight of this guideline somewhat and did not follow up on compliance. To make the user interface a little more straightforward and to support the resolution of issues such as Mantis #36638, this page has been created. We try to push it for ILIAS 11.

2 Conceptual Summary

In a first step we have to make an investigation about the current implementation of this guideline in all repository objects. Guiding questions would be:

1. Does the component provide a 'top actions' dropdown?
2. Which actions are provided by the dropdown?
3. Which actions do belong there due to the guideline – and which should be moved to another place?

This investigation will give us a good overview to decide upon the further steps of this development activity.

In a second step we should analyse if there are cross-component actions that are not tackled yet by the guideline and supplement the guideline accordingly.

Finally, we need to implement missing top actions dropdown and compose them according to the guideline.

3 User Interface Modifications

3.1 List of Affected Views

• Start page of all repository objects (except Poll)

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

none

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 or processed to implement this feature. We only add already existing functions like "Add to Favourites" to the dropdown or remove functions from it that do not belong there.

6 Security

No security relevant changes

7 Contact

• Author of the Request: Kunkel, Matthias [mkunkel]
• 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

Tödt, Alexandra [atoedt]: I welcome the streamlining. However from an accessibility perspective I would recommend to move the top actions down quite a bit: They lie in the line of tabbing very early, this communicates a lot of meaning and importance. The top actions typically do not carry a lot of meaning and importance. They mostly offer annotational  services, second tier functionality. Please move the top actions away from the top and out of the tabbing line. 

Kunkel, Matthias [mkunkel], 25 NOV 2024: Many thanks for this hint, Alexandra. What would be a good position in your opinion? Would you place them between headline (of the object) and the tabs (in a new row so to say)? Or even under the tabs?

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