Feature Wiki

Information about planned and released features

Tabs

IRSS: Migrate Exercise-Files to IRSS

This Feature-Request is part of the larger strategy to move all user-uploaded files to the ILIAS Resource Storage Service (see Project: ILIAS Resource Storage Service (IRSS)). Feature requests like this are spin-offs from IRSS: General Overview of Components to Migrate (ongoing) and are basically already approved, we just like to keep track of these.

There are two different approaches:
- Some components used ilObjFile in the past to store files. With ILIAS 7, Files from ilObjFile have been migrated and components using them communicate through a wrapper. These component now must be decoupled from ilObjFile and use the IRSS directly. 
- Some components stored their files on their own in the iliasdata or data Directory. These component should migrate their files to the IRSS using a Setup - Add migrate Command

1 Initial Problem

The exercise stores its files in different directories, which will be migrated to the ILIAS Resource Storage Service with ILIAS 9.

2 Conceptual Summary

The exercise uses files at various points, e.g. for submissions but also as additional files and sample solutions in the exercise units.

For each use of files a migration must be written here, which these files, which are stored so far in the following directories:

- WEBROOT/data/CLIENT/ilExercise/
- DATADIR/CLIENT/ilExercise/

It must be ensured that files can be downloaded even if the migrations have not yet been executed. Therefore, an abstract implementation for accessing the files is needed. With ILIAS 10 this abstraction can be removed.

All locations where new files are uploaded and processed must be rebuilt so that the files are newly stored directly in the IRSS.

Optionally, the forms should also be converted to the new UI inputs.

3 User Interface Modifications

3.1 List of Affected Views

  • none

3.2 User Interface Details

none

3.3 New User Interface Concepts

none

3.4 Accessibility Implications

none

4 Technical Information

none

5 Privacy

No new user-based data is stored as part of this refactoring.

6 Security

No new security-relevant changes based on this refactoring

7 Contact

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}

Approval

Approved at {date} by {user}.

Last edited: 18. Oct 2024, 15:53, Kunkel, Matthias [mkunkel]