Streamline permalink position

1 Initial Problem

In some objects the position of the permanent link is still different and should be streamlined.

Further request

The position of the permanent links is different and should be streamlined.

Current Situation

Repository:
- after the content box
- before the footer

Wiki:
- in the content box
- before comments/notes
- after content box follows footer

Info Page:
- within the info page in section "additional information"
- comments notes follow in the content box
- footer follows afterwards

Due to Design Revision of ILIAS for Release 5.0 a lot of streamlining has already been made. The Permanent Link has been moved to the footer - except for the Info Page where it is still displayed in section "Additional Information" and not in the footer. This change could be done with a Revision of Info Page or separately.

2 Conceptual Summary

In most of ILIAS objects you can find the permanent link in the footer. However there are still some objects/views missing. In these the permanent link should also be displayed in the footer.

These are:

• info pages of all object types
• excercise 
• chat room
• individual assessment
• media pool

3 User Interface Modifications

3.1 List of Affected Views

• info page (of any object type)
• exercise > assignment > view
• chat room > view (via Usability Bug by M. Jansen: https://mantis.ilias.de/view.php?id=32607) 
• individual assessment > participants
• media pool > content > all subtabs (at least Folders and maybe also All Media Objects, Media Subtitles)

3.2 User Interface Details

3.3 New User Interface Concepts

none

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: Seibt, Alina [alina.seibt]
• Maintainer: Killing, Alexander [alex], Klees, Richard [rklees] for individual assessment, Jansen, Michael [mjansen] for chat room
• Implementation of the feature is done by: {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.

• …

9 Discussion

Samoila, Oliver [oliver.samoila], 08 MAR 2024 : Feature is already implemented.

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