Feature Wiki

Information about planned and released features

Tabs

Internal links to Data Collection entries

1 Initial Problem

There's currently no possibility to internal link to a Data Collection entry. As a work-around you have to use an external link, where the detailed view of the entry will be opened in a new tab or window, although it is a link to an internal ressource.

Example: A Plugin Data Collection entry

2 Conceptual Summary

Internal links to Data Collection entries should be supported in the same manner as internal links to Glossary terms.

Precondition: The detailed view must be activated for the corresponding table.

3 User Interface Modifications

3.1 List of Affected Views

  • … { Please list titles of 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, you might consult UI Kitchen Sink in order to find the necessary information to propose new UI-Concepts. Note that any maintainer might gladly assist you with this. }

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: Hilbert, Mirco [mirco.hilbert]
  • 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.}

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], 28 August 2024: In general, an internal link to the specific data record of a data collection would be useful.

However, several questions remain: 
Where is this offered? I assume in the footer in the single view, as it is currently also available for the example in use as an external link.
This assumes that the person who inserts the internal link somewhere has access to exactly this single view and that the assumption is correct that the person who is to call up the internal link also has access to it. But what should happen if the person does not have access to a single view or even to several single views due to their authorisations via role? 
If there are several possible single views, it should therefore be clear in advance which single view is to be called up and made selectable accordingly in the context of an internal link. This is not a trivial task.
The use of the external link hides the entire question of whether access is granted. This simplifies handling, but of course it is also possible to want to call up a data collection record but then not be able to do so.

I'm not sure whether we will really improve data collection with such a development.

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

Last edited: 28. Aug 2024, 21:20, Samoila, Oliver [oliver.samoila]