2021.07

[antgonza]

@mestaki, this is how the prep page will look like:

... and this is the new workflow page:

What do you think?

[coveralls]

coverage: 91.099% (+0.008%) from 91.091%
when pulling 94991b8 on antgonza:2021.07
into fb396ec on qiita-spots:dev.

[mestaki]

*This is very useful, just some rewording below to hopefully make it more clear for novice users.

---

In this page you will find our recommendations on how to processes each data type available in Qiita and the minimum processing requirements to make your data public.



For convenience, there is an "Add Default Workflow" button for each preparation that will add the recommended workflow steps for your raw data which then you can process. It is important to note however that this workflow is based on the default Earth Microbiome Project protocol and so assumes the uploaded data are multiplexed sequences with the reversed barcodes in your mapping file and index sequence file (see here for more details). If this protocol does not apply to your data you can still use the Default Workflow, however, you should first manually process your data using the appropriate steps until you have demultiplexed your reads. After demultiplexing the Default Workflow is safe to use with any protocol.



If you have already manually performed one of the processing steps in the Defaul Workflow pipeline, the "Add Default Workflow" button will not re-select those steps but instead will only select any remaining steps that have not been completed. You can also add additional workflows on top of the recommended Default Workflow at any time.



Note that this is not a full inclusive list of data types accepted by Qiita but only those that have a defined workflow.

[mestaki]

I was thinking that if we are not vigilant enough with explaining the EMP assumptions of the Default Workflow we may get a lot of headaches later on when people not-knowingly process their non-EMP protocols. So anything we can to draw their attention to that important aspect I see as time-saving for admin later on.

One suggestion, what about replacing "What's a Default Workflow" to "Important note about Default Workflow"? <- That way they are more likely to read that description with the important note about the demux step. Or maybe adding a ⚠️ logo beside the button?

[mestaki]

Just some rewording and one suggestion about adding a "notice/warning" about EMP dependency of Standard Workflow

[antgonza]

Thank you; now it looks like this:

and this:

Note that I used most of your suggestions but tried to keep the explanation as general as possible by using the target gene example but still mention that there are multiple workflows.