-
Notifications
You must be signed in to change notification settings - Fork 2
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
Comments on Download Page #89
Comments
Other Genome Download - Reference To be consistent with what we do for Dd, put the citation at bottom here and once we do Dd we decide what shorter format we use |
For the references,
|
References for DownloadGenome Sequence: Eichinger et. al 2008 Maybe we should have one Ref page for all genomes. Then we might have this order: D. discoideum Genome |
Some updates based on the original post:
|
https://testdb.dictybase.org/downloads
This long reference on top is ridiculous. Why on top and so big?? Please remove for now. We should add references to the Dicty anatomy, the genome seq, maybe others and have to think how we do add them at bottom.
When clicking on any Download, open in new tab or window automatically? After I first clicked and it overwrote the downloads page and I couldn't even go back I now do right click to open in new tab. But maybe should do automatically?
I thought we decided not to have this anymore? https://betastorage.dictybase.org/downloads/44689/gene-information/DDB_G-curation_status.txt Instead we should just have a table for DDB ID mapping? Gene Prediction (Old vs Up to date (Mostly curated)like the ID Converter where it's hard to do all.
Maybe in 'Dictyostelium Sequences and Annotations' it should not only say what entity but what format, e.g. FastA format.
@cybersiddhu I think the protein domain data should be with Gene ID (DDB_G) and not Feature ID (DDB). Is that possible? I'm surprised at the DDB ID as it's proteins and those are mapped to DDB_G ID?
This seems too old: 'N-terminal myristoylation sites (July 2006)'. Maybe don't have here and add when we have an update?
Thanks!
The text was updated successfully, but these errors were encountered: