Query Behaviour on Dev Version

[mgrani]

Although the query still are not perfect, the new query behaviour often returns strange results.

Below you see a screenshot of the ada lovelace wikipedia page. The term feather (for sure not a very good query term here) yields to a number of bee images that come from Europeana. This means that Europeana queries no longer apply the main topic concept and thus return more irrelevant results. The same applies also to other providers like KIM Portal. Is there a possibility to do unit testing for main topic related issues?

The second issue i often encounter is, that one provider returns nearly all results and thus biases the results strongly in one direction. From my point of view, diverse results should cover a range of different data provider. As a rough model I would say that the number of items returned by the data providers with the most hits should be max 2 times as many as the number of items of the data provider with the second most hits (just as an rough guess).

[hziak]

the dev server produced following query according to the stats:
"(Ada AND (programming AND language)) OR Anatomy OR River OR (Physical AND disability) OR Bird OR (Bed AND rest) OR Fly OR Art OR Compass OR Headache OR Measles OR (Assistive AND cane) OR Steamboat OR Feather"
but everything should be configured correctly on the server and
if i called directly with a main topic specified it logs queries like this:
"(Mozart) AND (Nannerl OR (Kleine AND nacht AND musik))"

Are your sure that the frontend is setting a main topic?
It appears that for every query the dev server receives there is no main topic specified.
The stable server seems to receive querys with main topic.

[hziak]

Regarding the second issue: This issue should be hopefully resolved and can be tested at
EExcessDemo before we deploy it. Feedback is appreciated. (but it's still work in progress)

[mgrani]

Thanks Hermann.

Jörg, could you take a look if it is a client side issue?

[schloett]

The main topic is set by the client. Payload of the POST-request:

{"contextKeywords":[{"text":"Augusta Leigh","uri":"http://dbpedia.org/resource/Augusta_Leigh","type":"Person","isMainTopic":true},{"text":"Ada (programming language)","uri":"http://dbpedia.org/resource/Ada_(programming_language)","type":"Misc","isMainTopic":false},{"text":"Lord Byron","uri":"http://dbpedia.org/resource/Lord_Byron","type":"Person","isMainTopic":false},{"text":"Anatomy","uri":"http://dbpedia.org/resource/Anatomy","type":"Misc","isMainTopic":false},{"text":"River","uri":"http://dbpedia.org/resource/River","type":"Misc","isMainTopic":false},{"text":"Physical disability","uri":"http://dbpedia.org/resource/Physical_disability","type":"Misc","isMainTopic":false},{"text":"Bird","uri":"http://dbpedia.org/resource/Bird","type":"Misc","isMainTopic":false},{"text":"Bed rest","uri":"http://dbpedia.org/resource/Bed_rest","type":"Misc","isMainTopic":false},{"text":"Fly","uri":"http://dbpedia.org/resource/Fly","type":"Misc","isMainTopic":false},{"text":"Claire Clairmont","uri":"http://dbpedia.org/resource/Claire_Clairmont","type":"Person","isMainTopic":false},{"text":"Art","uri":"http://dbpedia.org/resource/Art","type":"Misc","isMainTopic":false},{"text":"Compass","uri":"http://dbpedia.org/resource/Compass","type":"Misc","isMainTopic":false},{"text":"Headache","uri":"http://dbpedia.org/resource/Headache","type":"Misc","isMainTopic":false},{"text":"Measles","uri":"http://dbpedia.org/resource/Measles","type":"Misc","isMainTopic":false},{"text":"Assistive cane","uri":"http://dbpedia.org/resource/Assistive_cane","type":"Misc","isMainTopic":false},{"text":"Charles Babbage","uri":"http://dbpedia.org/resource/Charles_Babbage","type":"Person","isMainTopic":false},{"text":"Steamboat","uri":"http://dbpedia.org/resource/Steamboat","type":"Misc","isMainTopic":false},{"text":"Feather","uri":"http://dbpedia.org/resource/Feather","type":"Misc","isMainTopic":false}],"origin":{"module":"c4/searchBar","clientType":"EEXCESS_DEV/chrome-extension","clientVersion":"1.5.1","userID":"6CED5A36-1C39-4326-A95A-1F0CE153D7AA"},"loggingLevel":0,"numResults":"80"}

[hziak]

Thx for the request, now i know what the problem is.
Since the type of the main topic is set to "person" it's not considered as normal query term anymore but as term for the special fields in the partners that support these fields.
I will try to find a solution for that. Will lead to a redeployment of the dev-server within this week.