We are using MultiQC to generate QC reports for the RNA-seq pipeline (#205). MultiQC generates HTML files (example here). During this week's tech team meeting, the question of hosting these HTML files came up.
Problem or idea
The idea behind hosting these files is that this will facilitate users ability quickly view the report, perhaps obviating the need to download the files alongside their expression data & sample metadata. It may also be helpful information during the data discovery and selection process -- i.e., a user may want to know about per sequence quality scores prior to adding a sample to their dataset.
Solution or next step
We should investigate this further from both implementation and user experience angles after Keytar Kurt.
Related
Relevant QC tools are discussed here: #203, #205
New Issue Checklist
[x] The title is short and descriptive.
[x] You have explained the context that led you to write this issue.
This is fairly trivial to implement backend-wise (just a single call to boto to move a file to S3), but there will be interface work required, I think we want to punt this until after KK.
Context
We are using MultiQC to generate QC reports for the RNA-seq pipeline (#205). MultiQC generates HTML files (example here). During this week's tech team meeting, the question of hosting these HTML files came up.
Problem or idea
The idea behind hosting these files is that this will facilitate users ability quickly view the report, perhaps obviating the need to download the files alongside their expression data & sample metadata. It may also be helpful information during the data discovery and selection process -- i.e., a user may want to know about per sequence quality scores prior to adding a sample to their dataset.
Solution or next step
We should investigate this further from both implementation and user experience angles after Keytar Kurt.
Related
Relevant QC tools are discussed here: #203, #205
New Issue Checklist