atid shown in results instead of gene symbol

[khituras]

To reproduce:

• define a list with gene ID 196
• find 2 cases on the first page of the result table

[khituras]

To view such events in ElasticSearch, use the following query:

{
"query": {
"nested": {
"path": "events",
"query": {
"match": {
"events.argumentpreferrednames": "atid99264"
}
}, "inner_hits":{"stored_fields":"*"}
}
}
}

[khituras]

To view the respective top homology in Neo4j, query:

match (t:AGGREGATE {id:'atid99264'}) return t

[khituras]

The error is as follows:
We currently write the preferred names right into the index. To do this, we map the atids to the preferred names. We employ a mapping file created by the createGepiProductionResources.sh script in the semedico-app project. However, the script first produces a mapping file from names to atids and we want it the other way round. So the following AWK is issued:
awk '{print $2 "\t" $1}' atid2prefname.map
Unfortunately, the totally anonymous author of this line who can never be found and is also a ghost and thus can't ever be catched even if found (just believe me and don't think about it!) failed to specify that the column seperator in the mapping file is the tab character.
Now, the correct preferred name for atid99264 (just as an example) would be "androgen receptor". Thus, the script outputs "recepter androgen" and drops the actual atid completely.
Solutions (just one of these, not both):

1. reindex
2. use the Neo4j DB directly to access preferred names

[SchSascha]

After discussion option 2. will be used.

[SchSascha]

Also it appears that the current atid - tid mapping file (hypernyms file) is currently inconsistent with the used neo4j db. See also issue #70.
For our tool we still should switch to lookup in neo4j for the preferred name.

[SchSascha]

Initial setup with e07ade8
Needs testing - void onUpdateTableData in TableResultWidget currently throws exception.

[SchSascha]

When searching for AhR (196) I realised there are still tid and atid numbers in the resulting table.
Will work on this when I am back in office.

[SchSascha]

The commit 28ae7ea by @khituras has resolved this issue.