Setting internal Redirect-Links in Test

1 Initial Problem

When exporting a course with a test set to Re-Direct the original input is taken along. For adaptive courses it is not helpful. 

There are two cases:

1. Redirect to external links there is no need for change.
2. Redirect to an object in ILIAS should be a proper internal link. 

The more common use case in contrast might be the need for setting internal links in test. this is mandatory for setting up an adaptive course.    

The problem:

The momentary workflow of "setting internal redirect-links" (Test) is to  copy&paste EVERY destination link Test-Redirect.  As it is one manual input field / input method for internal and external links it is not featured to update redirect-links while Export.

For complex and  basic  scenarios as well, this is a major problem as this results in a huge workload for resetting or delivering a new course. 

Aim: Better input method for internal "URLs" (objectIDs) of destination page (internal redirect after finishing Test)

The setting of "External links" remains as it is now  (manual input field).

No more manual input for "Internal Links".

This would offer the ability of automatically updating Test configuraiotn (Redirect-Links)  when a Test is exported. 

The actual workflow for Setting internal Links (in Test) resulting in:

1. better input workflow and system usability
2. feature: referencing method for Redirect-Link (in Test) and thereby the ability to automatically update didactic dependencies e.g. redirect-link to another object (reference by ObjectID)
3. enabling educators to offer (adaptive) templates

2 Conceptual Summary

The redirect Link input should have two parts ( 3 options):

1. No Redirect
2. "External Link": Input for external Link
3. "Object in ILIAS": Repository Picker to select the object the internal link points to. 

3 User Interface Modifications

3.1 List of Affected Views

• changed input method for Re-Direct setting in the object Test 
  • settings of object Test: horizontal settings menu ("Reiter Einstellungen"), unten: "Weiterleitung"
• add new option "select target object" (Rep. Picker) for internal links
• the option for manual input "external links"  remains

3.2 User Interface Details

3.3 New User Interface Concepts

Test > Settings

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: Simon Yadel (ILIAS.nrw / MIau.nrw), Alexandra Tödt (leifos)
• Maintainer: 
• Implementation of the feature is done by: t.b.a {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.

• DHBW can possibly contribute to funding
• …

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