-
Notifications
You must be signed in to change notification settings - Fork 0
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
Can we tell when was the last time a feature was annotated? #7
Comments
None of the tables (feature_cvterm, blast_hit_data, analysis) provide a way to find when the last record was created. Also, the importers don't have any indication which organisms they affected so we can't use those hooks either. We might have to just generate an entire site fasta file once every 6 months or something like that. Would that work? |
the chado way to track this is to keep the date in the analysis. |
Right but unfortunately the analysis itself won't change per annotation run. It also won't have information on which organisms to generate data for and which to ignore. It gets even more complicated when importers clear all annotations related to an analysis before reimporting. |
why not? it should.
It will if you create new analyses... |
We are using 1 site-wide analysis for this (1 ips analysis, 1 blast trembl, etc). We then run blast/ips on a fasta file that has all organisms merged into one. (like we did before for ips) |
If we can find a way to tell when was the last time an organism was annotated, we can allow the admin to specify every how often should we generate fasta files for those organisms.
The text was updated successfully, but these errors were encountered: