Muse Search FAQ
Muse Search
$APPLICATION_HOME/www/application/searchOptions.db
file and/or the
– $APPLICATION_HOME/www/international/XYZ/application/searchOptions.db
file(s), where XYZ is the language code.
The line
Load More
Load More
Load More
Load More
Load More
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.
The procedure to change/remove the default sorting algorithm in an application (Muse 2.3.0.2. or above) is:
– log into the MCAA/MCCS,
– select an application,
– click Application Modules,
– click Ranking Keys,
– click Update Interface,
– select for which language to make the change,
– select the desired default ordering method/key (right side),
– click Update,
– click Close Window button.
Note that this applies for applications based on a MuseFoundation application template. To verify the changes relogin into the application.
For applications that are based on an older application template, the settings must be manually done because they are not compatible with the newer Muse admin consoles (MCAA/MCCS).
Below are the changes that must be done to configure the default sorting algorithm in applications based on older templates. Edit the
- $APPLICATION_HOME/www/application/searchOptions.db file and/or the
- $APPLICATION_HOME/www/international/XYZ/application/searchOptions.db file(s), where XYZ is the language code.
The line
which is equivalent to None (no ordering), must be replaced with:
or any other sorting key, such as:
– ICERankingKeyAuthor
– ICERankingKeyAuthorTitle
– ICERankingKeyDate
– ICERankingKeyField
– ICERankingKeyRelevance
– ICERankingKeyRetrieved
– ICERankingKeySource
– ICERankingKeyTitle
depending on the needes.
Load More
The procedure to change/remove the default sorting algorithm in an application (Muse 2.3.0.2. or above) is:
– log into the MCAA/MCCS,
– select an application,
– click Application Modules,
– click Ranking Keys,
– click Update Interface,
– select for which language to make the change,
– select the desired default ordering method/key (right side),
– click Update,
– click Close Window button.
Note that this applies for applications based on a MuseFoundation application template. To verify the changes relogin into the application.
For applications that are based on an older application template, the settings must be manually done because they are not compatible with the newer Muse admin consoles (MCAA/MCCS).
Below are the changes that must be done to configure the default sorting algorithm in applications based on older templates. Edit the
– $APPLICATION_HOME/www/application/searchOptions.db
file and/or the
– $APPLICATION_HOME/www/international/XYZ/application/searchOptions.db
file(s), where XYZ is the language code.
The line
which is equivalent to None (no ordering), must be replaced with:
or any other sorting key, such as:
– ICERankingKeyAuthor
– ICERankingKeyAuthorTitle
– ICERankingKeyDate
– ICERankingKeyField
– ICERankingKeyRelevance
– ICERankingKeyRetrieved
– ICERankingKeySource
– ICERankingKeyTitle
depending on the needes.