VEuPathDB / VEuPathDB/lib-eda-subsetting
Add annotations to mbio data to help determine appropriate apps
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
The correlation apps aren't appropriate for all studies. We'd like to hide them in the New Visualization Picker page, just like we do for maps.
To do this, it looks like we'll need two new annotations:
- for each study, add a
hasMetagenomicDataboolean noting if the study contains metagenomic data (entity 'OBI_0002623') - for each assay entity (or all entities), add
isAssayboolean noting if that entity is an assay entity or not.
Also open to other ideas! This was first discussed in https://github.com/VEuPathDB/web-monorepo/pull/732
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the discussion in web-monorepo pull request 732 and reviewing how data and metadata are exposed to the New Visualization Picker page. Determine where study and assay-entity annotations are produced, using OBI_0002623 as the metagenomic-data marker. Done means the requested annotations are available for the picker to use to hide inappropriate correlation apps.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- data
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100