Generate recommended content from competence profiles

1 Initial Problem

In competence profiles are used in ILIAS to suggest competence targets to users. Based on the competence targets, users are proposed learning materials. If users complete the suggested materials, they achieve their competence target and fulfill the competence profile.

Since users are often assigned multiple competence profiles, it is difficult to identify the learning materials to work on next. Currently, there is no  access to competence profiles. Users have to open each profile and find the corresponding learning material. 

2 Conceptual Summary

Learning materials for target achievement should be displayed as Recommended Content on the dashboard.

• For each competence profile that has been assigned to a user, only the learning material that is to be worked on next is displayed.
• Only learning materials that lead to the achievement of the competence target are displayed.
• Next is defined by the order of competences within a competencs profile and then by the order of learning materials for target achievement. 
• A property shows from which competence profile the learning materials are suggested.
• If a competency target is reached, the learning material of this competence is no longer displayed on the dashboard. Instead, the learning material for the next competence in the competence profile is displayed as Recommended Content. This is repeated until a competence profile has been completely fulfilled (all competence target has been fulfilled).

Since there is no separate settings screen for Recommended Content, the setting is placed in Competence Management.

Maybe we should discuss if the Recommended Content is not only displayed in roles, but has its own administration or is displayed under Administration » Dashboard.

3 User Interface Modifications

3.1 List of Affected Views

• Administration » Competence Management » Settings
• Dashboard » Recommended Content

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

{ 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: Zenzen, Enrico [ezenzen], Spirou, Ilias [ispirou]
• Maintainer: Famula, Thomas [tfamula]
• 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}.