Show Advanced KnowledgeHide Advanced Knowledge

View and Manage Materials in the same place

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

1 Initial Problem

The "Info" tab of a session displays both general information about the object (e.g. owner, permanent link,...), general and user-specific metadata and materials.

This leads to the following three problems

• In the "Info" tab, meta-information is therefore mixed with further content.
• In addition, the display and management of materials is placed in two different locations: Users can see the materials in the "Info" tab, but they must add and remove them in a separate "Materials" tab.
• Users can be confused because the session offers materials on the "Info" tab, but in other objects these are found under "Content".

2 Conceptual Summary

Session materials should be separated from other meta-information. For this purpose, a separate "Content" tab is to be created.

Tab Ordering
The session would therefore include the following registers:

1. Content
2. Info
3. Settings
4. Edit Participants
5. Learning Progress
6. Metadata
7. Export
8. Permissions

Tab Content
???


Landing Page
If a user clicks on a session title, or if the session is opened via a calendar appointment, the user always ends up on the "Content" page.

evt. in Kombination mit:

• Display Metadata in Content-Sidebar
• Making Operating Information of the Info-tab and Info-Action in Lists permission-sensitive

3 User Interface Modifications

3.1 List of Affected Views

• Session > Info
• Session > Materials

3.2 User Interface Details

Set, ordering and contents of tabs is changed as explained above.

3.3 New User Interface Concepts

No new UI concepts are introduced.

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], Amstutz, Timon [amstutz], 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.

• Universität Bern

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