I've set up a NameRes instance on Sterling (accessible in the RENCI VPN only) at <a hr

New synonym format leads to much worse querying about nameresolution HOT 2 CLOSED

translatorsri commented on July 21, 2024

New synonym format leads to much worse querying

from nameresolution.

Comments (2)

gaurav commented on July 21, 2024

This seems to be caused by the query being names:{fragment}*. Removing the asterisk fixing this problem, and the query (preferred_name:{fragment}^10 OR names:{fragment} OR names:{fragment}*) works pretty well:

NameResolution/api/server.py

Lines 104 to 111 in 61fb6d2

    
           filters = [ 
        
               # Boost the preferred name by a factor of 10. 
        
               # Using names:{fragment}* causes Solr to prioritize some odd results; 
        
               # using names:{fragment} OR names:{fragment}* should cause it to still 
        
               # include those results while prioritizing complete fragments. 
        
               f"(preferred_name:{fragment}^10 OR names:{fragment} OR names:{fragment}*)" 
        
               for fragment in fragments if len(fragment) > 0 
        
           ]

((preferred_name:{fragment}^10 OR names:{fragment}* still prioritizes odd results over anything that isn't a preferred-name match, and (preferred_name:{fragment}^10 OR names:{fragment} fails to match when the fragment is incomplete, i.e. Alzheimer disease matches but Alzheimer's disease fails.)

from nameresolution.

gaurav commented on July 21, 2024

This has now been significantly improved, and it's working well enough that is what is being used by Translator UI. Closing.

from nameresolution.

New synonym format leads to much worse querying about nameresolution HOT 2 CLOSED

Comments (2)

Related Issues (20)

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent

	filters = [
	# Boost the preferred name by a factor of 10.
	# Using names:{fragment}* causes Solr to prioritize some odd results;
	# using names:{fragment} OR names:{fragment}* should cause it to still
	# include those results while prioritizing complete fragments.
	f"(preferred_name:{fragment}^10 OR names:{fragment} OR names:{fragment}*)"
	for fragment in fragments if len(fragment) > 0
	]