Novell NETWARE 6-DOCUMENTATION Manual page 2103

Making Good Use of Document Fields
174 Getting Results with Novell Web Services
Number of concurrent active indexing jobs
Other functions being performed by your server
Adjusting any of these values can have a significant impact on the
performance of your search services.
As a general guideline, use the fastest CPU possible and include as much
RAM as possible. Although the duration of each user query is very short,
while it is active it consumes an average of 500 KB of memory. Memory
consumption varies widely while the indexer is calculating the final search
results list, depending on the number of possible search results.
Also, try to schedule the regeneration of your indexes during off-peak hours.
That way, they won't interfere with normal user searches. (See
Site Management" on page
If you find that your users frequently enter search words such as to, of, a, the,
in, etc., you might want to consider removing these words before they are
submitted to the Web Search engine.
HINT:
A stop-words processor is available in the Enterprise version of Web
Search. Contact your local Novell resale representive for more information.
A document field is any tag or field in any document that helps to identify the
document's contents. A document field might be a title, heading, or paragraph
contained in an H1, TITLE, or META tag within an HTML document.
Web Search is designed to take advantage of document fields in order to
improve the accuracy and speed of search results.
By design, Web Search always indexes all document fields in many document
types, including HTML, PDF, Word, WordPerfect, XML, etc. Users can then
constrain searches to the contents of any document field.
As a Web Search administrator, you can use document fields to restrict search
results to certain products, categories, authors, titles, keywords, or any other
content belonging to a document field.
This is done using the /fieldname=search_criteria query parameter.
HINT:
You might consider sending this information as hidden data using the
&filter= query parameter.
155.)
"Automating