Integration of CampusConnect course link resolver into goto.php

1 Initial Problem

The ECS Interface/CampusConnect is not only able to share course links (and other objects) between ILIAS installations (as well as Stud.IP and Moodle) but can also facilitate the integration of ILIAS with a campus management system (like eg. HIS LSF or CAMPUSonline).

This means courses (not course links!) are created from the campus management system (CMS). We think it makes sense to also provide a way to refer from the CMS course to the associated ILIAS course.

The easies way is a link resolver that takes the CMS course ID and looks up the matching ILIAS course ID. This way no information needs to flow back from ILIAS to the CMS after course creation. (In our experience it would is notoriously hard to get such a piece of information back into a CMS from the outside.)

2 Conceptual Summary

For ILIAS 5.2 we've already built our own link resolver that provides the desired functionality (thanks to Pascal Grube!):

https://github.com/TIK-NFL/ILIAS/blob/release_5-2/ecsredi.php

Since the ECS Interface is part of ILIAS’ core we would like to see this resolver capability integrated in to ILIAS’ standard goto.php, too. It would in our opinion be the most fitting place.

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, please provide a link to separate feature wiki entries for each of them according to the kitchen sink template.}

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: Bogen, Christian [bogen]
• 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.

• Universität Stuttgart

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