IRSS: Migrate SCORM-Modules to ContainerResources

1 Initial Problem

The SCORM modules are currently stored by the Legacy FileSystem Service and are located in the www-data directory, which is directly accessible from the Internet. The WbAccessChecker must therefore perform rights checks for these directories, which sometimes leads to performance problems

2 Conceptual Summary

The SCORM modules are now to be stored in the IRSS in ContainerResources. The modules are then delivered via the SignedDelivery mechanism of the FileDelivery Service.

3 User Interface Modifications

3.1 List of Affected Views

• Edit Content of SCORM-Modules

3.2 User Interface Details

This is implemented using the ContainerResourceGUI already available in ILIAS (see IRSS: Container-Resource User-interface):

3.3 New User Interface Concepts

None

3.4 Accessibility Implications

The use of existing UI components does not introduce any new implications for accessibility.

4 Technical Information

A migration moves the existing SCORM modules to the IRSS in a similar way to the HTML learning modules: https://github.com/ILIAS-eLearning/ILIAS/pull/7214

5 Privacy

No new personal data is collected or processed as a result of the implementation of the feature. 

6 Security

The implementation of the feature does not introduce any new attack vectors. there are no further special security-related considerations to be made.

7 Contact

• Author of the Request: Schmid, Fabian [fschmid]
• Maintainer: Schmid, Fabian [fschmid]
• Implementation of the feature is done by: sr.solutions

8 Funding

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

• Technische Hochschule OWL

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}

Privacy

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

Approval

Approved at {date} by {user}.