Aggregation by Profiles 

1 Initial Problem

Aggregation of competence data is currently not available. 
Future aggregation requires a locus of control, where the rules for aggregation can be defined. 

2 Conceptual Summary

• Profiles offer Settings allowing to set the time frame of aggregation.
• Profiles list the objects that feed into aggregation. 
• Profile state the target value.

Competence results are aggregated within their type of formation

1. Self-Evaluation is NEVER aggregated. Instead of an aggregated value the last record is dislpayed. The last record could be either generated on Personal Desktop or in a 360° Feedback Survey. 
2. Learning Progress  is NEVER aggregated. Instead of an aggregated value the last record is dislpayed. The last record is generated by completing an object.  New Type
3. Appriasal IS aggregated. Records that feed into the aggregation come either from Courses or 360° Feedback Surveys.
4. Measurement IS aggregated. Records of Tests feed into the aggregation.

Profile in Kurs
Tab Competences

• Button in Toolbar „Add Profile“
  • Assign Users & crobjob?
  • Non-editable Profile

• Object List
  • Objects with activated competence service AND feeding into any one competence of this profile
• Settings: Time settings

• Stamp in Profile

Profile in Kurs
Tab Competences

• Button in Toolbar „Add Profile“
  • Assign Users & crobjob?
  • Non-editable Profile

• Object List
  • Objects with activated competence service AND feeding into any one competence of this profile
• Settings: Time settings

• Stamp in Profile

3 User Interface Modifications

3.1 List of Affected Views

{Please list all views (screens) of ILIAS that should be modified, newly introduced or removed.}

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

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

6 Funding

If you are interest in funding this feature, please add your name and institution to this list.

• …

7 Discussion

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