Feature Wiki

Information about planned and released features

Tabs

Revise File Upload Question Creation Process

Page Overview

[Hide]

This feature request is part of (Project) Revision of Test Question Creation.

1 Initial Problem

The set of questions available has grown organically over many years. There are redundancies and inconsistencies and the forms to edit the questions are based on a lot of custom code based on the legacy forms featuring many unique concepts, like forms that are rendered by javascript on the client.

There is a clear need to bring this process back in alignment with the current way of doing things in ILIAS, to remove redundancies, and rectify inconsistencies.

2 Conceptual Summary

  • This Feature Request follows the guidelines set by Revision of ILIAS Test Question Creation Process and fleshed out for the anwser form type "Cloze" in Revise Cloze, Long Menu, Numeric, and Text Subset Question Creation Process.
  • This request is only concerned with question creation and structure. The form to answer a question will basically stay as is and only undergo some minor tweaks.
  • The form to set up the answer form will offer a maximum of four inputs:
    • A numeric input "Maximum File Size" that can be left empty to fall back on the default. 
    • A tag input "Allowed File Extensions" only allowing to enter extensions that are also allowed to the user on the platform.
    • If marking is required in the current context, a required numeric input "Points".
    • If marking is required in the current context, a checkbox "Completed by Submission".
  • The "Maximum File Size" will be changed from a value in Bytes to a Value in MB. We do not believe that a value in Bytes makes much sense today. We use decimal MBs as they are also used in the File Service. As in the File Service we will only allow integer values.
  • No additional form steps are needed.
  • The overview page will only show the basic form properties in a panel with a button to edit them. Consistency is rated higher than the oportunity to edit the properties directly.
  • The feedback options are kept exactly as today and only offer options to provide feedback texts for the case the participant has given the best possible response or not. It is to be noted that the feedback does in a first step not depend on the response of the participant, as there is no automatic marking.

3 User Interface Modifications

3.1 List of Affected Views

  • All views of `assFileUploadGUI`

3.2 User Interface Details

The process to create the answer form consists of only one step that contains the inputs "Maximum File Size", "Allowed File Extensions", and if marking is required in the current context, an input for points and one to assign points to users upon submission labeled "Completed by Submission".
The overview page of the answer form shows only a panel labeled "Basic Answer Form Properties" showing the properties as they were set. The information for Points and completion by submission is only shown if marking is required in the current context.

3.3 New User Interface Concepts

None

3.4 Accessibility Implications

The forms to create questions are based on legacy-ui-forms with a lot of custom inputs that have a huge amount of accessibility issues. By moving these forms to KS-Forms a lot of the issues should be resolved. Additionally it will be easier to address future accessibility issue.

4 Additional Information

4.1 Involved Authorities

If this request is related to multiple components, please list both authorities for all related components.

4.2 Technical Aspects

Technical aspects of this request are provided as part of the project. See: (Project) Revision of Test Question Creation .

4.3 Privacy

This feature request doesn't change the data that is collected and also doesn't change how it is presented. It clarifies the storage of answers by users answering questions, by doing so it will improve the understandability and the structure of the data thus making it easier to control the data's lifecycle.

4.4 Security

By moving to KS-Forms and restructuring and clarify the storage of data, the data will be easier to control and user inputs in the KS-Forms will be more consistently validated and sanitized on output.

4.5 Contact

Person to be contacted in case of questions about the feature or for funding offers: Strassner, Denis [dstrassner]

4.6 Funding

Funding status and funding parties are listed in the block 'Status of Feature' in the right column of this page.

If you are interested to give funding for this feature, please get into contact with the person mentioned above as 'Contact'.

5 Discussion

6 Implementation

Feature has been implemented by {Please add related profile link of this person}

6.1 Description and Screenshots

{ Description of the final implementation and screenshots if possible. }

6.2 Test Cases

Test cases completed at {date} by {user}

  • {Test case number linked to Testrail} : {test case title}

6.3 Privacy

Information in privacy.md of component: updated at {date} by {user} | no change required

6.4 Approval

Approved at {date} by {user}.

Full Screen

Last edited: 22. Jun 2026, 09:15, Kergomard, Stephan [skergomard]