Setting: File Visible for Participant

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

When creating records for individual participants, examiners have the option (or are required
to do so) of uploading files into that record. At present, examiners have the option to
determine whether or not the uploaded file should be visible via the participant record for each
individual record they create. 

2 Conceptual Summary

To streamline the process, this option should be elevated to the
level of each Individual Assessment object. Consequently, Individual Assessments will have the
option "Files Visible for Participants" in their Settings, located directly under the option "Record
file required". If that option is selected for an Individual Assessment, all files uploaded via that
Individual Assessment object will (or will not) be visible to the participants.
A migration will be carried out to elevate the option from individual records to the object for
existing objects. If a record in the object does not have the option set, the complete individual
assessment will not acquire it. Conversely, if the option is set for all records, it will be set. In the 
Individual Assessment: Use in High Volume Scenarios 15.10.2024 Seite 5 von 10
event that the Individual Assessment object contains records with one or the other, the object
will be listed via the Makro:codestatus command, allowing measures to be taken before the
migration is initiated.

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