You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the new clowder 2.0 I was wondering if we can change the organization of spaces and datasets.
I have noticed that frequently we end up with a lot of spaces that belong to a single group/org. It would be nice if we can have a hierarchy of spaces. One such example is gitlab
gitlab has the notion of project and groups (and subgroups).
project is top level
project has groups and repositories
groups has groups and repositories
permissions are done on each of these, and trickle down. So if i'm an owner in project, i'm an owner of everything below. I can give permissions at the level of repo. Keep in mind a repo can only be part of a single group/space, so that make the permissions each to find.
Now mapping this to clowder:
space it top level
space can have groups and datasets
groups can have groups and datasets
Permissions are done on each of these, allowing use so give global permissions on a per space level (as currently is done), but then have permissions on a group and finally dataset basis.
One change, although I think a lot of systems are already set this way, dataset can only be in a single space/group.
This would remove the need for collections, since we can put them in a group.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
With the new clowder 2.0 I was wondering if we can change the organization of spaces and datasets.
I have noticed that frequently we end up with a lot of spaces that belong to a single group/org. It would be nice if we can have a hierarchy of spaces. One such example is gitlab
gitlab has the notion of project and groups (and subgroups).
permissions are done on each of these, and trickle down. So if i'm an owner in project, i'm an owner of everything below. I can give permissions at the level of repo. Keep in mind a repo can only be part of a single group/space, so that make the permissions each to find.
Now mapping this to clowder:
Permissions are done on each of these, allowing use so give global permissions on a per space level (as currently is done), but then have permissions on a group and finally dataset basis.
One change, although I think a lot of systems are already set this way, dataset can only be in a single space/group.
This would remove the need for collections, since we can put them in a group.
Beta Was this translation helpful? Give feedback.
All reactions