Specify Field Names

If you specify multiple field names, separate them with commas. There must be no space before or after any comma. You can use Wildcards.

When naming fields, use the format /FieldName to match root-level fields, */FieldName to match all fields except root-level, or /Path/FieldName to match fields with the specified path. If you just specify FieldName, HPE IDOL Server automatically adds */ to it.

ACLFields Example

&ACLFields=*/AUTONOMYMETADATA

HPE IDOL Server reads ACLs from any fields called AUTONOMYMETADATA.

DatabaseFields Example

&DatabaseFields=Document/DREDbName,*/myDB

HPE IDOL Server indexes the document into the database with the name contained in any DREDbName field below the Document level and with the name contained in any fields called myDB.

DateFields Example

&DateFields=Document/DREDate,*/myDocDate

HPE IDOL Server extracts dates from any fields called DREDate contained below the Document level and from any fields called myDocDate.

NOTE:

If you index documents that contain fields with partial dates into HPE IDOL Server, the document is assigned a metadata field specifying a full date. This date is the first day of the month if the day is not specified, and the first of January if neither the day or the month are specified. The format of the partial date must be a format specified in the DateFormatCSVs configuration parameter.

DocumentDelimiters Example

&DocumentDelimiters=*/DOCUMENT,*/SPEECH

HPE IDOL Server marks the beginning and end of individual documents in the file by opening and closing DOCUMENT and SPEECH tags.

ExpiryDateFields Example

&ExpiryDateFields=Document/DREExpiryDate,*/myExpiryDate

HPE IDOL Server reads the expiration date from any DREExpiryDate field below the Document level and from any fields called myExpiryDate.

FlattenIndexFields Example

<documents>
   <article id="_21498602">
      <url>http://example.com/21490.html</url>
      <hltext_display>The history of pharmacogenetics </hltext_display>
      <source>Science Online</source>
      <media_type>text</media_type>
      <subject>
         <text>The prologue to pharmacogenetics began to play out around 1850 and spanned some 60 years into the 1900s.</text>
         <text>In 1953, the molecular basis of heredity, the double helix of DNA, was described.</text>
      </subject>
      <valid_time>Jul 13 2001  5:00AM</valid_time>
   </article>
</documents>

If you specify FlattenIndexFields=*/subject, and index the above document, HPE IDOL Server indexes any content in a subject field or a field within a subject field as the content of the subject field.

If you then query the subject field for a particular term that is actually contained in a level below the subject field (such as the term “pharmacogenetics”), the content of both text fields returns. If you do not flatten the subject field the query does not return results, because the subject field itself does not contain the term.

IndexFields Example

&IndexFields=*/DRECONTENT,*/DRETITLE

HPE IDOL Server explicitly indexes the DRECONTENT and DRETITLE field in documents.

LanguageFields Example

&LanguageFields=Document/DRELanguageType,*/myLanguageType

In this example, HPE IDOL Server reads the language type of documents from any DRELanguageType field below the Document level and any myLanguageType fields.

MustHaveFields Example

&MustHaveFields=*/DRECONTENT,*/DRETITLE

In this example, HPE IDOL Server stores only the DRECONTENT and DRETITLE fields in the document.

SectionFields Example

&SectionFields=Document/DRESection,*/mySection

In this example, any DRESection field below the Document level and any mySection fields indicate the start of a new section.

SecurityFields Example

&SecurityFields=Document/DRESecurity,*/mySecurity

In this example, HPE IDOL Server reads the security type of documents from any DRESecurity field below the Document level and any mySecurity fields.

TitleFields Example

&TitleFields=*/DRETITLE

In this example, HPE IDOL Server reads a document title from its DRETITLE field.


_HP_HTML5_bannerTitle.htm