Feature Wiki

Information about planned and released features

Tabs

Usability Improvement Sessions

1 Initial Problem

Adding a new session differs greatly from adding other objects:

  • The accordion "Option1: New Session" comprises a not more than the average Title, Description, Type. 
  • Users are not taken to the Settings tab after creating the session as they are in all other objects. 

2 Conceptual Summary

{ Please add a brief summary on how you would like the problem to be solved. }

3 User Interface Modifications

3.1 List of Affected Views

  • Add new item > Session > Option 1: New Session
  • Session > Settings 

3.2 User Interface Details

More normal and vastly shortend create accordion
first sub-tab greatly shortened
new sub-tab strictly derived from course model

3.3 New User Interface Concepts

{ If the proposal introduces any completely new user interface elements, you might consult UI Kitchen Sink in order to find the necessary information to propose new UI-Concepts. Note that any maintainer might gladly assist you with this. }

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: {Please add your name.}
  • 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: 24. Oct 2022, 09:04, Tödt, Alexandra [atoedt]