New Object: Individual Assessment Report

If you need any help in filling out this wiki page, please visit our ILIAS Community FAQ. And please complete the metadata information in the right column after having created the page.

1 Initial Problem

{ Please give a brief description of the problem you want to be solved. }

2 Conceptual Summary

To provide the desired overview, a new repository object, "Individual Assessment Report", shall
be added. The object can be configured to provide an overview in one of two ways:

• The overall Individual Assessment in the system can be viewed as a global overview.
• The overview can be configured to show all Individual Assessments in or below the
  repository node where the report object is located. This is referred to as a local
  overview.

The report then displays information for all Individual Assessments in which the current user is
a participant. The results will be displayed as a presentation table with suitable view controls,
allowing users to quickly access all their results from Individual Assessments in the configured
space. The report will also show results from Individual Assessments that are not accessible for
the user from an RBAC perspective. This provides an independent view of Individual
Assessment results that is not bound to the objects where the reports have actually been
created.

3 User Interface Modifications

3.1 List of Affected Views

• … { Please list titles of 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. }

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 data point, provide a short explanation of why it is necessary to use that data. You may consult the Privacy Clinic for questions regarding the legality, minimization, or appropiate use of personal data in compliance with applicable privacy regulations such as GDPR. }

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