Feature Wiki

Information about planned and released features

Tabs

Personal Profile Groups Tab

1 Initial Problem

See Revamp Personal Profile.

2 Conceptual Summary

In extension of Revamp Personal Profile the personal profile should show a groups tab.

Each user needs to opt-in, to publish his/her groups.

This is also where a user will find his/her own groups, i.e. in a sub-tab of his/her profile. This will be true EVEN if groups are not published to other users or publishing is disabled globally. I.e. personal desktop > My Groups should link this sub-tab in the future.

This sub-tab should have a permanent-link.

2.1 Outlook and Related Features

  • courses tab
  • upload images for groups / courses / ...

3 User Interface Modifications

3.1 List of Affected Views

  • User Profile (and my own profile, i.e. Personal Data and Privacy > Preview)
  • Personal Data and Privacy
  • Administration > User Management > Profile (new category) > Settings (new tab)

3.2 User Interface Details

3.2.1 Administration

Administration > Profile (new category) > Settings

  • groups (default=enabled): If enabled, users can publish their groups to other users.

3.2.2 User Profile

  • We suggest to start with a repository-like list representation. Additional feature requests could later add alternative presentations like shown in the following mockup.
  • The usual repository/RBAC permissions are needed to see each group here, i.e. administrators will see all groups, but ordinary users may only see a subset.

3.2.3 User Data and Privacy

My Account > User Data and Privacy > Privacy

  • Groups (y/n): Other users can see your group memberships.

3.3 New User Interface Concepts

{If the proposal introduces any completely new user interface elements, please provide a link to separate feature wiki entries for each of them according to the kitchen sink template.}

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: Kiegel, Colin [kiegel]
  • 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

COGNOS AG, Leitinger, Patrick [PatrickLeitinger]: An existing implementation can be used as groundwork for this. However further funding is needed for trunk-specific requirements and trunk integration.

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

Last edited: 3. Mar 2017, 14:54, Kunkel, Matthias [mkunkel]