Improve File Upload in Mediacasts

1 Initial Problem

The file upload in mediacasts is very complicated. Users have to fill out a very long form before they can create a media object. ILIAS does not recognize the file type, i.e. users are also shown information / input fields for video files during the upload of an image file. However, input fields such as "Additional Video File for Portable Devices" are not relevant for image files.

2 Conceptual Summary

The file upload in Mediacast is to be simplified and extended:

• Simplify File-Upload in Mediacasts
• Introduction of Multiple Upload in Mediacasts

2.1 Simplify File-Upload in Mediacasts

Users only need to enter a minimum of relevant information when uploading files. Additional information can be added by the user afterwards by editing the media object. This has the advantage that the file upload is simplified and users do not see any information or input fields that are not necessary for the file type they want to upload. When users edit a media object, ILIAS already knows the file type and displays the form for a video format, for example.

Upload Steps

2.2 Introduction of Multiple Upload in Mediacasts

The new upload dialog uses the KS element "Standard File Dropzone" and supports multiple upload of files.

3 User Interface Modifications

3.1 List of Affected Views

• Mediacast >> Add Media Object

3.2 User Interface Details

The User Interface Details are displayed in the respective subchapters of the Conceptual Summary.

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 Contact

• Author of the Request: Zenzen, Enrico [ezenzen]
  
• Maintainer: Killing, Alexander [alex]
• 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}.