-
Notifications
You must be signed in to change notification settings - Fork 1
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
Share experiment feature during creation #371
Comments
Experiments are private by default (they are only available for the user who created them). Right now, we have no way to change this through application UI.
In order to have the above available in the application we need to:
I don't know how the multiple experiments dialog is shown, maybe we don't need it? The above estimation doesn't include it. |
thanks @afonsobspinto, I am not sure what you mean by 'multiple experiments dialog' can you please elaborate on that? Also, users are going to be able to share only during creation or will they be able to share the experiment after it has bee created (and inspected)? |
Thanks Afonso, I frankly forgot about the sharing multiple. I would leave it on the side for now as it is not a pressing use case. I would default that the user wants to share an exp after the creation (From the menu as showed in the picture) and experiments can only share with an existing user (i.e. you cannot input an email address of someone who is not in the Keycloak db, you can only input unsernames or email from keycloack). does this make sense? cc @syamace-metacell |
uh, also, let's keep in mind users might want to un-share an experiment. so she Share line might open a model where we see with whom the experiment has been shared, and the user can 'remove' someone |
From the client:
Share feature appears to be disabled. This is an open issue that Afonso just started addressing at the end of the last SOW, according to github. He wants to make it an option during upload for a dataset/cord to be public.
@afonsobspinto could you please weigh in wrt to what's missing? cc @zsinnema @D-GopalKrishna
The text was updated successfully, but these errors were encountered: