Show Advanced KnowledgeHide Advanced Knowledge

Streamline Labels for creating and adding new threads, posts and answers

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

1 Initial Problem

It is important that a user understands the hierarchies and interdependencies in a system. The forum contains different elements (forum, thread, posting, answer), which must be kept apart as a user. If the labels are not handy, it will be difficult to imagine what the user is doing right now.

The labels in the forum are currently causing users to be confused about what they are doing when clicking on a button. The different labels for the individual elements in the forum show how difficult it is:

Level	English	German
Forum	Add Forum	Forum anlegen
Thread	Create	Erstellen
Posting	1. Add Posting	Neuer Beitrag
	2. Create	Erstellen
Antwort	1. Reply	Antworten
	2. Save	Speichern

For the user it is visually hardly visible what the difference is between "Add Posting" and "Reply". It only has to do with the fact

• that "Reply" displays the reply directly below the post (visible in the tree on the left) and
• that in the "Add Posting" the post at the end or at the beginning (depending on the sorting of the forum thread).

The area is called "Your Reply" for both button variants, which is an additional sign for the user that it doesn't matter much whether you "Create" a post or "Reply" to a post. Therefore the different naming of the buttons is more confusing than helpful when adding a posting.

2 Conceptual Summary

• Reduce complexity
• (Forumsbeitrag) Erstellen --> Posten oder Senden

3 User Interface Modifications

3.1 List of Affected Views

• Container > Add New Object > Forum
• Forum > Threads
• Forum > New Threads
• Forum > Threads (open a thread) > Sort by posts / sort by dates
• Forum > Threads (open a thread) > Sort by posts / sort by dates > Reply or Add Posting

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