FAQ
FAQ by Product
Most Popular
The .cpb file describes the search capabilities of a source. The .pmf is the pre-mapping file that allows administrators to map search/index attributes that apply before the Muse ISR stylesheet is used to format the search for the source (thus “Pre”-mapping). The .cpb file lists all the search indexes and Boolean operators which are supported by the Source (whatever the actual, native syntax of the attribute). It is also a place where other source capabilities could be added later for easy import into the Muse InfoBase. The search limiter sets are one example. The .pmf file provides a mapping from one attribute in ISR to one attribute in translator. The .pmf mapping is TO an attribute which is handled into the ISR translator. All of the attributes handled (supported) in the ISR translator have been automatically extracted and recorded into the appropriate section in .cpb file. By default, the PMF files map unsupported attributes to keyword.
Load More
Latest
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.
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 Muse Source Packages.
Why am I obtaining different results in two cosecutive for the same search on same Source Packages?
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, sends these records to ICE which further sends records to the Muse application to be displayed.
So, the records come and are displayed in the Muse application www interface in the order in which they are received from the native sites and parsed. From one search to another the native sites might have different speeds of response and also the order in which the connectors are launched and run into execution may differ because they are run in parallel as threads.
Considering this, it is possible that at a second search performed in a Muse application, using the same term and on the same sources, to show records in different order.
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.
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 Muse Source Packages.