Skip to content
New issue

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

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

Already on GitHub? # to your account

Only allow users to autocomplete with their own target genes #273

Closed
bencap opened this issue Sep 16, 2024 · 1 comment · Fixed by VariantEffect/mavedb-api#341, #307 or #321
Closed
Assignees
Labels
app: backend Task implementation touches the backend app: frontend Task implementation touches the frontend type: enhancement Enhancement to an existing feature

Comments

@bencap
Copy link
Collaborator

bencap commented Sep 16, 2024

Autocompleting via the global MaveDB target gene space may be somewhat error prone and lead to behavior our users do not expect. They are much more likely to be familiar with their own target genes, and those target genes are also substantially more likely to actually be relevant to their data.

@bencap bencap added the type: enhancement Enhancement to an existing feature label Sep 16, 2024
@bencap bencap added app: backend Task implementation touches the backend app: frontend Task implementation touches the frontend labels Oct 1, 2024
@bencap
Copy link
Collaborator Author

bencap commented Oct 7, 2024

Every target is a copy of the autocompleted target. This means there is a lot of duplication of targets in our database. Might we want to de-duplicate targets for a user when there are many?

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
app: backend Task implementation touches the backend app: frontend Task implementation touches the frontend type: enhancement Enhancement to an existing feature
Projects
None yet
2 participants