Feature Wiki

Information about planned and released features

Tabs

Using a remote LTI-Ressource Repository

1 Initial Problem

Only a local xml with LTI Ressourse information can be used for importing as batch process. 

2 Conceptual Summary

A third Call-to-action Button should be implemented in the LTI-adminsitration Area for using a external path for batch import Ressources.

3 User Interface Modifications

3.1 List of Affected Views

  • Mockup is following ...

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

The xml of LTI-Ressources contains path and secrets, which can be used to login to a remote provider system. A transport encryption (TLS/SSL) should be used.

7 Contact

8 Funding

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

9 Discussion

Maybe using a REST-API could be a more convenient way

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: 31. Mar 2022, 16:36, Vorkauf, Klaus [KlausVorkauf]