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

Field Specifiers for Common Restrictions
 
Fields Whose Value Exactly Matches One or More Strings
You can use the following field specifier to return documents with fields that contain a specified string.
MATCH
The MATCH field specifier (case sensitive) finds documents in which a specified field contains a value that exactly matches a specified string.
FieldText=MATCH{yourStrings}:yourFields
where,
 
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 exactly matches one of yourStrings.
Examples:
FieldText=MATCH{Archive,Web,docs}:DB:DATABASE
The DB or DATABASE field must have the value Archive, Web, or docs for the document to return as a result.
FieldText=MATCH{Premier league}:DB
The DB field must have the value Premier League for the document to return as a result.
FieldText=MATCH{0-226-10389-7}:ISBN
The ISBN field must have the value 0-226-10389-7 for the document to return as a result.
Fields that Contain a Number
You can use these field specifiers (case sensitive) to return documents with fields that contain numbers. To optimize the processing time of queries for fields that contain numbers, store them as numeric fields in IDOL server during the indexing process.
Related Topics 
*
EQUAL
The EQUAL field specifier (case sensitive) allows you to find documents in which a specified field contains a number that matches one of the numbers specified by you.
FieldText=EQUAL{yourNumbers}:yourFields
where,
 
is one or more numbers. A document returns only if one of yourFields contains one of these numbers.
is one or more fields. A document returns only if it contains one of these fields, and if this field contains one of yourNumbers.
Examples:
FieldText=EQUAL{1234567890123}:ACCOUNT:KONTO
The ACCOUNT or KONTO field must contain the number 1234567890123 for the document to return.
FieldText=EQUAL{3.9,4.9,7}:ID
The ID field must contain the number 3.9, 3.90, 4.9, 4.90, 7, or 7.0 for the document to return.
GREATER
The GREATER field specifier (case sensitive) allows you to find documents in which a specified field contains a number that is greater than a number you specify.
FieldText=GREATER{yourNumber}:yourFields
where,
 
is a number. A document returns only if one of yourFields contains a number that is greater than this number.
is one or more fields. A document returns only if it contains one of these fields, and if the number in this field is greater than yourNumber.
Examples:
FieldText=GREATER{66}:ID
The ID field must contain a number greater than 66 for the document to return.
FieldText=GREATER{5.59}:PRICE:PREIS
The PRICE or PREIS field must contain a number greater than 5.59 for the document to return.
LESS
The LESS field specifier (case sensitive) allows you to find documents in which a specified field contains a number that is smaller than a number you specify.
FieldText=LESS{yourNumber}:yourFields
where,
 
is a number. A document returns only if one of yourFields contains a number that is smaller than this number.
is one or more fields. A document returns only if it contains one of these fields, and if the number in this field is smaller than yourNumber.
Examples:
FieldText=LESS{66}:ID
The ID field must contain a smaller number than 66 for the document to return.
FieldText=LESS{5.59}:PRICE:PREIS
The PRICE or PREIS field must contain a smaller number than 5.59 for the document to return.
NOTEQUAL
The NOTEQUAL field specifier (case sensitive) allows you to find documents in which a specified field contains a number that does not match a number you specify.
FieldText=NOTEQUAL{yourNumber}:yourFields
where,
 
is a number. A document returns only if one of yourFields does not contain this number.
is one or more fields. A document returns only if it contains one of these fields, and if this field does not contain yourNumber.
Examples:
FieldText=NOTEQUAL{1234567890123}:ACCOUNT:KONTO
The ACCOUNT or KONTO field must not contain the number 1234567890123 for the document to return.
FieldText=NOTEQUAL{3.9}:ID
The ID field must not contain the number 3.9 for this document to return.
NRANGE
The NRANGE field specifier (case sensitive) allows you to find documents in which a specified field contains a number that falls within the inclusive range of two numbers you specify.
FieldText=NRANGE{yourNumbers}:yourFields
where,
 
is two numbers, separated by a comma (there must be no space before or after the comma). A document returns only if one of yourFields contains a number that falls within the inclusive range of the specified numbers (including decimal numbers).
is one or more fields. A document returns only if it contains one of these fields, and if this field contains a number that falls within the inclusive range of yourNumbers.
Examples:
FieldText=NRANGE{1,99}:CODE
The CODE field must contain a number between 1 and 99 (inclusive) for the document to return.
FieldText=NRANGE{1234567890123,2345678901234}:ACCOUNT:KONTO
The ACCOUNT or KONTO field must not contain a number between 1234567890123 and 2345678901234 (inclusive) for the document to return.
FieldText=NRANGE{36.5,42.3}:CODE
The CODE field must contain a number between 36.5 and 42.3 (inclusive) for the document to return.
FieldText=NRANGE{10:}:CODE
The CODE field must contain a number equal to or above 10 for the document to return.
Fields that Contain a Date
You can use these field specifiers (case sensitive) to return documents with fields that contain dates.
 
NOTE To optimize the processing time of queries for fields that contain dates, store them as numeric date fields in IDOL server during the indexing process.
Related Topics 
*
GTNOW
The GTNOW field specifier (case sensitive) allows you to find documents in which a specified field contains a date that is greater than the AUTNDATE (that is all documents that were indexed with dates after the current time).
FieldText=GTNOW{}:yourFields
where,
 
is one or more fields. A document returns only if it contains one of these fields, and if this field contains a date that is greater than the AUTNDATE (that is all documents that were indexed with dates after the current time).
Examples:
FieldText=GTNOW{}:TIME
The TIME field must contain a date that is greater than the AUTNDATE (that is all documents that were indexed with dates after the current time) for the document to return.
FieldText=GTNOW{}:TIME:DATE
The TIME or DATE field must contain a date that is greater than the current time (that is all documents that were indexed with dates after the current time) for the document to return.
LTNOW
The LTNOW field specifier (case sensitive) allows you to find documents in which a specified field contains a date that is smaller than the AUTNDATE (that is all documents that were indexed with dates before the current time).
FieldText=LTNOW{}:yourFields
where,
 
is one or more fields. A document returns only if it contains one of these fields, and if this field contains a date that is smaller than the current time.
Examples:
FieldText=LTNOW{}:*/TIME
The TIME field must contain a date that is smaller than the AUTNDATE (that is all documents that were indexed with dates before the current time) for the document to return.
FieldText=LTNOW{}:TIME:DATE
The TIME or DATE field must contain a date that is smaller than the AUTNDATE (that is all documents that were indexed with dates before the current time) for the document to return.
RANGE
The RANGE field specifier (case sensitive) allows you to find documents in which a specified field contains a date that falls within the inclusive range of two dates you specify.
FieldText=RANGE{yourDates}:yourFields
where,
 
is two dates separated by a comma (there must be no space before or after the comma). A document returns only if one of yourFields contains a date that falls within the inclusive time span of the specified dates. You can use the formats in Table 3 to specify each date.
is one or more fields. A document returns only if it contains one of these fields, and if this field contains a date that falls within the inclusive range of yourDates.
 
Table 3 Date formats  
A date. For example, 1/3/05, 23/12/99 or 10/07/40.
If the year is a number less than 40, it is read as a year in the 2000s. If the year is a number between 40 and 99, it is read as a year in the 1900s. For example, 1/02/1 is read as February first 2001, while 01/3/40 is read as March first 1940.
A date. For example, 1/3/2005, 23/12/1999 or 10/07/1940.
For example, –1 specifies yesterday's date, 0 specifies today's date, 1 specifies tomorrow's date, 2 specifies two days from now (the current date plus two) and so on.
Ns
For example, –60s specifies one minute ago, –900s specifies 15 minutes ago, –3600s specifies one hour ago and so on. 60s specifies one minute from now, 900s specifies 15 minutes from now, 3600s specifies one hour from now and so on.
Ne
For example, 1012345000e specifies 22:56:40 on January 29th 2002.
If you enter a full stop for the first point in time you are specifying, the beginning of the time period is unrestricted (so the period ranges up to the specified date, including any date before the specified date).
If you enter a full stop for the second points in time you are specifying, the end of the time period is unrestricted (so the period ranges from the specified date, including any date after the specified date).
Examples:
FieldText=RANGE{01/01/90,1/1/01}:DATE
The DATE field must contain a date between 01/01/1990 and 1/1/2001 for the document to return.
FieldText=RANGE{01/01/02,01/01/2003}:DATE:DATUM
The DATE or DATUM field must contain a date between 01/01/2002 and 01/01/2003 for the document to return.
FieldText=RANGE{-14,-7}:DATE
The DATE field must contain a date 14 to 7 days before the current date for the document to return.
FieldText=RANGE{0,1}:DATE
The DATE field must contain today's or tomorrow's date (which is possible, for example, if the document originates from a different time zone or if the field contains an expiry date) for the document to return.
FieldText=RANGE{01/01/99,.}:DATE:FECHA
The DATE or FECHA field can contain any date after 01/01/1999 for the document to return.
FieldText=RANGE{.,10/10/04}:DATE
The DATE field can contain any date before 10/10/2004 for the document to return.
FieldText=RANGE{-172800s,-1}:DATE
The DATE field must contain a time between 48 and 24 hours ago.
FieldText=RANGE{198765e,.}:DATE
The DATE field must contain a date between 198765 seconds after the epoch and the current time.
Fields Whose Value Matches Wildcard Strings
WILD
The WILD field specifier (case sensitive) allows you to find documents in which a specified field contains a string that matches a specified wildcard string.
If the query does not contain any wildcard characters (? or *) then the WILD field specifier acts in the same way as the MATCH field specifier.
FieldText=WILD{yourStrings}:yourFields
where,
 
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 one of yourStrings.
Examples:
FieldText=WILD{*.html,*.htm}:URL
The URL field value must end with .html or .htm for this document to return as a result.
FieldText=WILD{passi*incarnata}:Climbers:Plants
The Climbers or Plants field value must 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.
FieldText=WILD{*www.autonomy.com*.txt}:PATH
The PATH field value must contain a path that contains www.autonomy.com and ends with .txt (for example, http://www.autonomy.com/files/doc.txt) for the document to return as a result.
FieldText=WILD{wom?n }:Clothes
The Clothes field value must contain a word that matches the specified wildcard string (for example, woman or women) for this document to return as a result.