Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

target_gene eNum suggestion #887

Open
only1chunts opened this issue Jan 13, 2025 · 0 comments
Open

target_gene eNum suggestion #887

only1chunts opened this issue Jan 13, 2025 · 0 comments
Labels
1-TermUpdate Update suggestion for existing term, including bugs. Issues from "cig-bug" label moved here. 3-CIG Issues that should be handled by the CIG eDNA

Comments

@only1chunts
Copy link
Member

Current term details
Please supply the current details of the term that you would like to update:

Term name - target gene
Term ID - MIXS:0000044
Structured comment name - target_gene
Definition - Targeted gene or locus name for marker gene studies
Expected value - `16S rRNA, 18S rRNA, nif, amoA, rpo`

Current our list of expected values is very restricted and infact misleading in certain cases (16S rRNA is not specific, the eukaryotic 16S rRNA is not homologous to the bacterial 16S rRNA, see comments in linked ticket below)

Suggested update(s)
There is ongoing work by GBIF and the eDNA group that are suggesting a list of possible target gene terms that we can consider as the controlled vocab list of possible values for this term:
gbif/metabarcoding-data-toolkit-ui#93

Additional context

@only1chunts only1chunts added 1-TermUpdate Update suggestion for existing term, including bugs. Issues from "cig-bug" label moved here. 3-CIG Issues that should be handled by the CIG eDNA labels Jan 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1-TermUpdate Update suggestion for existing term, including bugs. Issues from "cig-bug" label moved here. 3-CIG Issues that should be handled by the CIG eDNA
Projects
Status: No status
Development

No branches or pull requests

1 participant