The ability for a group to be linked to multiple groups

Created on 10 June 2024, 7 months ago

Updated 11 June 2024, 7 months ago

Problem/Motivation

We use groups to signify organisations on a platform. These organisations contain various data with different roles that may see data associated with that organisation based on group permissions. Additionally the groups have subgroups which contain further information around which may be collaborated (e.g. certain yearly repeating processes that different people need access to).

What we now want to do is to have the organisation groups be able to collaborate with other organisations in different collective structures. To achieve this we believe we need the ability to associate an organization with multiple collaborative groups at a time (i.e. be in multiple trees at the same time). An ASCII illustration is below (subgroups for the organisations not visualised).

       Collaboration A         Collaboration B
      /               \        /              \ 
Group 1                 Group 2                Group 3

The idea is that this would allow people from Group 1 and 3 to see thngs in Group 2 through Collaboration A and Collaboration B. It would allow people in Group 2 to see things in Group 1 through Collaboration A and things in Group 3 through Collaboration B.

There is an N:N relationship of Collaboration groups and organisation Groups.

Steps to reproduce

Proposed resolution

I'm not sure what it would take.

Remaining tasks

User interface changes

API changes

Data model changes

✨ Feature request

Status

Active

Version

2.0

Component

Code

Created by

🇳🇱Netherlands kingdutch

Live updates comments and jobs are added and updated live.

Comments & Activities

Issue created by @kingdutch
Comment 7 months ago →
🇳🇱Netherlands kingdutch
Comment 7 months ago →
🇧🇪Belgium kristiaanvandeneynde Antwerp, Belgium
Well the main issue is that Subgroup is based on the nested set model for fast reads (and slower writes as a tradeoff). Theoretically it could be done if we made the tree metadata fields multi-value and tagged the same groups as belonging to multiple trees.

However, the entire module was built around the single tree principle and therefore this would constitute a significant rewrite of seemingly unrelated systems. Most of these rewrites would probably end up breaking BC, so it's likely that an entire new major version is needed for this functionality.

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024