Changes between Version 73 and Version 74 of Discovery/DiscoveryWebServiceMEDIN

Timestamp:

09/11/11 13:16:42 (10 years ago)

Author:

mnagni

Comment:

Updated with Exact Phrase Search and explict definition of AND,OR,NOT as reserved words

Discovery/DiscoveryWebServiceMEDIN

@@ -96 +96 @@
 
 ===== !TermSearch =====
-!TermSearch is a full-text search invoked on a specific target field in the discovery database. !TermSearch elements must have an attribute named "id" with an integer value representing the order to be considered in complex multi termed searches, usually though "id" can be considered as the number of the !TermSearch element.  If more than one !TermSearch element is used then all subsequent !TermSearch elements (excluding the first) must also have an "operator" attribute describing the relationship between the !TermSearch element in question with preceding !TermSearchs (the order of these is given by the "id" attribute).  Acceptable values for the operator attribute are "AND", "OR" and "NOT".
+!TermSearch is a full-text search invoked on a specific target field in the discovery database. !TermSearch elements must have an attribute named "id" with an integer value representing the order to be considered in complex multi termed searches, usually though "id" can be considered as the number of the !TermSearch element.  If more than one !TermSearch element is used then all subsequent !TermSearch elements (excluding the first) must also have an "operator" attribute describing the relationship between the !TermSearch element in question with preceding !TermSearchs (the order of these is given by the "id" attribute).  Acceptable values for the operator attribute are "AND", "OR" and "NOT" which are to be considered reserved words (for an exception see "Exact Phrase Search" paragraph below).
 
 Child elements <!Term> and <!TermTarget> should be populated as follows:
@@ -186 +186 @@
 
 ..and so on.
+
+
+===== Exact Phrase Search =====
+
+If an "exact phrase" search is needed the sentence has to be wrapped with two double quotes. Consequently if the user is looking for looking for 'Snow and rain' should be translated to ""Snow and rain""
+
+{{{
+<m:Term>""Snow and rain""</m:Term>
+}}}
 
 ===== Spatial searching : <!SpatialOperator> and <!BoundingBox> =====