Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. UI under the user area to create and manage a deck
    1. Addition option under Username dropdown to access Groups. This should be available for all users and list all the groups they belong to.
    2. on the Group page "Add New Group" takes you to a new page to create a new group and add users.
    3. Settings button allows the owner to edit the group (e.g. add and remove users). This should only be enabled for group owners





    User profile should display which groups a user is a member of and allow users to leave a group (implement later)



  2. UI under deck edit to allocate an existing group to a deck to give permissions to edit the deck.
    1. this should be disabled if the user is not the owner of the deck
      DeckEdit UI mockup

...

property
type
required
format checking
state of implementation
Remarks

id

objectIdnumber, autoincrementyesisInteger



namestringyes 

timestampstringyesauto generated

descriptionstringno


isActivebooleanno


membersarray of membersnouser ids


{userid, joined}

creatornumberyes

userid



Deckservice → has property Group

...

QuestionAsked byOutcome

 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 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!

Do we define different roles for group members? e.g. editor, owner, etc.
FOR THE FUTURE!
Do we want to provide info about active groups on home page?
FOR THE FUTURE!
Shouldn't a user be able to assign multiple groups write access to a deck?KurtAlso Abi thinks this should be possible. As this gives a tiny additionally implementation cost this will be ready for december.

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:

...

In future we are likely to need to manage a group of users for a deck who don't have editing rights (e.g. students). We can either extend the group functionality to have roles within groups or sub -groups OR allow decks to have different groups assigned for different permissions.

User profile should display which groups a user is a member of and allow users to leave a group (implement later)


FeatureStatus
  

Source material for user/stakeholder feedback

...