FAQ

The difference in the Content Mining (CM) results is given by the difference in the results returned by the sources. Using “Full Text” limiters limits the number and the ‘quality’ (with regard to the CM) of the results returned by the search sources. The configuration of the module and the different results returned by the different searches are factors that limit the number of terms in the “Refine your results” window. We actually don’t display any term unless its threshold weight is above 3, which usually means that the term must be found at least 2-3 times in the returned records. Of course the limit can be lowered to 1 so that the CM always returns something, no matter the search, but the results will not always be meaningful with respect to the search query. It will also waste quite a lot of heap memory since we will have to keep more terms into the main memory until they are being sent to the browser to be displayed. Having many CM terms is less important than having only the relevant terms even if it means that there is only one relevant term. The CM process must be focused on quality and not quantity.

Muse has the possibility to control the behavior of searches in cases when queries having unsupported limiters are launched. By unsupported limiter, we mean that one wants to search a source for records between 2 dates, even if the native site does not support this (i.e., does not have this option).

The control is done by means of the of the “Stop If Limiter Not Supported” parameter. It is a property of the Search Module and can be set by:
– logging into the MCAA Muse Console;
– selecting the desired application;
– selecting “Application Modules” from the left panel;
– clicking on the “Search Module” link.

The “Stop If Limiter Not Supported:” field appears along with 2 values that can be set:
– “Stop If Limiter Not Supported:” field on YES – if the limiters are not supported, the search will stop and no records will be retrieved;
– “Stop If Limiter Not Supported:” field on NO – if the limiters are not supported the search will bring results (searching by default without any limiter) with the warning “Unsupported limiter(s): …”