Orphan Studies

[odeimaiz]

Currently the frontend doesn't prevent a Study go orphan.

A user with write access can change the accessRights of a Study, meaning that can add/remove/edit study collaborators. Within this operations, one can even remove themself from the list of collaborators, and if that was the last user with access to the study, the study would end up orphan (no entry in the project_to_group table).

If this happens, when that user lists the projects, the backend fails and the projects can't be shown.

[sanderegg]

Also check why the project that is disowned is still listed