-
Notifications
You must be signed in to change notification settings - Fork 3
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
Request to Add 'Normal' Record to bt.Disease #98
Comments
Dear @Kang-chen I'm happy that you find our packages useful! I've transferred this to the
Please keep the feedback coming! I hope this is helpful. If not, please don't be afraid to get back to us. |
Dear @ck-HN the issue here is that our search also searches for this query in the We have already noticed that our search does not quite perform as well as our search on the user interface and we will take this as a chance to improve it. I am afraid that it might take a bit of time though as we are currently also working on other tasks. I'll report back! |
I might be missing something: @Zethson, the search restricted to My guess is that |
@falexwolf I had mixed up the column headers 🤦 . Sorry, the hits are indeed in |
That is astonishing. 🤔 |
Hi @Zethson , When importing datasets, I often encounter the error: I understand you have other development plans, but could you suggest a workaround to help me avoid this issue in the meantime? Thanks a lot! |
Hi @ck-HN, Using When you get the error, it prints a list of records that are already associate with this synonym. You need to Hope this helpes! |
Incredible work on this project!
I would like to kindly request the addition of a "normal" record to the
bt.Disease
.Currently, this specific record appears to be missing, which could lead to inconsistencies when integrating with other datasets. But, in the
laminlabs/cellxgene
repository includes a "normal" record.This addition could help streamline data integration and ensure that users can effectively merge and analyze datasets without encountering discrepancies.
Thank you for considering this enhancement!
The text was updated successfully, but these errors were encountered: