-
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
Change the quick search to find obsolete genes on the merges and deletions page #1054
Comments
A good first step would be to discuss what should be shown on the pages for the obsolete genes. Then it will be easier to decide if we should use Chado for this. For comparison, FlyBase do store obsolete genes in Chado. |
name, location, reason for obsoletion |
I wonder if those identifiers for many cases should not be treated just as synonyms, two examples below. What would be a case in which an obsoletion should be treated differently from a synonym? SPNCRNA.55This is how
When
Then
SPAC11D3.12cIn this one we don't even have two separate features in our record. Currently it is an
|
Historically if a CDS was replaced by an ncRNA or vice. versa, we kept the original names as synonyms. This was mainly because we would 'lose' them otherwise. If we have a method to obsolete IDs and allow people to trace their history we can review this practice. (i.e SPNCRNA.55 would not be a synonym of SPAC6B12.18, it would just become an obsoleted feature that was 'replaced by SPAC6B12.18). We can discuss this tomorrow... |
Not used for anything yet Refs pombase/pombase-chado#1054
@manulera update with todays decisions |
We decided that for most cases these obsoletions are either coming from merges or from removed features that never had associated annotations. We decided that having dedicated pages for each them is not worth it, but that they should be findable in the quick search and redirect to a page with the list of merges or deletions. |
I've changed the title to match our plan. |
We should think about loading the deleted genes with the
is_obsolete
flag to true. A lot of downstream code will need to change to check the flag so that obsolete genes aren't included in the query builder results and in counts/stats.We're considering this so that we can eventually include the deleted/obsolete genes in the quick search and provide basic "obsolete gene" pages with any historical information that might be useful.
Loading these genes into Chado might not be the best solution. It might be better for the web site code to read a separate (TSV?) file with this information and only load the current genes into Chado, as we do at the moment. This needs a bit or discussion and thought.
The text was updated successfully, but these errors were encountered: