Streamline Object Properties

This request is part of the transfer of container objects to standard listing panels. Transfer Repository Objects to KS Items gives an overview of all requirements for the transfer of container objects.

1 Initial Problem

{ Please give a brief description of the problem you want to be solved. }

2 Conceptual Summary

There are some properties that are only displayed to certain users (e.g. type or status). In a first implementation these properties can be converted into normal key/value pairs. But maybe we can find another solution for such properties, so that objects in lists are always displayed the same way.

Related Conceptual UI Discussion

• PR UI Framework doc: UX Guide for properties and actions on repository objects

Related Feature Requests and Issues

• Presentation of Items WITHOUT Read-Permission
• Results of collecting Actions and Properties of Repository Objects

Screenshots

Needs to be discussed

- How do we deal with the properties? What can be represented as a property?
- How do we want "show previous" or "show next" actions to be displayed in panels?
- How do we deal with properties that are only displayed a certain role? E.g. Type: Learning Module, Status: Offline.
- How do we deal with "personal properties"? E.g. Tags, Notes

* Status sollte immer rollenabhängig sein, z.B. Online/ Offline ODER Typ (werden nur Admins angezeigt)
* persönliches hängt am Benutzeraccount, z.B. Notizen, Tag (?je nach Einstellung?)

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: Zenzen, Enrico [ezenzen]
• Maintainer: Killing, Alexander [alex], Meyer, Stefan [smeyer]
• 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] 11 AUG 2021: 
With ILIAS 6, the standard listing panels were introduced on the dashboard.
Since various properties that previously existed on the personal desktop were missing from the dashboard, they became available again with adjustments based on mantis report #30747. I still consider the adjustments to be correct and necessary.
Complete key-value pairs are not available for all properties, which is why report #30966 was created. There is a similar situation with other objects, such as the file.

Please have a look at the collection under Results of collecting Actions and Properties of Repository Objects. 
There may have been changes since 5.4. One known one is the key-value-pair on file migration.

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