Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

gather community/leadership input regarding the textual annotations involved in study/consortium #1119

Open
turbomam opened this issue Sep 15, 2023 · 1 comment

Comments

@turbomam
Copy link
Member

turbomam commented Sep 15, 2023

We can merge this PR now and change it's textual annotations (mappings, labels, etc.)later without a migration. @emileyfadrosh @mslarae13 @lamccue

After populating the study_category for all Studys in MngoDB, we can switch that to a required slot, and s migration shouldn't be required.

However, it will become necessary for the Submission Portal to ask whether the thing that is being submitted is a more like a study or more like a consortium. @jeffbaumes @naglepuff @marySalvi

@mslarae13
Copy link
Contributor

We chatted about this in the study page squad. My suggestion, we assume a study is a study and any consortiums or umbrella studies we want to add, we'll evaluate on a case by case basis for now.

Implementing this language into the submission portal now is likely to confuse the community and we should popularize it first.

Leave this issue open, as a reminder for when we're ready to tackle identifying study type on the submission portal. Until then, backlog.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants