Most Popular

Load More


The “:” character is a keyword in Muse syntax, used to search on the simple search formfor a complex query (example: to search on both author and title on the simple search form : “:CREATOR john AND :TITLE design”). Note that words that contain a “:” character can be searched if the text is in quotes (ex: “asthma:”).

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 remapped to the default attribute. The default attribute to be used for unsupported search attributes is defined in the Source Package PMF (PreMappingFile) file.

The reason why the search is not automatically starting when using the following search form:

is that there are no SP targets provided on which to perform the search.

Specifying/providing the SP targets can be done in 2 ways:

a) Setting in the application the default sources for the searches. This can be done using the Muse Console for Customer Support or Muse Console for Applications Administration as follows:
– login into the Muse Console for Customer Support or Muse Console for Applications Administration, select the desired application and click on the “Setup and Organize Sources” left menu item;
– go to “Organize Sources” left menu item and click on the “Update Interface” sub-item;
– in the right section of the “Update Interface” panel check the Source Packages that should be selected as default from each defined group;
– press the Update button; this will update the interface for the default language with the selected Source Packages; if you want to specify default selected Source Packages for other languages available than the default one, select the desired language from the “Language” combobox and make the same operations, e.g. select the sources and press the “Update” button.
b) Extend the HTML form presented below and include the targets on which to perform the search. For example if one wants to perform the search on the XX and YY SPs, add the following lines inside the form:

The dbList parameter is documented in the “2.0 Use of MusePeer – Auto-logon and Pass-through mechanisms” chapter from the Muse Web Bridge Communication Interface.pdf document.

The Source Packages installed in a Muse application can be seen in the Muse Administrator Consoles (Muse Console for Customer Support or Muse Console for Applications Administration) as follows:
– login into the Muse Console for Customer Support or Muse Console for Applications Administration console, select the desired application and click on the “Setup and Organize Sources” left menu item;
– the source IDs (dbList values) are in the “ID” column of the sources listing.

Additionally, another parameter could be added: “reuseSession=true” parameter (also documented in the above mentioned chapter) in the HTML form so that the sessions are reused for consecutive usage of the passthrough form from the same end-user. For this add int he form above:

Muse maintains a set of internally recognized index labels or attributes for use in queries. These are recognized within the Muse Query Syntax by the parser on input and stored internally. When a search statement is translated for a particular Source, the internal forms are translated (using a Source-specific Translator) into the actual indices the Source recognizes. This preserves a mapping for all the indices the user is allowed to use to all the indices the particular Source recognizes.

An internal index can be mapped to one or more Source indices. If it is mapped to no Source index and it appears in a search statement then it will use either the default index (almost universally “keyword”) or it produces an “unsupported query” error message for that Source. This behavior is controlled by the designer.

The internal indices can be exposed to users in many different ways, and can be given labels which will be meaningful to users. If an index is not made available through the search interface (human or machine) then it will not be recognized by the parser, and an “unsupported query” error will be returned for that search.

The internal indices are based on the Standard Dublin Core set of bibliographic descriptor fields. Some remain as indices, others are treated as limiters.

Standard Internal Indices

  • Keyword
  • Title
  • Subject
  • Creator

Standard Internal Limiters

  • Date
  • Type
  • Language
  • Format

Other Indices which are nonstandard and are only available for special use

  • Contributor
  • Coverage
  • Description
  • Identifier
  • Publisher
  • Source
  • Relation
  • Rights

This a known/intermittent behavior of some old browsers, like Internet Explorer 6.

By default, Muse HTTP Server closes client sockets as soon as it finishes sending out the response, in order to recycle sockets as soon as possible. However, there are some problems with certain browsers (like IE6) that send data after the socket was closed by the server. Since the socket was already closed by the server, the browser displays the “The page cannot be displayed” error instantly.

To work around this, Muse Http Server was adapted to wait a configurable amount of time after sending all the data back to the browser and before closing the socket. This amount of time is configurable through thesocketCloseDelay parameter for the desired Connector in ${MUSE_HOME}/http/conf/contexts.xml file. The value for socketCloseDelay parameter is specified in milliseconds.

Note: This value represents the time that the server waits before closing down the socket to the client. Setting a too high value for this parameter can degrade performance of the Muse Http Server. In general, this value should never be set higher than 100 milliseconds.

To activate the socket close delay for Muse HTTP Server please follow the next steps:

1. Stop the Muse HTTP Server;
2. Edit the "${MUSE_HOME}/http/conf/contexts.xml" file and add the following line:

after the lines (port 8000 below can be any port that Muse HTTP Server was set to run on):

3. start the Muse HTTP Server.

If the problem still persists, a tunning is necessary till a proper value is found (please consider the note above):
1. Shutdown the Muse HTTP Server;
2. Change the value of the “socketCloseDelay” parameter;
3. Start the Muse HTTP Server;
4. Run new tests.

Categories: Muse Search, Sources

Load More