Home

Sigma - Backend

Here are some insights about the global structure of the application.

• Users
• Groups
• Memberships

To-Do list (sorted by priority)

• Check User's serialisation (attribute invited_to_groups?)
• Improve users list retrieval (no need to check cluster membership since clusters are groups)
• Improve group retrieval: if requestor is member of the group, he can see all members (even those with perm_rank = 0), otherwise he can only see users that he shares another group with and whose perm_rank is > 0; particular case: if a user has requested to be member of a group, he can retrieve the membership instance
• Precise the specifications about groups relations (resp_group? Type of a group written in a relation with a parent group?)
• Group.resp_group cannot be null anymore
• Solve problem at Group creation in case that the group is its own rest_group
• Anybody can change the profile photo of everybody???
• The route /user/<pk>/invite/ is not correctly documented on Swagger
• Review tests after serialisers modifications