Activity Badges for Learning Objectives

1 Initial Problem

Activity badges in courses are currently only triggered by learning progress. In courses with learning objectives it would be a good option to motivate learners if a badge is awarded when a learning objective has been reached.

2 Conceptual Summary

• The already existing badge administration in courses is extended by a new type "Learning Objective (automatic)".
• The edit form of a badge of this type consists of:
  • Checkbox "Active"
  • Radio box selection "Learning Objective" (only existing learning objectives within this course are listed)
  • Text input "Description"
  • File upload "Image"
• Title of the badge is inherited from title of learning objective (and should not be changed to avoid confusion).
• Criteria of badge is inherited from threshold for reaching learning objective.

3 User Interface Modifications

3.1 List of Affected Views

• Course » Badges

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

none

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 Information

{ 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 Implications

{ 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: Kunkel, Matthias [mkunkel]
• 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.

• ILIAS-Verein

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}.