Configurable Embedding Snippets for Embedding External Media

1 Initial Problem

It is currently not possible to embed media, e.g. videos, in page editor content without creating a page editor compoenent plugin to do that. Many universities run their own video platforms which provide embedding snipppets and ebdding links for publicly available content. Up until ILIAS 7 users were able to use these snippets in the page editor. This is not possible anymore.

2 Conceptual Summary

ILIAS should provide a way to globally configure (system admins) and embedding snippet with placeholders in it which is used, when users provide an URL to a media source on the configured platform.

Admistrators should be able to globally configure HTML snippets with placeholders for trusted platforms in teh central administzration of media objects.

Users should be able to use URLs that point to media on the trusted AND configured platforms, which is then parsed for the relevant video ID. The page editor then uses the preconfigured snippet, fils in the parsed media ID and renders the content on the page editor page.

3 User Interface Modifications

3.1 List of Affected Views

• … { Please list titles of all views (screens) of ILIAS that should be modified, newly introduced or removed. }

3.2 User Interface Details

{ For each of these views please list all user interface elements that should be modified, added or removed. Please provide the textual appearance of the UI elements and their interactive behaviour. }

3.3 New User Interface Concepts

{ If the proposal introduces any completely new user interface elements, you might consult UI Kitchen Sink in order to find the necessary information to propose new UI-Concepts. Note that any maintainer might gladly assist you with this. }

3.4 Accessibility Implications

{ If the proposal contains potential accessibility issues that are neither covered by existing UI components nor clarified by guidelines, please list them here. For every potential issue please either propose a solution or write down a short risk assessment about potential fallout if there would be no solution for the issue. }

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

{ Please list all personal data that will need to be stored or processed to implement this feature. For each date give a short explanation why it is necessary to use that date. }

6 Security

{ Does the feature include any special security relevant changes, e.g. the introducion of new endpoints or other new possible attack vectors. If yes, please explain these implications and include a commitment to deliver a written security concept as part of the feature development. This concept will need an additional approvement by the JourFixe. }

7 Contact

• Author of the Request: Glaubitz, Marko [mglaubitz]
• Maintainer: Killing, Alexander [alex]
• Implementation of the feature is done by: {The maintainer must add the name of the implementing developer.}

8 Funding

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

• Universität Freiburg

9 Discussion

2024-04-19 Mela, Alix [ILIAS_LM]
Only to be documented: there is a plugin development for external (iFrame) content ongoing from sr.solutions ag that goes in this direction

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