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
{{ message }}
This repository has been archived by the owner on Jan 18, 2020. It is now read-only.
There need to be some controls around who can create, modify, and view/use cohorts. View in this context means see allele frequencies for variants, similar to what is done now. I suggest the following approach:
Project cohorts: People with a project manager role (likely needs to be created) can add, edit, and delete project-level cohorts. All members of a project can see these cohorts and use them in queries
Public cohorts: Site admins can create, edit, and delete public cohorts. All users can view these cohorts and use in queries.
This ticket originally included a notion of "personal" cohorts, but this introduces complexity we don't need at this time that is hard to justify.
The text was updated successfully, but these errors were encountered:
There need to be some controls around who can create, modify, and view/use cohorts. View in this context means see allele frequencies for variants, similar to what is done now. I suggest the following approach:
Project cohorts: People with a project manager role (likely needs to be created) can add, edit, and delete project-level cohorts. All members of a project can see these cohorts and use them in queries
Public cohorts: Site admins can create, edit, and delete public cohorts. All users can view these cohorts and use in queries.
This ticket originally included a notion of "personal" cohorts, but this introduces complexity we don't need at this time that is hard to justify.
The text was updated successfully, but these errors were encountered: