Show Advanced KnowledgeHide Advanced Knowledge

Introducing an Object Bar

1 Initial Problem

1. The concepts Tags, Notes and Comments are underrepresented and need a higher visibility at the objects. Oftentimes users overlook that these functions are available. Only after the first comments were made, users come up with the idea to click on the glyph (which is only then available) in order to become active themselves. Tags and comments are often noticed in the ListGUI in the repository, but not inside the object.
2. To make it more difficult, not all concepts are uniformly available for all repository objects. Streamlining to tags, notes and comments on almost all objects is handled by a separate FeatureRequest.
3. In addition to tags, comments and notes, a glyph is available next to the actions menu on object level, which indicates whether a notification/notification-type is activated. It is often assumed here that this is to be clicked. Unfortunately this is not the case. This problem is handled by the FeatureRequest Clickable Glyph for Notification Bell.
4. Actions such as "Place on Desktop" (5.4) or "Add to Favorites" (ILIAS 6) are hidden in the Actions menu.
5. Some actions are available, which do not have to be reached via the "inner" action menu. A general revision of the "outer" action menus is again processed in a separate request. This will follow here (Request missing at tht moment) (soon, hopefully ;) ) The collection of problem areas can already be viewed here Results of collecting Actions and Properties of Repository Objects.

2 Conceptual Summary

From these many "little things" the idea grew to revise the inner action menu in general - to exchange it for an existing uniform visual language.
In consideration of the requirements, which are known with ILIAS 6 and foreseeable for ILIAS 7, the process "Add to favorites" and "Recommend something" was added directly to the group of glyphs.
This results in a grouping:

• Tags
• Notes
• Comments
• Notifications
• Add to favorites
• Recommend something

(The topic Recommendation already implies that I can actively recommend something to others. This will certainly be a topic for ILIAS 7.)

3 User Interface Modifications

3.1 List of Affected Views

• All Tabs of almost all Repository Objects. (Exception for example: Item List)
  • See: Results of collecting Actions and Properties of Repository Objects »» Actions:TopActions - Sammlung - ILIAS 54 - 2019_10_08.xlsx »» Tab "Object Bar"
• All Objects in Personal Workspace.

3.2 User Interface Details

It is a draft.

• In the section above you can see the behavior in ILIAS 5.4  (Once without using Tags, Notes, Comments (T+N+C). Once with entries in the respective concepts.)
• Below the design for an ObjectBar (with and without entries in T+N+C)

• What happens when I click on the glyph?
  • If entries / selections are required, they should be able to be entered in modal dialogs.
  • The T+N+C concepts already work with modal dialogs.
  • Notification Bell should also trigger a modal dialog if entire objects or parts of objects can trigger notifications. Otherwise it becomes active/inactive.
  • Add to Favorites should at best trigger a confirmation message.
  • Recommendations must be specified in more detail. But here a modal dialog is also conceivable, which gives me the choice to send content to a person, group, role, by mail to the outside, ... to recommend.

»» Sorry, I couldn't draw that anymore.

3.3 New User Interface Concepts

We need a new Kitchensink Element "ObjectBar"

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 Information

{ 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 Contact

• Author of the Request: Samoila, Oliver [oliver.samoila]
• 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.}

7 Funding

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

• partly Technische Hochschule OWL
• In any case, I want to push it in the direction of the Advisory Council of ILIAS e.V.

8 Discussion

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