Presentation of Items with preconditions

1 Initial Problem

Preconditions are displayed as a property in the ListGUI.

• Preconditions that need to be fulfilled to access this object: » Show

If the user clicks on Show, all preconditions will be displayed in a kind of accordion. Due to the way the object is displayed, many users do not realize that you must edit the preconditions in order to open or edit the object. While technically users get all information needed, but I get no specific visual cue. It should be clear that the object cannot be processed until the preconditions are fulfilled.

2 Conceptual Summary

There are different approaches to visually strengthen the concept of preconditions. All options are listed and described below. The options have been elaborated for both tile and list view. 

2.1 Option 1 - Padlock icon in front of title

An outlined black padlock is displayed in front oder behind of the objects title. The icon is already part of the Kitchen Sink.

• KS » Symbol » Icon » Standard » "peusr - User"

2.2 Option 2 - Padlock icon in front of title and disabled object icon

An outlined black padlock is displayed in front oder behind of the objects title. The object icon is displayed as disabled icon. Also the possibility to disable icons is already integrated in the KS. 

• KS » Symbol » Icon » Standard » "peusr - User"
• KS » Symbol » Icon » Standard »  Example 2: Disabled icon

For this option, the tile view must be customized, here the option to disable a card image does not yet exist. 

2.3 Option 3: Overlay Image

Icon/Tile of ListGUI-object is layerd with a 50%-black-box AND an outlined white padlock (KS » Symbol » Icon » Standard » "peusr - User") on that layer.

When the new catalog view is implemented, the preconditions could be displayed there as follows:

Mockup: (new) catalogue view

3 User Interface Modifications

3.1 List of Affected Views

• ListGUI

3.2 User Interface Details

See Conceptual Summary.

3.3 New User Interface Concepts

KS-element "peusr - User" (KS » Symbol » Icon » Standard » "peusr - User") should be used to represent if you cannot access an object. 
Therefore it needed to be replaced on tile/icon or in front of the title.

Important: for Screenreaders it must be able to inform the users that they cannot access.

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

{ 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: Tödt, Alexandra [atoedt], Seibt, Alina [alina.seibt], Zenzen, Enrico [ezenzen]
  
• Maintainer: Meyer, Stefan [smeyer]
• 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}.