Display Metadata in Content-Sidebar

This feature request is a part of the Calendar Revision II.

1 Initial Problem

General and user-specific metadata are visible in "Info" tab of an object. If you have a "Content" tab in an object, this content tab is the main page where users stay. Important informations from the metadata aren't visible for these user (instead they click by chance on "Info" tab).

Certain metadata should be more visible in content tab of an object.

2 Conceptual Summary

In the metadata set settings, you can specify whether the metadata sets are displayed on the content page of the object.

In this case, they are displayed in the right sidebar of the content area (similar to the wiki page with metadata).

Concerns

• Custom Metadata or Custom Metadata Definition
• General Metadata (wie soll es für diese festgelegt werden können?)

3 User Interface Modifications

3.1 List of Affected Views

• Every objects with content tab and metadata (f.e. course, group, (session),...) > Content
• Object > Metadata 

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

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 Contact

• Author of the Request: Seiler, Yvonne [yvseiler], Universität Bern
• 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.}

6 Funding

If you are interest in funding this feature, please add your name and institution to this list.

• …

7 Discussion

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