...
Status | ||
---|---|---|
|
...
...
Rwquirements
Requirements
- to allow users to create a group of user
- to allow deck creators to allocate a group to have editor permissions on a deck
- to allow deck creators to allocate a group to add comments / questions to a deck
- to allow deck creators to allocate a group to add comments / questions to a deck
...
- UI under the user area to create and manage a deck
- name a group
- find users
- add / invite a user
- delete a user
- deactivate a group (may be better than deleting)
- UI under deck edit to allocate an existing group to a deck to give permissions to edit the deck.
- this should be disabled if the user is not the owner of the deck
- User profile should display which groups a user is a member of and allow users to leave a group.
...
property | type | required | format checking | state of implementation | Remarks |
---|---|---|---|---|---|
id | objectId, autoincrement | yes | isInteger | ||
name | string | yes | |||
timestamp | string | yes | auto generated | ||
Descriptiondescription | string | no | |||
isActive | boolean | no | |||
members | array of members | no | user ids | ||
...
Question | Asked by | Outcome |
---|---|---|
What happens when a user is removed from a group? Do they lose rights to edit a deck they have made contributions to in the past or do they remain an "active" contributor? | Propose - user rights a are removed for now | |
Do we "invite" users to group or automatically add them? | Propose - user received notification and then option to leave group | |
Do we allow groups to be "owned" by multiple users or transferred between owners? | FOR THE FUTURE! |
Not Doing
In D2.2 SlideWiki diff/merge module, it is proposed that groups of editors is managed through users belonging to an organisation (4.4.1). This has 2 limitations we wish to avoid:
...