Page Editor » Internal Link to parent object

1 Initial Problem

In ILIAS objects it is often needed to link the parent object in order to navigate to the next step, e.g. navigate from a Learning Module ILIAS to the parent Course. For scenarios where the parent object always should be visited, because this object shows the correct order of the learning content or specific information belonging to the objects, this is linking to the parent object is mandatory.

At the moment, this is possible by using an internal link, manually choosing the parent object.

Problem: When copying the whole container object or just the content with the learning content, the internal link remains unchanged and still links to the orginal course. It then has to be changed manually.

2 Conceptual Summary

This Feature Request introduces a new type "Parent Object" for Internal Links at the ILIAS Page Editor. This Internal Link has no selection - it just always links to the parent object. Only at the root of the Repository this is not possible.

The new Link type checks the parent object at the runtime (loading of the page) and links it. This should be possible for all objects except the root of the repository.

This would strongly simplify the creation of learning processes within container objects.

3 User Interface Modifications

3.1 List of Affected Views

3.2 User Interface Details

3.2.1 Modal for Internal Links

The Modal for Internal Links gets a new option "Parent Object". After choosing this option, there is no further selection possible. Therefore there has to be a button "Create Link" in order to create the link and close the modal.

This is the same way when e.g. creating a Link type "File/Document".

3.2.2 View of the Internal Link at the text element

Analog to the other Internal Links, the Parent Object Link is shown, when editing the text element. The parameter is always "1".

This is the same way when linking the root object of the repository.

3.3 New User Interface Concepts

No new User Interface Concepts needed

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 Additional Information

4.1 Involved Authorities

If this request is related to multiple components, please list both authorities for all related components.

4.2 Technical Aspects

{ Necessary technical information have to be provided here, e.g. dependencies on other ILIAS components, necessary modifications in general services/architecture, potential security or performance issues. }

4.3 Privacy

No personal data used

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

4.5 Contact

Person to be contacted in case of questions about the feature or for funding offers: Lowe, Simon [simon.lowe]

4.6 Funding

Funding status and funding parties are listed in the block 'Status of Feature' in the right column of this page.

If you are interested to give funding for this feature, please get into contact with the person mentioned above as 'Contact'.

5 Discussion

6 Implementation

Feature has been implemented by {Please add related profile link of this person}

6.1 Description and Screenshots

{ Description of the final implementation and screenshots if possible. }

6.2 Test Cases

Test cases completed at {date} by {user}

6.3 Privacy

Information in privacy.md of component: updated at {date} by {user} | no change required

6.4 Approval

Approved at {date} by {user}.