FAQ Category: Sources

The message “Global InfoBase error: UnknownHostException:factory.museglobal.com” clearly states that the factory.museglobal.com host cannot be solved by the DNS servers configured on the Muse server. This is not a Muse problem, but a network/server configuration issue. This may lead to other side efects, like populating the Status values of the Source Packages with “Not working” values.

This a normal behavior considering how Muse works and how different sites on Internet respond to consecutive searches. A search performed in a Muse application starts at the ICE server level a number of connectors, each working on a native data service. Each such connector, as it searches the native data service and obtains records,…

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),…

1) At the application level: This can be done by changing the value of the “User Concurrent Sessions” field from the application’s properties using the Muse Admin Console. The file from within the application which contains this setting is $APPLICATION_HOME/profile.xml, field: <MAX_USER_CONCURRENT_SESSIONS>. Note that this field sets the maximum number of simultaneous sessions for one…

“Total number of unique sources from all applications” is the total number of SPs from all applications listed in the report. In this case, unique means that if the same SP appears in many applications it is counted only once. Also they are counted no matter if they are part or not of any group…

Here are some details about the query remapping mechanism in Muse: if a search on one or more search attributes is performed on a Muse Source Package, the ICE Search module analyses the Source Package CPB (capabilities) file and all the search attributes included in query which are not present in the CPB file are…

If a search with limiters is performed on a Muse Source Package then all the limiters which are not supported by that Source Package are ignored – only supported ones are processed. There will never be an unsupported query caused by the presence of some search limiters in the query. This is valid for all…

The reason why the search is not automatically starting when using the following search form: <form name=”logonForm” action=”http://www.museserver.com/muse/servlet/MusePeer” target=”_blank” method=”get” onsubmit=”return beforeSubmit()”> <input type=”text” name=”query” size=”30″ value=””/> <input type=”submit” name=”submit” value=”Search”/> <input type=”hidden” name=”action” value=”logon” /> <input type=”hidden” name=”userID” value=”applicationid” /> <input type=”hidden” name=”userPwd” value=”applicationpassword” /> <input type=”hidden” name=”languageCode” value=”” /> <input type=”hidden” name=”templateFile” value=”/passThrough.html”…

The Group ID may contain alphabetic, numeric or underscore characters. The first character in an Group ID must be alphabetic (NOT numeric or an underscore). No other characters are allowed. There is no limitation on the number of characters the ID can have. Note: A Group ID cannot match any Source ID in the same…

Elsevier does not permit HTTP access to their resources through federated search products. For federated search Elsevier provides specialized APIs for which we have the following Source Packages: ScienceDirectRESTXML, ScienceDirectRESTXMLBooks, ScienceDirectRESTXMLJournals and ScopusRESTXML. Arrangements with Elsevier for this access must be handled by you (the partner), or by your customer, following the steps below: Install…