-
Notifications
You must be signed in to change notification settings - Fork 1
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
Remap automatically some anatomical terms #208
Comments
In GitLab by @ANiknejad on Feb 12, 2019, 13:27 | the main term to conserve in each case, and what term should be remapped? I guess, we should conserve the one we used in expression data annotations (if any), right? Otherwise, we just have to let these multiple entities commented |
In GitLab by @smoretti on Mar 6, 2019, 09:16 So @ANiknejad which one to we keep? The left or the right term? Also have you already done this remapping on annotation files? |
In GitLab by @smoretti on Apr 30, 2019, 16:04 @ANiknejad should those terms be added to Bgee14.1_mapToUberon_6.xlsx? I didn't get them as warnings currently |
In GitLab by @ANiknejad on Apr 30, 2019, 18:26 no, I do not think so, this is a different problem here. Bgee14.1_mapToUberon_6.xlsx is to currently bypass the problem of non-synchronisation between Bgee ontologies files and annotation files. Here I do not know from where @fbastian is getting this list...but as said, we just have to select the UberonID/name that has the most expression annotation, for example |
In GitLab by @ANiknejad on May 1, 2019, 15:48 |
In GitLab by @fbastian on May 1, 2019, 17:47 I guess the list simply comes from annotations that we identified as being inconsistent. |
In GitLab by @fbastian on Feb 12, 2019, 13:20
Some terms need to be automatically remapped
@ANiknejad can you please tell us what is the main term to conserve in each case, and what term should be remapped?
@smoretti I think we have a pipeline step to remap terms automatically already, right? Can you please add them after reply from Anne?
The text was updated successfully, but these errors were encountered: