-
Notifications
You must be signed in to change notification settings - Fork 0
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
Implement separate procedure to "share with consortium" #21
Comments
@cbutsko, @kvantricht |
to be discussed: do we need the license and link for each dataset that we use for training (in order to publish the products later on)? |
to add to the pop-up message: |
@jdegerickx can be change this message a bit to inform about citation as well. |
@santoshkaranam, good question. Personally I would avoid being too specific at this point because we still might change the procedure. If they already provided a preferred way of citation through the metadata, we will off course use that instead of username and institute... |
@jdegerickx @kvantricht should we make it the default selection with checkbox checked initially? If the user does not want, then the user has to uncheck, else all uploaded datasets are shared with the consortium (privately) by default. If we decide to make it default option, then this checkbox has to be included in the very first step where the user uploads the dataset file. |
@santoshkaranam, could you briefly explain again what happens in the background when a user wants to share the data with the consortium? |
@jdegerickx Having default check is to get as many user datasets to consortium as possible. The flag can be set any time in the upload workflow. If it is at the first step, the user will be informed before user uploads. |
I would keep it as Christina suggested just at the end of the workflow. |
OK Sure, so this will be explicit selection by the user. |
what happens when user selects to share with consortium:
|
Next to option to initiate "make public" procedure of user datasets, we need a separate and simpler approach to share the dataset with the consortium so we can use it in training.
The text was updated successfully, but these errors were encountered: