You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the addition of the kaiko metaproteomics analysis option, we need a way to distinguish the data objects associated with two types of MetaproteomicsAnalysis records.
As is, if there are two MetaproteomicsAnalysis records associated with the same biosample with different values in the metaproteomics_analysis_category, they are displayed like below:
We'd like to add an annotation line below each "Workflow Activity" line following the rules outlined below:
if the value for metaproteomics_analysis_category == matched_metagenome; display like below Workflow Activity: Metaproteomics Analysis Acvitivty for nmdc:wfmp-XX-XXXX; NMDC metagenome matched
OR
if the value for metaproteomics_analysis_category == in_silico_metagenome; display like below Workflow Activity: Metaproteomics Analysis Acvitivty for nmdc:wfmp-XX-XXXX; Uniprot reference genome matched
@naglepuff - I've (re)-loaded some mock data to dev-mongo today after it was overwritten during the last release. See details here: microbiomedata/issues#1082
With the addition of the kaiko metaproteomics analysis option, we need a way to distinguish the data objects associated with two types of MetaproteomicsAnalysis records.
As is, if there are two MetaproteomicsAnalysis records associated with the same biosample with different values in the metaproteomics_analysis_category, they are displayed like below:
We'd like to add an annotation line below each "Workflow Activity" line following the rules outlined below:
Workflow Activity: Metaproteomics Analysis Acvitivty for nmdc:wfmp-XX-XXXX;
NMDC metagenome matched
OR
Workflow Activity: Metaproteomics Analysis Acvitivty for nmdc:wfmp-XX-XXXX;
Uniprot reference genome matched
See slides 12 and 13 in https://docs.google.com/presentation/d/1ubYn0TMVNJ6VkG5UoQNns5NsJaqPUnro/edit?usp=sharing&ouid=107901205882214522292&rtpof=true&sd=true
The text was updated successfully, but these errors were encountered: