make form for parameter description in public upload

[mlocardpaulet]

Here is how it should work now for public submission:

1. upload the parameter files
2. automatic parsing when available
3. presentation of a pre-filled form that contains all the parameters that are required for public submission. When absent from the parameter file or not parsed, the fields are empty
4. manual curation from the person providing the data: add missing parameters.
5. submission

When the PR is sent, it should be reviewed by a ProteoBench curator. To simplify his/her work, we should provide:

1. the original parsed parameters
2. the parameter file (the link to them is already available)
3. the parameters modified by submitter (we could consider flagging differences)

[RobbinBouwmeester]

We should maybe have a look at earlier code where this was actually implemented. Also make sure this is connected to required/visualized parameters in the app.

[enryH]

So we predefine the parameters as before. So you decided against allowing for free entries? (parameters the researcher deems interesting)?

[mlocardpaulet]

So we predefine the parameters as before. So you decided against allowing for free entries? (parameters the researcher deems interesting)?

We decided for something in between. When people submit the parameter file:

1. a pre-filled form appears containing a set of parsed parameters.
2. users can fill in the information when it was not parsed (empty fields)
3. there should be a free-text field for parameters that people would be interested in but are not in "our" list.

Does it answer your question?

[RobbinBouwmeester]

File I was talking about:

https://github.com/Proteobench/ProteoBench/blob/b35c47b3322b480a84a0fd97cc63f8d7548adecb/webinterface/configuration/dda_quant.json

[RobbinBouwmeester]

This json is used here:

ProteoBench/webinterface/pages/base_pages/quant.py

Line 245 in 2d3276a

# TODO: change additional_params_json for other modules, to capture relevant parameters

[RobbinBouwmeester]

Will resolve this and at the same time this issue:

#434