Results > Search and Retrieve > Field Text Search > Field Specifiers for Advanced Restrictions

Field Specifiers for Advanced Restrictions
 
contains a value in a BitFieldType field where the specified bit is set
contains multiple instances, whose values include at least one match for each of the specified strings or numeric values
contains a specified reference in a ReferenceMemoryMappedType field recursively to a maximum number of times
TERM, TERMALL, TERMEXACT, TERMEXACTALL, TERMEXACTPHRASE, TERMPHRASE
Fields whose Value Falls Within a Specific Alphabetical Range
ARANGE
The ARANGE field specifier (case sensitive) allows you to find documents in which a specified field contains a term that falls within the inclusive alphabetical range of two terms you specify.
FieldText=ARANGE{yourTerms}:yourFields
where,
 
is two terms separated by a comma (there must be no space before or after the comma). A document returns only if one of yourFields contains a term that falls within the inclusive alphabetical range of the specified terms.
It uses unicode tables to determine alphabetical order. This means that non-7-bit ASCII characters (α, ä, å, ç, δ, ê, ë, ø, ö, ü, û, ß, ÿ and so on.) come after z in the alphabet.
is one or more fields. A document returns only if it contains one of these fields, and if this field contains a term that falls within the inclusive alphabetical range of yourTerms.
Examples:
FieldText=ARANGE{aardvark,alligator}:ANIMAL
The ANIMAL field must contain a value that alphabetically falls between aardvark and alligator. If the ANIMAL field contains the value aardvark, ant, anteater, antelope or alligator, the document returns. If the ANIMAL field contains the value armadillo, it does not return.
FieldText=ARANGE{bear,buffalo}:ANIMAL:TIER
The ANIMAL or TIER field must contain a value that alphabetically falls between bear and buffalo. If the field contains the value bear, bee, Biene, bird or buffalo, the document returns. If the ANIMAL field contains the value Büffel or chipmunk, it does not return.
FieldText=ARANGE{dog,.}:ANIMAL AND ARANGE{.,cat}:PET
The ANIMAL field must contain a value that alphabetically falls after dog, and the PET field must contain a value that alphabetically falls before cat.
Fields With a Non-zero Value for Bitwise AND
You can use these field specifiers (case sensitive) to return documents with fields whose value result in a nonzero value when a bitwise AND operation is carried out against a specified value.
BITAND
The BITAND field specifier (case sensitive) allows you find documents with a field whose integer value does not result in 0 when a bitwise AND operation is carried out between this value and an integer value you specify.
FieldText=BITAND{yourInteger}:yourBitFields>
where,
 
is an integer. A document returns only if one of yourBitFields contains a value that results in a nonzero value when a bitwise AND operation is carried out between this value and the specified integer.
is one or more fields. A document returns only if it contains one of these fields, and if this field contains an integer that results in a nonzero value when a bitwise AND operation is carried out between it and yourInteger.
If you want to specify multiple fields, separate them with colons (there must be no space before or after a colon).
Example:
FieldText=BITAND{128}:BitField
The binary representation of the integer value 128 is compared with the binary representations of the integer values that BitField fields in IDOL server contain. Only documents whose BitField values result in a nonzero value when they are compared to the binary representation of 128 return.
If a document's BitField, for example, contains the integer value 129, it returns, while a document whose BitField contains the value 127 does not return.
Field value comparison:
 
 
BITANDHEX
The BITANDHEX field specifier (case sensitive) allows you find documents with a field whose hexadecimal string value does not result in zero when a bitwise AND operation is carried out between this value and a hexadecimal string you specify.
FieldText=BITANDHEX{yourHexString}:yourBitFields
where,
 
is a hexadecimal string. A document returns only if one of yourBitFields contains a value that result in a nonzero value when a bitwise AND operation is carried out between this value and the specified hexadecimal string.
is one or more fields. A document returns only if it contains one of these fields, and if this field contains a hexadecimal string that results in a nonzero value when a bitwise AND operation is carried out between it and yourHexString.
Example:
FieldText=BITANDHEX{7F}:BitField
The binary representation of the hexadecimal value 7F is compared with the binary representations of the hexadecimal values that BitField fields in IDOL server contain. Only documents whose BitField values result in a nonzero value when they are compared to the binary representation of 7F return.
If a document's BitField, for example, contains the hexadecimal value C0, it returns, while a document whose BitField contains the hexadecimal value 80 does not return.
Field value comparison:
 
 
BITANDOFFHEX
The BITANDOFFHEX field specifier (case sensitive) allows you find documents with a field whose hexadecimal string value does not result in zero when a bitwise AND operation is carried out between this value and an offset hexadecimal string you specify.
FieldText=BITANDOFFHEX{NN,yourHexString}:yourBitFields
where,
 
is the number of 16 bit chunks by which the value in yourHexString and in yourBitFields is shifted before the bitwise AND operation is carried out (this allows you to store sparse bit masks more efficiently).
is a hexadecimal string. A document returns only if one of yourBitFields contains a value that result in a nonzero value when a bitwise AND operation is carried out between this value and the specified hexadecimal string.
is one or more fields. A document returns only if it contains one of these fields, and if this field contains a hexadecimal string that results in a nonzero value when a bitwise AND operation is carried out between it and yourHexString.
If you want to specify multiple fields, separate them with colons (there must be no space before or after a colon).
Example:
FieldText=BITANDOFFHEX{01,0a001}:BitOffField
The binary representation of the hexadecimal value 01,0a001 is compared with the binary representations of the hexadecimal values that BitOffField fields in IDOL server contain. Only documents whose BitOffField values result in a nonzero value when they are compared to the binary representation of 01,0a001 (after they have been shifted left by one 16-bit chunk) return.
If the BitOffField, for example, contains the value 1,bc01, the document returns, while a document whose BitOffField contains the value 0,5ffeffff does not return.
Field value comparison:
 
 
Fields that Contain BitFieldType Information
BITSET
The BITSET field specifier (case sensitive) allows you find documents with a BitFieldType field that contains a value where the specified bit is set. This allows you to search for documents that belong to a particular set of documents.
 
NOTE You can use the BITSET field specifier only for BitFieldType fields.
FieldText=BITSET{yourBitSets}:yourFields
where,
 
are one or more BitFieldType fields. A document returns only if it contains one of these fields, and if this field contains a value where the bit corresponding to yourBitSets is set.
Examples:
FieldText=BITSET{0,4}:BitField
This example matches any document where the binary representation of the hexadecimal value contained in BitField has the bit set (the binary digit is 1) for set 0 or set 4.
For example, if a document has a BitField containing the hexadecimal value A4, it does not match the query. The binary representation is 10100100, where the bits for set 0 and 4 are both 0, so the document is not part of these sets.
If the document has a BitField containing the hexadecimal value A8, it does match the query. The binary representation is 10101000, where the bit for set 4 is a 1, so the document is part of set 4.
FieldText=BITSET{2}:BitField AND BITSET{15}:BitField
The binary representation of the hexadecimal value contained in BitField must have the bits switched on for both sets 2 and 15.
For example, if a document has a BitField containing the hexadecimal value B110, it does not match the query. The binary representation is 1011000100010000, where the bit is set to 1 for set 15, but not for set 2.
If the document has a BitField containing the hexadecimal value B114 it matches the query. The binary representation is 1011000100010100, where the bit is set to 1 for both set 15 and set 2.
Fields whose Values are Boolean Agents
BOOLEANFIELD
The BOOLEANFIELD field specifier (case sensitive) allows you to find documents in which a specified Boolean agent field contains an expression that matches text you specify. A Boolean agent is a Boolean or Proximity expression that legacy technologies use to categorize documents.
 
NOTE If you are using a Query action, Autonomy recommends that you use the AgentBooleanField action parameter rather than the BOOLEANFIELD field specifier. However, if you want to match more than one Boolean agent field, you must use the BOOLEANFIELD field specifier.
FieldText=BOOLEANFIELD{yourText}:yourFields
where,
 
is text. A document returns only if one of yourFields contains a Boolean or Proximity expression that matches the specified text.
is one or more Boolean agent fields. A document returns only if it contains one of these fields, and if this field contains a Boolean or Proximity expression that matches yourText.
For example:
BOOLEANFIELD{The cat sat on the mat}:MyFirstBooleanField:MySecondBooleanField
Any document that has a MyFirstBooleanField or MySecondBooleanField field that contains a Boolean or Proximity expression that matches the specified text returns. For example, the Boolean/Proximity expressions cat AND mat, cat OR mat, cat BEFORE mat and cat DNEAR1 sat could match The cat sat on the mat. Therefore, documents that contain any of these Boolean/Proximity expressions are returned.
Documents whose MyFirstBooleanField or MySecondBooleanField fields contain, for example, cat AND mat AND dog or mat BEFORE cat are not returned.
Fields that are a specified distance from a specified point
DISTCARTESIAN
The DISTCARTESIAN field specifier allows you to find documents whose X/Y position is within a specified distance from a specified point.
FieldText=DISTCARTESIAN{coordX,coordY,dist}:X:Y
where,
 
 
 
Example:
FieldText=DISTCARTESIAN{10,11,5}:X:Y
This example matches all documents whose (X,Y) position is within a distance of 5 units of the point (10,11).
DISTSPHERICAL
FieldText=DISTSPHERICAL{lat,long,dist}:LATFIELD:LONGFIELD
where,
 
 
 
Example:
FieldText=DISTSPHERICAL{37.75,-122.4,20}:LAT:LONG
This example matches all documents whose position is within a 20 kilometer radius of San Francisco (37.75N,122.4W). The latitude and longitude position of a document in this example is contained in the fields LAT and LONG, respectively.
Fields That Do Not Exist or Contain No Value
EMPTY
The EMPTY field specifier (case sensitive) allows you to find documents in which a specified field does not exist or contains no value.
FieldText=EMPTY{}:yourFields
where,
 
Examples:
FieldText=EMPTY{}:ID
A document must not contain an ID field or hold no value within its ID field to return.
FieldText=EMPTY{}:ID:Name
A document must not contain an ID or Name field, or hold no value in its ID or Name field to return.
Specific Fields, Irrespective of their Value
EXISTS
The EXISTS field specifier (case sensitive) allows you to find documents that contain a specified field even if this field contains no value.
FieldText=EXISTS{}:yourFields
where,
 
Examples:
FieldText=EXISTS{}:ID
A document must contain an ID field to return.
FieldText=EXISTS{}:ID:NAME
A document must contain an ID or NAME field (or both) to return.
Fields whose values are similar to a specified string
FUZZY
The FUZZY field specifier (case sensitive) allows you to find documents in which a specified field contains a term that is similar to a specified term or phrase.
FieldText=FUZZY{yourTerms}:yourFields
where,
 
is one or more terms (or phrases). A document returns only if one of these terms (or phrases) is similar to a string in one of yourFields.
Fieldtext queries which include commas and braces within the query have specific percent-encoding requirements. For information about percent-encoding, see FieldText.
is one or more fields. A document returns only if it contains one of these fields, and if the value in this field is similar to one of yourTerms.
Example:
FieldText=FUZZY{Bisiness News,Arkive}:DRETITLE
The DRETITLE field value must be similar to the term Bisiness News or Arkive for the document to return. (A document whose DRETITLE field contains Business News returns, while a document whose DRETITLE field contains Document Arkive does not).
At least one field instance matches a specified string or number
You can use these field specifiers (case sensitive) to return documents with multiple instances of the same fields and at least one field instance contains a specified string or number.
MATCHALL
The MATCHALL field specifier (case sensitive) allows you to find documents in which a specified field occurs in multiple instances, and in which there is at least one match among those instances for each of a set of strings that you specify.
 
NOTE You can optimize the field specifier speed by restricting the field to the MatchType property type.
FieldText=MATCHALL{yourStrings}:yourField
where,
 
is one or more strings. A document returns only if all these strings have exact matches among the instances of yourField. Separate the strings with commas (there must be no space before or after a comma).
Fieldtext queries which include commas and braces within the query have specific percent-encoding requirements. For information about percent-encoding, see FieldText.
is the name of the field to match against. A document returns only if it contains the field and only if all yourStrings are matched at least once in various instances of the field.
Examples:
FieldText=MATCHALL{Archive,Web,docs}:DIRECTORY
The DIRECTORY fields must include at least the values Archive and Web and docs for the document to return as a result.
FieldText=MATCHALL{Smith,Garcia,Lee}:SURNAME
The values Smith, Garcia, and Lee must all have matches in the SURNAME fields for the document to return as a result.
FieldText=MATCHALL{Smith%5C, John, Garcia%5C, Joaquin}:FULLNAME
The values Smith, John and Garcia, Joaquin must both have matches in the FULLNAME fields for the document to return as a result.
EQUALALL
The EQUALALL field specifier (case sensitive) allows you to find documents in which a specified field occurs in multiple instances, and in which there is at least one value among those instances that is equal to each of a set of numeric values that you specify.
 
NOTE You can optimize the field specifier speed by restricting the field to the NumericType property type.
FieldText=EQUALALL{yourValues}:yourNumericField
where,
 
is one or more numeric values. A document returns only if all these values occur among the instances of yourNumericField. Separate the numbers with commas (there must be no space before or after a comma).
is the name of the field to match against. A document returns only if it contains the field and only if all yourValues are matched at least once in various instances of the field.
Example:
FieldText=EQUALALL{32,98.6,212}:FAHRENHEIT
The FAHRENHEIT fields must include at least the values 32, 98.6, and 212 for the document to return as a result.
FieldText=EQUALALL{1999,2000,2001}:YEAR
The values 1999, 2000, and 2001 must all appear in YEAR fields for the document to return as a result.
All Field Instances Match a Specified String or Number
You can use these field specifiers (case sensitive) to return documents with multiple instances of the same fields and all field instances contain a specified string or number.
MATCHCOVER
The MATCHCOVER field specifier (case sensitive) allows you to find documents in which the values in all instances of a specified field have matches in the set of values provided in the specifier. In other words, the specifier must “cover” all instances of the field. A search using MATCHCOVER is slower than one using MATCH.
 
NOTE You can optimize the field specifier speed by restricting the field to the MatchType and CountType property types. You must specify both property types.
FieldText=MATCHCOVER{yourStrings}:yourField
where,
 
is one or more strings. A document returns only if the value in each of its instances of yourField matches one of the strings in yourStrings. Separate the strings with commas (there must be no space before or after a comma).
Fieldtext queries which include commas and braces within the query have specific percent-encoding requirements. For information about percent-encoding, see FieldText.
1.
Example:
FieldText=MATCHCOVER{Confidential,Secret,TopSecret,FBI}:SECURITYLEVEL
For a document to return as a result, its SECURITYLEVEL fields must not contain any values that are not in the specified list. For example, if a document includes a SECURITYLEVEL field with the value MI5, it does not return. (If a document has no SECURITYLEVEL field at all, it returns.)
EQUALCOVER
The EQUALCOVER field specifier (case sensitive) allows you to find documents in which the values in all instances of a specified field are found in the set of values provided in the specifier. In other words, the specifier must cover all instances of the field.
 
NOTE You can optimize the field specifier speed by restricting the field to the NumericType and CountType property types. You must specify both property types.
FieldText=EQUALCOVER{yourValues}:yourField
where,
 
is one or more numeric values. A document returns only if the value in each of its instances of yourField equals one of the values in yourValues. Separate the numbers with commas (there must be no space before or after a comma).
Fieldtext queries which include commas and braces within the query have specific percent-encoding requirements. For information about percent-encoding, see FieldText.
1.
Example:
FieldText=EQUALCOVER{9,10,11,12}:GRADELEVEL
For a document to return as a result, its GRADELEVEL fields must have no values that are not in the specified list. For example, if a document includes a GRADELEVEL field with the value 8, it does not return. (If a document has no GRADELEVEL field, it returns.)
Fields that Contain a Specified ReferenceMemoryMappedType Field
The MATCHRECURSE field specifier matches documents containing a specified reference in a ReferenceMemoryMappedType field recursively to a maximum number of times. You must restrict this field specifier to a single ReferenceMemoryMappedType field. It has the following syntax:
action=query&fieldtext=MATCHRECURSE{Ref,RecurseNumber}:yourField
where,
 
is the maximum number of times to recursively return references using the value of the ReferenceMemoryMappedType field.
is the name of the ReferenceMemoryMappedType field.
For example, let us say PARENT is defined as a ReferenceMemoryMapped field. The query
action=query&fieldtext=MATCHRECURSE{MyRef,1}:PARENT
matches the document with reference MyRef (parent) and documents whose PARENT field contains MyRef (children). The query
action=query&fieldtext=MATCHRECURSE{MyRef,2}:PARENT
matches the document with reference MyRef (parent), documents whose PARENT field contains MyRef (children), and documents whose PARENT field contains the references in the returned child documents (grandchildren).
Fields that do not contain a specified value
NOTMATCH
The NOTMATCH field specifier (case sensitive) allows you to find documents in which at least one instance of the specified fields contains a value that does not match the specified string.
If there are one or more instances of a particular field in the document, the document returns as long as at least one instance does not contain any of the specified strings, even if another instance of the field does match. The document does not return if all instances of the specified fields contain an exact match of one of the specified strings.
FieldText=NOTMATCH{yourStrings}:yourFields
where,
 
is one or more strings. A document returns only if at least one instance of one of yourFields contains a value that is not an exact match for these strings.
Fieldtext queries which include commas and braces within the query have specific percent-encoding requirements. For information about percent-encoding, see FieldText
is one or more fields. A document returns only if it contains one of these fields, and if the value in at least one instance of the field does not exactly match any of yourStrings.
For example:
FieldText=NOTMATCH{cat}:ANIMAL
At least one instance of the ANIMAL field must have a value other than cat for the document to return as a result.
For example, if a document contains only:
#DREFIELD ANIMAL="cat"
then it does not return as a result.
However, if the document contains:
#DREFIELD ANIMAL="cat"
#DREFIELD ANIMAL="dog"
 
Then it returns as a result, as one of the ANIMAL fields does not contain the value cat.
If you want to find documents in which the specified string is not present in any instance of the specified field, use the MATCH specifier with the Boolean operator NOT. For example, FieldText=NOT+MATCH{cat}:ANIMAL does not return any documents that have a ANIMAL field with the value cat, even if there are other ANIMAL fields with different values.
Related Topics 
*
NOTSTRING
The NOTSTRING field specifier (case sensitive) allows you to find documents in which at least one instance of the specified fields contains a value that does not contain any of the specified strings as a substring.
If there are one or more instances of a particular field in the document, the document returns as long as at least one instance does not contain any of the specified strings, even if another instance of the field does contain the string. The document does not return if all instances of the specified fields contain one of the specified strings as a substring.
FieldText=STRING{yourStrings}:yourFields
where,
 
is one or more strings. A document returns only if at least one instance of one of yourFields contains a value that is not a substring of any of these strings.
Fieldtext queries which include commas and braces within the query have specific percent-encoding requirements. For information about percent-encoding, see FieldText.
is one or more fields. A document returns only if it contains one of these fields, and if the value in at least one instance of the field does not contain any of yourStrings as a substring.
For example
FieldText=NOTSTRING{cat,dog}:ANIMAL:TOPIC
At least one instance of the ANIMAL or TOPIC field value must contain a value that does not contain the substring cat or dog for the document to return.
For example, if a document contains only:
#DREFIELD ANIMAL="old cat"
or
#DREFIELD TOPIC="dogs like playing catch "
#DREFIELD ANIMAL="dog"
 
Then it does not return as a result.
However, if the document contains:
#DREFIELD TOPIC="dogs have trouble catching mice"
#DREFIELD ANIMAL="dog"
#DREFIELD ANIMAL="mouse"
 
Then it returns as a result, as one of the ANIMAL fields does not contain the substring cat or dog.
If you want to find documents in which the specified string is not present in any instance of the specified field, use the STRING specifier with the Boolean operator NOT. For example, FieldText=NOT+STRING{cat,dog}:ANIMAL does not return any documents that have a ANIMAL field with the substring cat or dog, even if there are other ANIMAL fields with different values.
Related Topics 
*
NOTWILD
The NOTWILD field specifier (case sensitive) allows you to find documents in which at least one instance of the specified field contains a value that does not match the specified wildcard string.
If there are one or more instances of a particular field in the document, the document returns as long as at least one instance does not contain the specified string, even if another instance of the field does match. The document does not return if all instances of the specified fields contain the specified string.
If the query does not contain any wildcard characters (? or *) then the NOTWILD field specifier acts in the same way as the NOTMATCH field specifier.
FieldText=NOTWILD{yourStrings}:yourFields
where,
 
is one or more strings containing wildcards. A document returns only if at least one instance of one of yourFields does not contain any of these strings.
Fieldtext queries which include commas and braces within the query have specific percent-encoding requirements. For information about percent-encoding, see FieldText
is one or more fields. A document returns only if it contains one of these fields, and if the value in at least one instance of the field does not contain any of yourStrings.
For example:
FieldText=NOTWILD{passi*incarnata}:Climbers:Plants
At least one instance of a document's Climbers or Plants field must contain a value which does not contain a phrase that begins with passi and ends with incarnata (for example, passionflower incarnata or passiflora incarnata) for this document to return as a result.
For example, if a document contains only:
#DREFIELD Climbers="passiflora incarnata"
or
#DREFIELD Climbers="passiflora incarnata"
#DREFIELD Plants="passionflower incarnata"
Then it does not return as a result.
However, if the document contains:
#DREFIELD Climbers="passiflora incarnata"
#DREFIELD Plants="passionflower incarnata"
#DREFIELD Climbers="bindweed"
Then it returns, as one of the Climbers fields contains a value that does not match the wildcard string passi*incarnata.
If you want to find documents in which the specified string is not present in any instance of the specified field, use the WILD specifier with the Boolean operator NOT. For example, FieldText=NOT+WILD{passi*incarnata}:Climbers does not return any documents that have a Climbers field with a phrase that begins with passi and ends with incarnata, even if there are other Climbers fields with different values.
Related Topics 
*
*
Fields That Contain Coordinates Within a Specified Area
POLYGON
The POLYGON field specifier (case sensitive) allows you to find documents whose X/Y position is within a specified polygonal shape.
FieldText=POLYGON{coordX,coordY,coordX,coordY,...}:X:Y
where,
 
are the coordinates for one of the vertices. Specify an x,y pair of coordinates for each vertex of the polygon working either clockwise or counterclockwise around the polygon.
You can specify a concave polygon, but the edges must not cross themselves. You can specify coordinates with decimal numbers.
Y
 
NOTE You must always specify two fields, in the order X:Y. You can specify more than one pair of fields in the form X1:Y1:X2:Y2 and so on.
For example:
FieldText=POLYGON{1,1,-1,1,0,-2,1,-1}:XPOS:YPOS
This example matches all documents whose (X,Y) position is within the quadrilateral with vertices at (1,1), (–1,1), (0,–2), (1,–1).
Fields That Contain a Specified String
You can use these field specifiers (case sensitive) to return documents with fields that contain a specified string.
STRING
The STRING field specifier (case sensitive) allows you to specify one or more strings of which one must be contained as a substring in a specified field.
FieldText=STRING{yourStrings}:yourFields
where,
 
is one or more strings. A document returns only if one of these strings is a substring of the value in one of yourFields.
Fieldtext queries which include commas and braces within the query have specific percent-encoding requirements. For information about percent-encoding, see FieldText
is one or more fields. A document returns only if it contains one of these fields, and if the value in this field is contains one of yourStrings as a substring.
Examples:
FieldText=STRING{cat,dog}:ANIMAL
The ANIMAL field value must contain the substring cat or dog for the document to return. If the ANIMAL field, for example, has the value scattering, the document returns.
FieldText=STRING{old cat}:ANIMAL:TOPIC
The ANIMAL or TOPIC field value must contain the substring old cat for the document to return. If a document's ANIMAL field, for example, has the value old cat, old caterpillar or bold cats, the document returns.
FieldText=STRING{autonomy.com}:COMPANY
The COMPANY field value must contain the substring autonomy.com for the document to return. If the COMPANY field, for example, has the value autonomy.com or http://www.autonomy.com/content/home, the document returns.
FieldText=STRING{a\,b}:MISC
The MISC field value must contain the substring a,b for the document to return. If the MISC field, for example, has the value a,b or a,b,c, the document returns.
STRINGALL
The STRINGALL field specifier (case sensitive) allows you to specify one or more strings, which must all be contained as a substring in a specified field.
FieldText=STRINGALL{yourStrings}:yourFields
where,
 
If you want to specify multiple strings, separate them with commas (there must be no space before or after a comma). Fieldtext queries which include commas and braces within the query have specific percent-encoding requirements. For information about percent-encoding, see FieldText.
is one or more fields. A document returns only if it contains one of these fields, and if the value in this field contains yourStrings as substrings.
Examples:
FieldText=STRINGALL{cat,dog}:ANIMAL
The ANIMAL field value must contain the substrings cat and dog for the document to return. If the ANIMAL field, for example, has the value grooming cats and dogs or doggedly scattering seeds, the document returns.
FieldText=STRINGALL{old cat,young dog}:ANIMAL:TOPIC
The ANIMAL or TOPIC field value must contain the substrings old cat and young dog for this document to return. If the ANIMAL field, for example, has the value old cat chases young dog, or young.doggedly chasing bold cats, the document returns.
FieldText=STRINGALL{a\,b,e\,f}:MISC
The MISC field value must contain the substring a,b and e,f for this document to return. If a document's MISC field, for example, has the value a,b,c,d,e,f or 0=e,fx 1=da,ba, the document returns.
SUBSTRING
The SUBSTRING field specifier (case sensitive) allows you to return documents whose field value is a substring of a specified string (or equal to a specified strings).
FieldText=SUBSTRING{yourStrings}:yourFields
where,
 
is one or more strings. A document returns only if one of yourFields contains a substring of one of the specified strings.
If you want to specify multiple strings, separate them with commas (there must be no space before or after a comma). Fieldtext queries which include commas and braces within the query have specific percent-encoding requirements. For information about percent-encoding, see FieldText.
is one or more fields. A document returns only if it contains one of these fields, and if the value in this field is a substring of yourStrings.
If you want to specify multiple fields, separate them with colons (there must be no space before or after a colon).
Examples:
FieldText=SUBSTRING{Telecommunications,Technology}:SECTOR
The SECTOR field must contain a string that is a substring of Telecommunications or Technology. If the SECTOR field, for example, has the value Telecom or Technology, the document returns. If the SECTOR field has the value Latest Technology, the document does not return.
The ANIMAL field value must contain a substring of scattering or doggedly for the document to return. If the ANIMAL field, for example, has the value cat or dog, the document returns.
Fields Whose Values Match Specific Terms or Phrases
You can use these field specifiers (case sensitive) to return documents in which specified fields contain specified terms or phrases.
TERM
The TERM field specifier (case sensitive) allows you to find documents with a specified field whose value contains a conceptual match of one or more terms you specify. A conceptual match exists if a term you specify matches a term in a specified field after it has been stemmed.
 
NOTE If the language you use does not match the DefaultLanguageType specified in the IDOL server configuration file, add the LanguageType parameter to your query action (see Specify the Language Type of a Query).
FieldText=TERM{yourTerms}:yourFields
where,
 
is one or more terms. A document returns only if one of yourFields contains a value that includes a term which conceptually matches of one of the specified terms.
To specify multiple terms, separate them with commas (there must be no space before or after a comma). Fieldtext queries which include commas and braces within the query have specific percent-encoding requirements. For information about percent-encoding, see FieldText.
is one or more fields. A document returns only if it contains one of these fields, and if a term in this field conceptually matches one of yourTerms.
Examples:
FieldText=TERM{shopping,centers}:DRETITLE
The DRETITLE field must contain a term that conceptually matches shopping or centers for the document to return. If the DRETITLE field, for example, has the value shop the document returns, while if it has the value bookshopping, it does not return.
FieldText=TERM{training,football}:ITEM:PRODUCT
TheITEM or PRODUCT field must contain a term that conceptually matches trainers or football for the document to return. If the ITEM or PRODUCT field, for example, has the value train or footballers, the document returns, while if it has the value trainer or soccer, it does not return.
TERMALL
The TERMALL field specifier (case sensitive) allows you to find documents with a specified field whose value contains conceptual matches of several terms you specify. A conceptual match exists if the terms you specify match terms in a specified field after they have been stemmed.
 
NOTE If the language you are using does not match the DefaultLanguageType specified in IDOL server's configuration file, add the LanguageType parameter to your query command (see Specify the Language Type of a Query).
FieldText=TERMALL{yourTerms}:yourFields
where,
 
is multiple terms. A document returns only if one of yourFields contains a value that includes terms which conceptually match the specified terms.
Separate the terms with commas (there must be no space before or after a comma). Fieldtext queries which include commas and braces within the query have specific percent-encoding requirements. For information about percent-encoding, see FieldText.
is one or more fields. A document returns only if it contains one of these fields, and if a term in this field conceptually matches one of yourTerms.
Examples:
FieldText=TERMALL{shopping,centers}:DRETITLE
The DRETITLE field value must contain a term that conceptually matches shopping or centers for the document to return. If the DRETITLE field, for example, has the value town center shop the document returns.
FieldText=TERMALL{walk,climb}:DRETITLE:TITLE
The DRETITLE or TITLE field value must contain a term that conceptually matches walking or climbing for the document to return. If the DRETITLE or TITLE field, for example, has the value hill walking and rock climbing the document returns.
TERMEXACT
The TERMEXACT field specifier (case sensitive) allows you to find documents with a specified field that contains an exact match of any of the terms you specify.
 
NOTE If the language you are using does not match the DefaultLanguageType specified in IDOL server's configuration file, add the LanguageType parameter to your query command (see Specify the Language Type of a Query).
FieldText=TERMEXACT{yourTerms}:yourFields
where,
 
is one or more terms. A document returns only if one of yourFields contains a value that exactly matches one of the specified terms.
To specify multiple terms, separate them with commas (there must be no space before or after a comma). Fieldtext queries which include commas and braces within the query have specific percent-encoding requirements. For information about percent-encoding, see FieldText.
is one or more fields. A document returns only if it contains one of these fields, and if this field contains an exact match of one of yourTerms.
Examples:
FieldText=TERMEXACT{help,helped}:DRETITLE
The DRETITLE field value must contain the term help or helped for the document to return. If the DRETITLE field, for example, has the value helps or helping, the document does not return.
FieldText=TERMEXACT{Word,Excel}:FILE:DATEI
The FILE or DATEI field value must contain the term Word or Excel for the document to return. If the FILE or DATEI field, for example, has the value WordPerfect, the document does not return.
TERMEXACTALL
The TERMEXACTALL field specifier (case sensitive) allows you to find documents with a specified field that contains an exact match of all terms you specify.
 
NOTE If the language you are using does not match the DefaultLanguageType specified in IDOL server's configuration file, add the LanguageType parameter to your query command (see Specify the Language Type of a Query).
FieldText=TERMEXACTALL{yourTerms}:yourFields
where,
 
is multiple terms. A document returns only if one of yourFields contains exact matches of the specified terms.
Separate the terms with commas (there must be no space before or after a comma). Fieldtext queries which include commas and braces within the query have specific percent-encoding requirements. For information about percent-encoding, see FieldText.
is one or more fields. A document returns only if it contains one of these fields, and if this field contains an exact match of all yourTerms.
Examples:
FieldText=TERMEXACTALL{rabbits,eating,carrots}:DRETITLE
This query returns only documents whose DRETITLE field contains all the specified terms (in their specified form). For example, a document whose DRETITLE field has the value Rabbits like eating carrots or The carrots were there but the rabbits ate all the cabbage return as a result, while a document with a field that contains Rabbits like to eat a carrot each day does not return.
FieldText=TERMEXACTALL{flour,milk,eggs}:DRETITLE:TITLE
This query returns only documents whose DRETITLE or TITLE field contains all the specified terms (in their specified form). For example, a document whose DRETITLE or TITLE field has the value Most cake recipes include milk, eggs and flower return as a result, while a document with a field that contains Use a cup of milk, two cups of flour and one egg does not return.
TERMEXACTPHRASE
The TERMEXACTPHRASE field specifier (case sensitive) allows you to return documents in which a specified field contains an exact match of a phrase specified by you. IDOL server matches your phrase before it applies stemming (it does not remove stop words). It ignores any punctuation in the specifier or field.
 
NOTE If the language you are using does not match the DefaultLanguageType specified in IDOL server's configuration file, add the LanguageType parameter to your query command (see Specify the Language Type of a Query).
FieldText=TERMEXACTPHRASE{yourPhrase}:yourFields
where,
 
is a phrase. A document returns only if one of yourFields contains an exact match of the specified phrase.
is one or more fields. A document returns only if it contains one of these fields, and if this field contains an exact match of yourPhrase.
Examples:
FieldText=TERMEXACTPHRASE{Batman! and Robins}:FILM
A document whose FILM field contains Showing now, Batman and Robin's film, returns as a result, while a document whose FILM field contains Showing now, 'Batman and Robin' the movie does not return.
FieldText=TERMEXACTPHRASE{gift horse }:DRETITLE:TITLE
A document whose DRETITLE or TITLE field contains looking a gift horse in the mouth return as a result, while a document whose DRETITLE or TITLE field contains the gift horse's mouth had rotting teeth does not return.
TERMPHRASE
The TERMPHRASE field specifier (case sensitive) allows you to return documents in which a specified field contains a conceptual match of a phrase you specify. IDOL server matches your phrase after it applies stemming (it does not remove stop words). It ignores any punctuation in the specifier or field.
 
NOTE If the language you are using does not match the DefaultLanguageType specified in IDOL server's configuration file, add the LanguageType parameter to your query command (see Specify the Language Type of a Query).
FieldText=TERMPHRASE{yourPhrase}:yourFields
where,
 
is a phrase. A document returns only if one of yourFields contains a conceptual match of the specified phrase.
is one or more fields. A document returns only if it contains one of these fields, and if this field contains a conceptual match of yourPhrase.
Examples:
FieldText=TERMPHRASE{Batman! and Robins}:FILM
A document whose FILM field contains Showing now: 'Batman and Robin', returns as a result.
FieldText=TERMPHRASE{gift horse }:DRETITLE:TITLE
A document whose DRETITLE or TITLE field contains the gift horse's mouth had rotting teeth returns.