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

Best practices in annotating CNVs and fusions alongside variants in knowledgebases #39

Closed
bpitel12 opened this issue Oct 9, 2018 · 2 comments
Labels
2018 Topics proposed for the 2018 hackathon in San Diego curation selected-for-action Tasks that were selected at the event and have followup attached to the issue

Comments

@bpitel12
Copy link

bpitel12 commented Oct 9, 2018

One noted gap in many well-known knowledgebases is the coverage and searchability of copy number variants and fusions/structural variants. Many our our in-house tools are attempting to employ segment/coordinate based searches to link to relevant data/knowledge for clinical reporting of copy number variants. Fusions are another beast for us - each assay seems to annotate things a little differently. For example, are the fusion partners always listed 5' --> 3'? How do we document structural rearrangements (translocations/inversions/CNVs) that result in over/under expression by position effect (i.e. they don't result in a fusion product)?

@anna-tanska
Copy link

That's a great topic. CNVs curation hasn't been well defined so far. Reporting and clinical actionability of CN poses many questions in our lab especially the ones that don't create a functional fusion but may still affect gene expression.

@bpitel12
Copy link
Author

CNV-SV.pptx

@acoffman acoffman added 2018 Topics proposed for the 2018 hackathon in San Diego selected-for-action Tasks that were selected at the event and have followup attached to the issue labels Feb 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2018 Topics proposed for the 2018 hackathon in San Diego curation selected-for-action Tasks that were selected at the event and have followup attached to the issue
Projects
None yet
Development

No branches or pull requests

4 participants