Glossary
-
A technology layer that automates operations on unstructured information for cross-enterprise applications. ACI enables an automated and compatible business-to-business, peer-to-peer infrastructure. The ACI allows enterprise applications to understand and process content that exists in unstructured formats, such as email, Web pages, Microsoft Office documents, and IBM Notes.
-
A server component that runs on the Autonomy Content Infrastructure (ACI).
-
An ACL is metadata associated with a document that defines which users and groups are permitted to access the document.
-
A request sent to an ACI server.
-
A domain controller for the Microsoft Windows operating system, which uses LDAP to authenticate users and computers on a network.
-
A process that searches for information about a specific topic. An administrator can create agents for users or allow users to create their own agents.
-
An index in IDOL Server that stores agents and profiles.
-
An IDOL Server field that stores Boolean agents (Boolean or Proximity expressions). You can then query IDOL Server with text and an AgentBoolean field to return categories whose Boolean agent matches this text. QMS rules use Boolean agents for matching queries.
-
A rule that allows you to specify a list of disallowed words for queries, and removes any terms that appear on this list.
-
A rule that modifies a query to include extra FieldText criteria, for example to boost the relevance of certain results.
-
A QMS rule that allows you to add a specified result to a specified position in a query results list.
-
The IDOL Server component that manages categorization and clustering.
-
The IDOL Server component that manages users and communities.
-
A type of query that allows you to search for documents that match the concept that your query text defines, rather than matching the particular keywords in your text. See also: query.
-
An IDOL component (for example File System Connector) that retrieves information from a local or remote repository (for example, a file system, database, or Web site).
-
Connector Framework Server processes the information that is retrieved by connectors. Connector Framework Server uses KeyView to extract document content and metadata from over 1,000 different file types. When the information has been processed, it is sent to an IDOL Server or Distributed Index Handler (DIH).
-
The IDOL Server component that manages the data index and performs most of the search and retrieval operations from the index.
-
DAH distributes actions to multiple copies of IDOL Server or a component. It allows you to use failover, load balancing, or distributed content.
-
An IDOL Server index that stores content data. You can customize how data is stored in the data index by configuring appropriate settings in the IDOL Server configuration file.
-
An IDOL Server data pool that stores indexed information. The administrator can set up one or more databases, and specifies how data is fed to the databases. By default IDOL Server contains the databases Profile, Agent, Activated, Deactivated, News, and Archive.
-
DIH allows you to efficiently split and index extremely large quantities of data into multiple copies of IDOL Server or the Content component. DIH allows you to create a scalable solution that delivers high performance and high availability. It provides a flexible way to batch, route, and categorize the indexing of internal and external content into IDOL Server.
-
See: DAH
-
A query that returns a document or set of documents that you want to promote. See Also: static promotions.
-
See: XML
-
Fields define different parts of content in IDOL documents, such as the title, content, and metadata information.
-
A syntax string that defines a matching criteria in FieldText.
-
A type of query that searches for particular content in a particular document field. See also: query, field.
-
A rule that modifies query text to replace specific terms with a more general term. For example, flower is a hypernym of rose and lily.
-
A rule that modifies query text to include terms that are specific instances of the original terms. For example, poodle and labrador are hyponyms of dog.
-
The Intelligent Data Operating Layer (IDOL) Server, which integrates unstructured, semi-structured and structured information from multiple repositories through an understanding of the content. It delivers a real-time environment in which operations across applications and content are automated.
-
An IDOL Server component that accepts incoming actions and distributes them to the appropriate subcomponent. IDOL Proxy also performs some maintenance operations to make sure that the subcomponents are running, and to start and stop them when necessary.
-
A structured file format that you can index into IDOL Server. You can use a connector to import files into this format, or you can manually create IDX files.
-
The IDOL Server data index contains document content and field information for analysis and retrieval.
-
An IDOL Server command to index data, or to maintain or manipulate the data index.
-
Fields that IDOL Server processes linguistically when it stores them. Store fields that contain text which you want to query frequently as Index fields. IDOL Server applies stemming and stop word lists to text in Index fields before it stores them, which allows IDOL Server to process queries for these fields more quickly. Typically DRETITLE and DRECONTENT are fields that are set up as Index fields.
-
The process of storing data in IDOL Server. IDOL Server stores data in different field types (for example, index, numeric, and ordinary fields). It is important to store data in appropriate field types to ensure optimized performance.
-
An integrated security solution to protect your data. At the front end, authentication checks that users are allowed to access the system that contains the result data. At the back end, entitlement checking and authentication combine to ensure that query results contain only documents that the user is allowed to see, from repositories that the user has permission to access. For more information, refer to the IDOL Document Security Administration Guide.
-
The IDOL component that extracts data, including text, metadata, and subfiles from over 1,000 different file types. KeyView can also convert documents to HTML format for viewing in a Web browser.
-
Lightweight Directory Access Protocol. Applications can use LDAP to retrieve information from a server. LDAP is used for directory services (such as corporate email and telephone directories) and user authentication. See also: active directory, primary domain controller.
-
License Server enables you to license and run multiple IDOL solutions. You must have a License Server on a machine with a known, static IP address.
-
Also referred to as “links”. Terms in query text that are also contained in the result documents that IDOL Server returns for this query.
-
A server that manages access permissions for your users. It communicates with your repositories and IDOL Server to apply access permissions to documents.
-
A QMS rule that allows you to place a specified parametric field in a specified position in a list.
-
A server computer in a Microsoft Windows domain that controls various computer resources. See also: active directory, LDAP.
-
The agent index that stores QMS rules.
-
Targeted content that you want to display to users but that is not included in the search results, such as advertisements.
-
An ACI server that manipulates queries and results according to user-defined rules.
-
A document stored in the Promotion Agentstore that defines how QMS manages a query. Rules can return promotion documents, modify the original query, or modify the results of a query.
-
A string that you submit to IDOL Server, which analyzes the concept of the query and returns documents that are conceptually similar to it. You can submit queries to IDOL Server to perform several kinds of search, such as natural language, Boolean, bracketed Boolean, and keyword.
-
See: QMS
-
A string that is used to identify a document. This string might be a title or a URL, and allows IDOL to identify documents for retrieval, indexing, and deduplication.
-
Fields used to identify documents. At index time IDOL Server can use ReferenceType fields to eliminate duplicate copies of documents. At query time IDOL Server can use ReferenceType fields to filter results.
-
The similarity that a particular query result has to the initial query. IDOL Server assigns results a percentage relevance score according to how closely it matches the query criteria.
-
A rule that allows you to return results from a promotions query that are relevant to a particular role, department, or other user-defined characteristic.
-
A specific document or set of documents that you want to return as a promotion. See Also: dynamic promotions.
-
A rule that modifies query text to include terms that are synonymous with the original terms.
-
The process of adding extra information to documents. The tag might be a category, or entities returned from Eduction. Tagging usually adds a field to a document, which you can use to search by the name of a tag.
-
The basic entity that IDOL Server stores (for example, a word in a document after IDOL Server applies stemming).
-
An IDOL component that converts files in a repository to HTML formats for viewing in a Web browser.
-
A rule that allows you to specify a list of allowed words for queries, and to remove any terms that do not appear on this list.
-
A character that stands in for any character or group of characters in a query.
-
Extensible Markup Language. XML is a language that defines the different attributes of document content in a format that can be read by humans and machines. In IDOL Server, you can index documents in XML format. IDOL Server also returns action responses in XML format.
A
B
C
D
E
F
H
I
K
L
O
P
Q
R
S
T
V
W
X