FAQ

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

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

For authenticating the end-users into a Muse Proxy Application the following authentication modules are available:
–ProxyLoginModuleUserPassword. Performs User Name/Password authentication.
–ProxyLoginModuleIP. Performs IP authentication based on client machine IP.
–ProxyLoginModuleLDAP. Performs authentication against a LDAP Server.
–ProxyLoginModuleFTP. Performs authentication against a FTP Server. The FTP authentication module supports NONE, SSL or TLS connection encryptions.
– ProxyLoginModuleIMAP. Performs authentication against a IMAP Server. The IMAP authentication module supports NONE, SSL or TLS connection encryptions.
–ProxyLoginModuleSQL. Performs authentication against an SQL Server through Java Database Connectivity (JDBC). The SQL authentication module supports NONE, SSL or TLS connection encryptions.
–ProxyLoginModuleReferer.Performs authentication against the client’s referer URL.

You can read more about the authentication in a Muse Proxy Application in the “Muse Proxy.pdf” manual, chapter “Authentication of a Muse Proxy Application”.