About Fields

Data passes to the IDOL Content component (for example, from IDOL connectors) in the form of IDX or XML fields. Content stores all the fields that it receives so that you can search any field by using FieldText queries. To optimize Content performance, you can specify how it processes and stores the fields it receives.

You can associate fields with special properties in the IDOL Content component configuration file. For example, you can instruct Content to treat these fields (or documents that contain them) in a specific way or read specific information from them.

You can associate a field with more than one property, as long as the properties do not clash.

You can assign the following properties to fields.

ACLType Fields that hold access control lists (ACLs).
AlwaysMatchType Fields that queries always match when they are present with a non-empty value.
AutnRankType Fields that hold the document rank.
BitFieldCompressed The index for BitFieldType fields is compressed.
BitFieldMaxMemoryKB The maximum memory (in KB) to allocate for each associated PropertyFieldCSVs field that has the BitFieldType property.
BitFieldType Fields that hold information on document sets. See BitFieldType Fields.
CountType The number of occurrences of the associated fields are stored in a fast look-up table in memory to optimize matching of the fields when you use the MATCHCOVER and EQUALCOVER FieldText specifiers.
DatabaseType Fields that hold the database that documents belongs to.
DateType Fields that hold the date of documents.
DocumentTrackingType Fields that hold the tracking IDs of documents.
ExpireAfterDelay An offset, in hours, to add to the expiration date in the associated ExpireDateType field.
ExpireDateType Fields that hold the expiration dates of documents.
FieldCheckType A field that occurs in a large number of documents and holds a value that is frequently used to restrict query results.
FlattenIndexType Fields that originate from hierarchically structured documents and whose content is stored as one level.
HiddenType Fields whose content is hidden.
HighlightType If fields contain terms that match a query, these terms are highlighted. See Highlight Fields.
Index Fields that are stored as Index fields. See Index Fields.
IndexNumbers Restrict the numbers to index for IndexNumbersType fields.
IndexNumbers1MaxLength Restrict the length of pure numeric terms for IndexNumbersType fields.
IndexNumbers2MaxLength Restrict the length of alphanumeric terms for IndexNumbersType fields.
IndexNumbersType Fields to index as numeric or mixed-alphanumeric fields.
InvertedAgentType Fields that are contained within inverted agents.
LangDetectType Fields to use for automatic language detection when AutoDetectLanguagesAtIndex is set to True.
LanguageType Fields that hold the language type of documents.
MatchType Fields to store in a fast look-up table in memory to optimize matching of the fields when you use the following FieldText specifiers: BIASVAL, EQUALCOVER, MATCH, MATCHALL, MATCHCOVER, STRING, WILD.
MemCachedType Fields to store in a memory cache.
NonReversibleType Fields whose content is not line-reversed on index, even if the document is detected as being right-to-left Arabic or Hebrew.
NumericDateType Fields that contain numeric dates and are stored in a fast look-up table in memory to optimize matching of the fields when you use FieldText specifiers. See NumericDateType Fields.
NumericIntegerOnly Fields with the NumericType property store signed 64-bit integer-only values, rather than doubles.
NumericNormalMaxMem The maximum memory (in KB) to allocate for each associated PropertyFieldCSVs field that has one of these properties: NumericDateType, NumericType, ParametricType.
NumericType Fields that contain numeric data and are stored in a fast look-up table in memory to optimize matching of the fields when you use FieldText specifiers. See NumericType Fields.
OcrFilterType Fields to evaluate by the OCR filter, and not to index or store if its quality is unsatisfactory (the field is stored, but is empty).
ParametricType Fields that hold parametric values.
ParametricRangeType Fields that contain numeric values to use to generate numeric ranges for parametric searches.
PrintType Fields whose content is displayed with results when you set the query action Print parameter to Fields.
Ranges The number of ranges to use for ParametricRangeType fields.
ReferenceMemoryMappedType Fields that hold a value that is an existing value in a different ReferenceType field. This is then used in combination with the FieldRecurse action parameter and the field specifier MATCHRECURSE.
ReferenceType Fields that hold document references. See ReferenceType Fields.
SectionBreakType Fields that hold the section number of documents that were split by the Import module.
SecurityType The security type of documents that contain associated fields.
SortType Fields to store for fast sorting when you use the ARANGE FieldText specifier or an alphabetical Sort option when querying Content.
SourceType Fields to use to generate summaries and to suggest conceptually similar documents.
SynonymType Fields that hold the name of the synonym job whose settings apply to documents that contain associated fields.
TextParseIndexType Fields to treat as Index fields when sending a query using the TextParse and AgentBooleanField parameters.
TitleType Fields that hold document titles.
TrimSpaces Fields from which to remove multiple, leading, or trailing spaces before storing in Content.
Weight The factor by which the weight of terms in associated fields is increased if they match query terms.

You cannot configure a field with more than one numeric-based type concurrently. Numeric-based types include NumericType, NumericDateType, MatchType, ParametricRangeType, ReferenceMemoryMappedType, and ParametricType when the ParametricNumericMapping configuration parameter is set to True.

If your configuration file contains a field with a conflicting configuration, the server uses an internal precedence to set the field property. It flags the configuration conflict in the logs, and in configuration validation.

You can view information about the indexing fields that are defined for the documents in the data index on the Field Types page in the Monitor section of the IDOL Admin interface. For more information, refer to the IDOL Admin User Guide.