Who-Is-Online: Usability Improvements and Advanced Options

1 Requirements

Make Awarenes tool entries configurable

Admins should have the possibility to dis-/enable the items / actions (Mail, Profile, Shared Ressources, New Onscreen-Chat ..) ...that are available there. See User Action Service.

Exception: On-Screen Chat. The new On-Screen Chat can only be activated when the "Who is online"-functionality is activated.

Popup-Deactivation

Some requrirements moved to Who-Is-Online: Advanced Settings.

The rest should move to a new, "Contact" related page.

Popup-deactivation of Contact Requests

• There should be a possibilty to deactivate the Contact-Request - popup in the administration panel of the awareness-tool.
• There should also be a possibility to individually block the contact request popups (Suggestion: Personal Desktop » Setting » General Settings). So if a user is just not interested with that information, even if the tool has been activated by the ILIAS administration.

Default state of new Users

Some requrirements moved to Who-Is-Online: Advanced Settings.

The rest should move to a new, "Contact" related page.

There should be a Privacy setting to set the default state of new users Settings for ILIAS-Admin to define the default state of new users,

• Default-value of: "Allow to Contact me"

2 Additional Information

• Idea / concept: Lauener, Hansjörg [lauener]
• Interest in funding: Universität Bern
  
• Maintainer: (will be set by Jour Fixe / maintainer)
• Implementation of the feature is done by (will be set by Jour Fixe / maintainer)
• Testcases by: (please add your name if you want to create the testcases for this feature)

3 Discussion

Killing, Alexander [alex], 17 June 2016: I support the awareness tool related configuration possibilities in general. Please note that

• "Contacts" is a whole separate component (different maintainer). So this feature wiki page needs to be splitted.
• I think the on-screen-chat should not depend on the who-is-online tool. It should be possible to use the on-screen-chat without the awareness tool. There are various contexts where are chat could be triggered (see next point).
• I think the configuration of the who-is-online actions (activation) should be generalized and moved into the user service. I quote myself from the Introduction of 'Staff' page page: "When it comes to the actions that are availble for each user, I think the implementation of the who-is-online tool could be a foundation. Parts of it should be moved to the user service to allow other components to a) provide user actions (e.g. Mail, Profile, Shared Ressources, View Competences, ...) and to b) provide user action contexts (e.g. awareness tool, profile, member gallery, staff list, ...). This way we could provide a general configuration in the administration, which contexts support what actions. And each context provider could get a list of actions in a generic/centralized way."

JourFixe, ILIAS [jourfixe], June 20, 2016: We support Alexander's suggestion to implement a User Action Service within the user service that could be used by the contact component, the awareness tool component and - in future releases - in other components, too. This service should be available for 5.2. The current wiki page could tackle the use of this GUACS in the awareness tool. Another wiki page should tackle the use by the contacts component. Additionally, we would like to use the notification configuration (see http://www.ilias.de/docu/goto_docu_pg_57146_42.html) to administrate the available channels and defaults for the several communication channels. Michael will show a dummy at the next Jour Fixe.

Mela, Alix [ILIAS_LM] @Uni Bern, 29 june 2016
Thank you for nr. 1! We had to deactivate the whole feature after two days because people felt disturbed by the pop-ups.

Killing, Alexander [alex], 23 Aug 2016: I just called Michael. Databay will not include the notification configuration in 5.2. So the awareness tool cannot really use it. I created a Who-Is-Online: Advanced Settings feature wiki page for the first two options here.

Zenzen, Enrico [ezenzen], 05 SEP 2022: This request no longer fulfills the requirements of the Feature Wiki. In consultation with the maintainer I change the status of the feature request to "Redundant / outdated". If the request is still relevant, please update template and mockups.

4 Implementation

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