Permanent-Link for Contacts, News, Badges, Mail

1 Initial Problem

Currently, there is no permanent or static link that allows users or third-party systems to directly reference the following pages/screens (marked in strong):

This limitation prevents users from:

Without a stable URL endpoint, there is no reliable way for users to return to those screens unless they navigate through the interface manually. This affects both usability and the integration potential of ILIAS in external workflows.

2 Conceptual Summary

To address this issue, the feature proposes the introduction of a permanent link to the listed screens. This link would be exposed in the ILIAS footer, making it easily accessible from anywhere in the system.

The link will:

This approach ensures a robust, user-friendly mechanism for referencing and sharing information in a consistent way across user sessions and system boundaries.

3 User Interface Modifications

3.1 List of Affected Views

3.2 User Interface Details

3.2.1 Contacts ›› My Contacts

Before

After

3.2.2 Contacts ›› Mailing Lists

Before

After

3.2.3 Contacts ›› My Courses

Before

After

3.2.4 Contacts ›› My Groups

Before

After

3.2.5 News

Before

After

3.2.6 Badges

Before

After

3.2.7 Mail ›› Folder

Before

After

3.2.8 Mail ›› Compose

Before

After

3.2.9 Mail ›› Read a Mail & ›› Reply to a Mail

For reading and replying a mail and a mail a Permanent-Link is technically provided. This link is not shown at the User-Interface.

This is to be used at the cronjob "New Mail Notifications" in the future.

3.3 New User Interface Concepts

No new User Interface Concepts needed

3.4 Accessibility Implications

No Accessbility Implications

4 Additional Information

4.1 Involved Authorities

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 new Personal Data used or stored

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: Samoila, Oliver [oliver.samoila]

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