Query Behaviour on Dev Version #34
Description
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).