Add file for 1.6 branch.

[Evergreen-DocBook.git] / opac / searchmethodology.xml

diff --git a/opac/searchmethodology.xml b/opac/searchmethodology.xml
new file mode 100644 (file)
index 0000000..98c3fff
--- /dev/null
+++ b/opac/searchmethodology.xml
@@ -0,0 +1,46 @@
+<?xml version='1.0' encoding='UTF-8'?>\r
+<chapter xmlns="http://docbook.org/ns/docbook" xmlns:xi="http://www.w3.org/2001/XInclude"\r
+           xmlns:xl="http://www.w3.org/1999/xlink" version="5.0" xml:id="catalogue-search-methodology">\r
+       <title>Search Methodology</title>\r
+        <simplesect xml:id="catalogue-search-methodology-stemming">\r
+                <title>Stemming</title><indexterm><primary>search methodology</primary><secondary>stemming</secondary></indexterm>\r
+                <para>A search for <emphasis>dogs</emphasis> will also return hits with the word\r
+                      <emphasis>dog</emphasis> and a search for <emphasis>parenting</emphasis> will return\r
+                   results with the words <emphasis>parent</emphasis> and<emphasis> parental</emphasis>.\r
+                   This is because the search uses stemming to help return the most relevant results. That\r
+                   is, words are reduced to their stem (or root word) before the search is\r
+                   performed.</para>\r
+\r
+                <para>The stemming algorithm relies on common English language patterns - like verbs ending\r
+                   in <emphasis>ing</emphasis> - to find the stems. This is more efficient that looking up\r
+                   each search term in a dictionary and usually produces desirable results. However, it\r
+                   also means the search will sometimes reduce a word to an incorrect stem and cause\r
+                   unexpected results. To prevent a word or phrase from stemming, put it in\r
+                   double-quotes.</para>\r
+\r
+                <para>Understanding how stemming works can help you to create more relevant searches, but\r
+                   it is usually best not to anticipate how a search term will be stemmed. For example,\r
+                   searching for <emphasis>gold compass</emphasis> does not return for <emphasis>golden\r
+                      compass</emphasis> because the search does not recognize <emphasis>gold</emphasis> as\r
+                   a stem of <emphasis>golden</emphasis>.</para>\r
+      </simplesect>\r
+      <simplesect>\r
+                <title>Truncation</title><indexterm><primary>search methodology</primary><secondary>truncation</secondary></indexterm>\r
+                <para>Truncation is not currently supported in Evergreen. </para>\r
+      </simplesect>\r
+      <simplesect xml:id="catalogue-search-methodology-order-of-results"\r
+                xreflabel="Order of Results">\r
+                <title> Order of Results </title><indexterm><primary>search methodology</primary><secondary>order of results</secondary></indexterm>\r
+                <para>By default, the results are listed in order of relevance, similar\r
+                   to a search engine like Google. The relevance is determined using a number of factors,\r
+                   including how often and where the search terms appear in the item description, and\r
+                   whether the search terms are part of the title, subject, author, or series. The results\r
+                   which best match your search are returned first rather than results appearing in\r
+                   alphabetical or chronological order.</para>\r
+                <para>In the <guilabel>Advanced Search </guilabel>screen, you may select to order the\r
+                   search results by relevance, title, author, or publication date before you start the\r
+                   search. You can also re-order your search results using the Sort Results dropdown list\r
+                   on the search result screen. </para>\r
+      </simplesect>\r
+</chapter>\r
+\r