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
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
The text was updated successfully, but these errors were encountered:
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.
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 allStudy
s in MngoDB, we can switch that to arequired
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
The text was updated successfully, but these errors were encountered: