-
Notifications
You must be signed in to change notification settings - Fork 16
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
Searching for full or partial concept accessions is not working, eg TO:0000286 #345
Comments
I just checked that TO is included in the list of Accession Data Sources to be searched, and yes it is there: Line 616 in 30ea3ee
So maybe the Lucene search is doing something funny with digits: Line 696 in 30ea3ee
|
We have internally deployed KnetMiner:master (2 weeks ago) for testing Arabidopsis on http://babvs72.rothamsted.ac.uk:8091/client/ Querying with a gene and TO term: http://babvs72.rothamsted.ac.uk:8091/ws/araknet/genepage?keyword=0002616&list=AT2G25930 shows gene plus 235 other (visible) concepts out of total: 419; with various Phenotype & 7 visible Trait nodes (1 of which is TO:0002616) |
The Lucene field is called ConceptAccession_DSID
Checked the Lucene index with Luke and spotted a tiny typo which meant the KnetMiner search was not considering concept accessions. |
Still does not highlight also, http://localhost:9090/ws/aratiny/genepage?keyword=%22plant%20height%22&list= throws this new |
The fix had unlocked another issue with the way concept accessions were indexed in Lucene. It has now been resolved in Ondex LuceneEnv. Following queries are now working as expected: ws/aratiny/genepage?keyword="TO:0000286"&list=AT1G13180 |
The example below should only show paths between gene:TraesCS2B02G184100 and TO:0020057
http://knetminer.rothamsted.ac.uk/wheatknet/genepage?keyword=0020057&list=TraesCS2B02G184100
But it shows many other paths...
It works fine if instead of the the TO accession, the TO name is used:
http://knetminer.rothamsted.ac.uk/wheatknet/genepage?keyword=leaf%20AND%20rust%20AND%20response&list=TraesCS2B02G184100
The text was updated successfully, but these errors were encountered: