Show availability and preconditions in modal

1 Initial Problem

In the ListGUI preconditions are presented neither useful nor attractive. If the list of preconditions and porperties of ListGUI-Items gets longer, it'll become confusing for users. To solve that and to purify the ListGUI, the properties availability and precondition should be presented in a modal.

2 Conceptual Summary

As an user you cannot see in ListGUI if there is an availability or precondition set on the object. However if there is a reason why you cannot open the object (due to wrong period of time or not fulfilled preconditions) a modal opens and explains the reason. From here you can directly access the preconditional object (if set) or just exit the modal.

If you have access to the object (for example correct period of time or you've already fulfilled the preconditions/there are none) you directly open the object by clicking on ListGUI-element as before. Now you can only get to know about the properties availability and preconditions on the info page of the object (not in ListGUI).

3 User Interface Modifications

3.1 List of Affected Views

• ListGUI

3.2 User Interface Details

need to be discussed:

• if my precondition object (1) has set preconditions (2) aswell (here: you try to open "such a nice course" but you have to pass the course "Lineare Algebra" (1) - but to access this course you first have to pass another object (2), p.e. a test) - what happens after clicking on the precondtion object (1) in the modal? 
  • the info tab (1) should be loaded - here I can see what preconditions this object has set (2)
  • proposal 2: after clicking on the precondition object (1) a new modal opens with information about the preconditions of this object
    • this would be a modal in a modal - should probably be NOT an option
• what is the trigger? 
  • tile/icon and title should open the modal, not the whole div
  • if you open action menu » info the info tab opens without showing modal
  • if you open action menu » join (i.e. course/group) the modal opens instead, if you cannot access due to availability/preconditions

3.3 New User Interface Concepts

A new modal is needed or the interruptive modal needs to be improved:

interruptive modal rule 3: 
Interruptive modals MUST contain a primary button continuing the action that initiated the modal (e.g. Delete the item) on the left side of the footer of the modal and a default button canceling the action on the right side of the footer.
This rule doesn't fit to a precondition modal, because there is no primary button needed. Furthermore the modal SHOULD be allowed to let the user get forward (i.e. to a precondition object).

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: Seibt, Alina [alina.seibt]
• 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}.