Menu
▾
▴
#52 Problems with maxGeneralityDistance parameter
open-accepted
5
2011-10-31
2011-10-28
No
We have implemented getResourcesByTerms method in our use case and we are testing with maxSpecificityDistance and maxGeneralityDistance parameters in order to get related content (specifity and general terms). We have no problems with the first one. For example, i searched with "human(mortal)" and i get specificity results like "man" or "woman".
Then i tried to get "human" searching with "woman" controlled concept. But i had no results relating to human.
http://195.235.93.234:8080/platform-rest/knowledge-service/getResourcesByTerms?json=\{%22includeTargets%22%3Atrue%2C%22maxSpecificityDistance%22%3A2%2C%22maxGeneralityDistance%22%3A3%2C%22operator%22%3A%22or%22%2C%22senses%22%3A%5B{%22term%22%3A%22woman%22%2C%22synsetUri%22%3A%22http%3A%2F%2Fwww.w3.org%2F2006%2F03%2Fwn%2Fwn20%2Finstances%2Fsynset-woman-noun-1%22%2C%22_specializationType%22%3A%22org.insemtives.platform.unitn.commons.model.QueryTerm%22}%5D}
Any idea?
Assigning the ticket to Viktor
Yes, I confirm that the problem exists, I asked our search developers but given that today and tomorrow are holidays in Italy it might take some time to get the answer :)
As a side note, there are two extra items in the request. First, the "_specializationType" parameter of the query term is not required anymore (to be honest I don't know why did Sergey put it at all, maybe some legacy code when there were several classes for the query terms), second, the operator makes sense only if there are several query term, if there's only one then it can safely be omitted since there is only one single cloud in the reply so no clouds to merge or intersect.
The partial fix has been delivered, the max generality distance parameter now works for the single-word terms. The support for the multi-word terms is still to be added.