Consuming LTI in Repository – Extension

Feature request is related to Consuming LTI in Repository – Basic and contains extended features for ILIAS as LTI consumer.

1 Initial Problem

{Please give a brief description of the problem you want to be solved.}

2 Conceptual Summary

Migration of exisiting functionality in plugin

• (b) Templates for launch URLs, launch pages or embedded HTML: An external content may be launched in a separate window with a configured link, in a new page based on a the configured page template or embedded to the content tab of the repository object based on a configured HTML template.
• Provision of selected user and context information, calculations and encodings in the template processing.

Extension of existing functionality

• Additionally to repository objects, external content types should also be provided as page components in the ILIAS editor. (own feature request, tbd)
• Restriction of content types to selected categories within the repository, supporting e.g. faculty specific video servers that is only available in a sub-part of the repository. (needs to be clarified)
• Slot for proprietary functions in a type definition to support exotic encodings or authentications. (option for second implementation step)
• Ressource files (e.g. css, images, js) for launch pages or enbedding templates. (required - needs to be supported)
• Export and import of type definitions as configuration packs including the definition, language and resource files and proprietary functions. Functions (php code) may only be activated after review and confirmation by the ILIAS admin. (option for second implementation step. PHP code should not be imported due to security reasons)

3 User Interface Modifications

3.1 List of Affected Views

{Please list 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.}

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 Contact

• Author of the Request: {Please add your name.}
• Maintainer: {Please add your name before applying for an initial workshop or a Jour Fixe meeting.}
• Implementation of the feature is done by: {The maintainer must add the name of the implementing developer.}

6 Funding

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

• …

7 Discussion

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