Feature Wiki

Information about planned and released features

Tabs

Communicate Workload Estimate in Courses

1 Initial Problem

Users do not get information how long an assignment or activity will take them to complete.

Current Implementation in ILIAS 9
Model for new suggestion in Learning Objective Course: Form with workflow triggering new subtabs

2 Conceptual Summary

For the objects in a course the associated workload should be communicated.

  • The workload is to be entered in the Learning Progress-tab.
  • The workload is entered as HH:SS. 
  • The workload is displayed in the List GUI of the Content tab.

3 User Interface Modifications

3.1 List of Affected Views

  • Course > Learning Progress 
  • Course > Content

3.2 User Interface Details

Form stays as it is

Status is Determined by a Collection of Items

Once "Status is Determined by a Collection of Items", the table is shown in a new sub-tab
Bulk-Actions open a form offereing checkboxes for all Objects

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}

Privacy

Information in privacy.md of component: updated on {date} by {user} | no change required

Approval

Approved at {date} by {user}.

Last edited: 26. Jul 2024, 17:18, Tödt, Alexandra [atoedt]