Configuring the Schema for Exalead v.4.6

Build 1501 on 14/Nov/2017  This topic last edited on: 21/Mar/2016, at 18:52

The default schema is already configured to index the standard object types. The below are details on how that's done.

The first thing to do is specify which GN4 objects will be indexed. It can be done as following:

 <xs:element name="story">

   <xs:annotation>

     <xs:documentation>Complete story: text with subject(s) + list of video and

     images. Descend from folderObject, so inherits slugline, author etc.</xs:documentation>

   </xs:annotation>

   <xs:complexType gs:key="folderRef name">

     <xs:annotation>

       <xs:appinfo>

         <gs:fullTextObj exaSourceName="story"/>

         ...

This indexes every “story” object and "exaSourceName" attribute refers to the Exalead source name.

Second step is specifying which attributes of the "story" object should be indexed:

         <xs:element name="richText" type="tHtml" gs:access="Content">

             <xs:annotation>

               <xs:appinfo>

                 <gs:fullTextAttr exaMetaName="richText"></gs:fullTextAttr>    

                 ...

 

In this example, we’re indexing the "richText" attribute, and it will be put into correspondent Exalead meta data handler.

Ancestor attributes can also be indexed, for example it's possible to index folderObject attributes such as "creationDate" or "modifiedDate".

Important

It is not possible to index attributes starting with “_” or named “size” (conflicts with Exalead one); Meta data handler name must be changed.

Attribute indexing options

Several options can be set for indexing attributes, defining a fullTextObj meta (optionally):

         <gs:fullTextObj exaSourceName="story">

           <gs:meta name="richText" score="TEXT" indexed="true" field="true"         isHtml="true" />

         </gs:fullTextObj>

Name: The name of corresponding meta data handler in Exalead.

Score: The Exalead score class name, in order to assign different score weight to attributes (Class score value can be changed in Exalead view administration).

Indexed: If the attribute’s content must be indexed as full text content (e.g.:  for identifier and date attributes can be set to false. This means that for example if we search “2009” it won’t find all the documents with a date containing “2009”).

Field: If attribute must be indexed in a specific Exalead field, so it can be searchable or used for sorting.

IsHtml: If attribute’s content is HTML (or any XML code), if set true all tags inside content will be stripped.

Standard indexing options

If a fullTextObj meta is not specified for an attribute, the standard indexing options will be used for corresponding indexed attribute:

Name: GN4 attribute name

Score: TEXT

Indexed: true

Field: true

IsHtml: false