Migrate HTML Export To IRSS And New Zip Process

1 Initial Problem

With the introduction of the IRSS for media objects and a new ZIP API in ILIAS the HTML process of content components needs to be revised.

2 Conceptual Summary

The HTML export process of the following content modules and services will be revised to use IRSS and the new ZIP API.

• Learning Modules
• Glossaries
• COPage Component
• Media Objects
• Content Styles
• Wiki
• Blog
• Portfolio

All resources (media objects, CSS, JS) will be stored in a zip IRSS container using the stream based API, avoiding any other file operations. The resulting zip will then most probably be stored as a simple IRSS resource in a collection.

3 User Interface Modifications

3.1 List of Affected Views

No user interface changes.

3.2 User Interface Details

No user interface changes.

3.3 New User Interface Concepts

No user interface changes.

3.4 Accessibility Implications

No accessibility implications.

4 Technical Information

No technical issues.

5 Privacy

This is a refactoring that should not affect any privacy issues.

6 Security

No security issues.

7 Contact

• Author of the Request: Killing, Alexander [alex]
• Maintainer: Killing, Alexander [alex]
• Implementation of the feature is done by: tbd

8 Funding

Killing, Alexander [alex], 7 May 2024: A rough estimation to implement this is aorund 12.000 Euro. We are looking for quick funding, since the old file handling is declared legacy for ILIAS 10.

If you are interest in funding this feature, please add your name and institution to this list.

• …

9 Discussion

JourFixe, ILIAS [jourfixe], 27 MAY 2024: We highly appreciate this suggestion and schedule the migration to IRSS and the new zip process for ILIAS 10. We ask all institutions and companies to partipate at funding for this important step as the legacy file service will be abandoned with ILIAS 10.

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