...
property | type | required | format checking | state of implementation | Remarks |
|---|---|---|---|---|---|
id | objectIdnumber, autoincrement | yes | isInteger | ||
| name | string | yes | |||
| timestamp | string | yes | auto generated | ||
| description | string | no | |||
| isActive | boolean | no | |||
| members | array of members | nouser ids | {userid, joined} | ||
| creator | number | yes | userid |
Deckservice → has property Group
...
| 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 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? | Kurt | Also 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:
...