Show Advanced KnowledgeHide Advanced Knowledge

Streamline Membership Assignment Methods

1 Requirements

There are two methods to assign/detach course/group member roles:

• Functions of the "Members" tab inside the Repository object
• Role administration / XML user data import

While assigning/detaching course/group member roles, there are two aspects:

• Assigning/detaching the role to/from the user account, thus affecting its permissions for the object
• Assigning/detaching the object to/from the Personal  Desktop ("Overview") of the user account

Unfortunately, both of the abovementioned methods do not have exactly the same impact which leads to some inconsistency regarding the presentation of the object on the Personal Desktop:

Assigning/detaching membership via:	Assigning object to the Personal Desktop	Detaching object from the Personal Desktop
"Members" tab	yes	yes
Role administration / XML import	yes	no!

 
So, as administrators often think that both of the ways to assign/detach course/group member roles have the same impact, often courses/groups stay at the Personal Desktop ("Overview") which aren't supposed to (provided that the affected user accounts still hold "View" permission for the course after detaching them – however, this is the case by default).
We think that both methods should have the same impact.

2 Status

• Scheduled for: Not scheduled yet (will be set by Jour Fixe)
• Funding: Required
• Maintainer: (will be set by Jour Fixe)
• Implementation of the feature is done by tbd
• Contract settled: No
• Tested by / status: tbd

3 Additional Information

Contact the following persons if you want to know more about this feature, its implementation or funding:

• Information about concept: Florian Suittenpointner (suittenpointner [at] qualitus [dot] de)
  
• Information about funding: tbd
• Information about implementation: tbd

4 Discussion

Consider implementing a completly seperated Service (including the GUI) with no dependencies to courses/groups... additionally keep in mind object relevant actions as register notifications (forum, ...)

Zenzen, Enrico [ezenzen], 03 AUG 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.

5 Implementation

...