Feature Wiki

Information about planned and released features

Tabs

IRSS: Migrate Tile-View-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).

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 tile images are stored in WEBROOT/data/CLIENT/obj_data/tile_image so far. In ILIAS 9, these are to be moved to the ILIAS Resource Storage Service. 

2 Conceptual Summary

With a migration, the existing tile images are moved from the previous location to the IRSS. Access to the images must be abstracted so that both variants work during the release until the migration has been performed. With ILIAS 10 the abstraction can be removed.
In addition to migrating the existing files, the processing of the newly uploaded tile images must be adapted so that they are stored directly in the IRSS.
A new consumer is needed for the IRSS, who can also delegate the checking of the images to the WebAccessChecker and thus quickly deliver files based on a token.
Optionally, the tile image form can be changed to the new UI form. 

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

{ 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

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]