Experiments management

[smacker]

We need to allow to manage experiments by web ui:

• create endpoint to manage experiments POST Add experiments create endpoint #180
• create endpoints to manage experiments PUT Experiment update endpoint #190
• create an endpoint to upload file pairs to experiment Upload endpoint #188
• create wireframes for UI
• create frontend for things above Manage Experiments from the front #195

[carlosms]

Hey @ricardobaeta we are ready to start working on the new front-end code to manage experiments. The new functionality, available only to Reviewers, is:

• Upload a DB file with file pairs to be added to a single experiment
• Create a new experiment: Name and Description can be provided
• Update the Name or Description of an existing experiment

Please let us know if you prefer to provide wireframes beforehand, or if it's better if we build something simple and then iterate the design with your input.
I imagine it could be similar to the current dashboard, with buttons to 'edit' 'add file pairs', and 'create new experiment'

[ricardobaeta]

Hey @carlosms The wireframes for this UI is in my to-do for today! Also, updated the description to include the wireframming.

[ricardobaeta]

@bzz @dpordomingo @smacker

Thanks for the help @carlosms !

Here's the wireframe https://balsamiq.cloud/sdjen2c/puva1qi

[carlosms]

Thanks @ricardobaeta. Just to confirm, this wireframe shows the current dashboard with extra elements visible only to users with the right role, or should this be a separate page accessible from the menu?

[ricardobaeta]

Just to confirm, this wireframe shows the current dashboard with extra elements visible only to users with the right role, or should this be a separate page accessible from the menu?

Let's make the experience as collaborative as we can. visible only to users with the right role Persona disclosure :)

[dpordomingo]

LGTM, but instead of «survey» I'd use «experiment»:

I'd also clarify in the upload section that the uploaded data will be added to the current one.

I say so because the button says «upload new file», what can be understood as replacing current data with new one. What about if the button says: «add more file pairs», for example...

[ricardobaeta]

but instead of «survey» I'd use «experiment»

The correct semantic expression is survey. Articulated in the past with @vmarkovtsev and @marnovo

and I'd clarify in the upload section that the uploaded data will be added to the current one.
I say so because the button says «upload new file», what can be understood as replacing current
data with new one. What about if the button says: «add more file pairs», for example...

upload new file allows logic engagement on both contextual behaviours. The one upon Edit & New. Saying that people can upload a new file to the survey, is suited for when they have or don't have a previous file. New file is clear, a new one - agnostic to whereas is a replacement or an addition.

Nevertheless, we should display on the screen the name of the file after upload. I think it's pretty valuable.

Thank you for the product savvy feedback, good ux is good copy.