<%@ Page CodeBehind="WSK-Search.aspx.cs" Language="c#" AutoEventWireup="false" Inherits="v1_7.text.WSK_Search" %> Searching for Documents

Searching for Documents

The LexisNexis® Web Services Kit search operations are used to locate and retrieve documents from the LexisNexis information warehouse. 

The most-often used search operation, Search lets users locate specific documents within the LexisNexis information warehouse by specifying a series of restrictions that indicate where to look (which sources) and what to look for (query). These restrictions can specify items such as...

Some users may not need or want to define this level of precision in their search request. Therefore, the Search operation contains a searchMethod option which allows your user-agent application to choose among several different types of searching method:

SearchMethod

Description

Boolean Equivalent to the Power Search / Terms and Connectors form on Nexis.com, the Boolean selection is for users who need to create custom searches to locate specific pieces of information. It lets them use special search term connectors (AND, OR, W/n, etc.) to specify specific search term relationships.
Freestyle Equivalent to the Power Search / Natural Language form on Nexis.com, the Freestyle selection is for users who want to search in plain English, without having to use any special terms or connectors. The natural language feature's document relevance ranking gives quick access to the most pertinent documents in the search results.
EasySearch Equivalent to the Easy Search form on Nexis.com, the EasySearch selection is for users not familiar with advanced searching methods on LexisNexis. Easy Search automatically creates a natural language or terms and connectors search based on the query input.
MoreLikeSelectedText Equivalent to MoreLikeSelectedText search feature on Lexis.com, MoreLikeSelectedText allows up to 1000 characters to be taken from the text of an existing document and used as the query text for a new search, finding closely related documents to the chosen text.
MatchOnPhrase Similar to the Freestyle search described above, except that at least one of the query terms must appear in the document for it to appear in the result set.
MatchOnAllWords Similar to the MatchOnPhrase search described above except that all of the query terms must appear in the document for it to appear in the result list.
MatchOnAnyWords Similar to the MatchOnPhrase search described above but with the dynamic phrase option set to not affect the scoring of the documents in the result list.

The Search operation also lets your user-agent applications specify how the search results set should be delivered. They can specify a specific display format (a cite listing, the full document text, etc.), the markup method (in XHTML or using a more descriptive markup such as NITF), the sort order (by date, by relevance, or by the source's recommended method), and the range of documents within the results set to be delivered.

The response message will contain the search results in the requested format. Most applications initially request that the documents be delivered in a list (such as the Cite format) because it contains summary information about each document found. The brief excerpt from the document makes it easier for a user to decide whether or not the document in question is relevant to his/her needs. Each search result item will also include a unique document identifier (valid for a short period of 48 hours or less) that is used to retrieve the full text of a requested document.

Other frequently-used Search operations include:

Click here to return to the API Reference Guide for a complete list of available Search operations.