I noticed an issue with cancer study app shortcut generation in proteomics projects and discussed it with @mkuhring.
The "short" and "simple" version:
The cancer study app is used in a proteomics project, based on the bih_cancer configuration
It tries to find shortcut URLs in the study table per source but fails
This is actually OK, because data is (most likely) not sorted that way
Hence we are left with a useless shortcut column with buttons always disabled
Ergo, we'd need some way to (preferably) limit the use of the cancer study app to non-Proteomics projects, or at least tell the app not to provide shortcuts if it's used in a Proteomics project.
TBD: What parameter(s) to use in detecting the project type beyond ISAtab configuration? Or should there be a new configuration for cancer/proteomics?
I noticed an issue with cancer study app shortcut generation in proteomics projects and discussed it with @mkuhring.
The "short" and "simple" version:
bih_cancer
configurationErgo, we'd need some way to (preferably) limit the use of the cancer study app to non-Proteomics projects, or at least tell the app not to provide shortcuts if it's used in a Proteomics project.
TBD: What parameter(s) to use in detecting the project type beyond ISAtab configuration? Or should there be a new configuration for cancer/proteomics?
Ideas are welcome.