How to Use Embedded Content Intelligence

• About Content Intelligence

• Feature Location and Settings

• How to Enable/Disable the Feature

• How to Use Embedded Content Intelligence

• modalTemplate: Default Labels and Values

• How to Configure Content Intelligence Labels and Metadata

• Content Intelligence Example With HTML Source Code

• ZeroSearch Feature

• How to Enable ZeroSearch

About Content Intelligence

• Content Intelligence is a native SmartHub feature contained in a button  next to each search result, as shown in the example below.

• Content Intelligence is also available as part of the ZeroSearch feature, described at the bottom of this page.

Feature Location and Settings

• Source code directory
  • <Smarthub_Installation_dir>\modules\ContentIntelligence\
• Settings:
  • Located around line 710 in the file DefaultModuleSettings.js located at: <SmartHub_install_dir>\modules\SmartHubResourceLoader\
• Default HTML template:
  • \modules\ContentIntelligence\templates\modalTemplate.html
  • The default file modalTemplate.html is overwritten when SmartHub is upgraded. 
  • Note: Copy and rename the provided default template file or rename the existing template as "modalTemplate_backup" before modifying it.
• Container ID (optional):
  • The landing page container ID is "contentIntelligence."
  • This ID can be embedded in your landing HTML page.
• Action bar <div> tag
  • Must be embedded on the HTML page where you use Content Intelligence
  • See the below "ActionBar Component" topic for details.

How to Enable/Disable the Feature

Before continuing, familiarize yourself with the information in the topic How to Use the UI Builder. Content Intelligence high-level feature settings are stored, like other BA Insight SmartHub features, in the DefaultModuleSettings.js file.You can find the DefaultModuleSettings.js file in the <SmartHub_install_dir>\modules\SmartHubResourceLoader\ folder.

UI Builder

• The easiest and fastest way to insert and customize ContentIntelligence is via the SmartHub UI Builder.

• For more information, see How to Use the UI Builder.

Procedure:

1. SmartHub administrators can simply click the UI Editor link from the SmartHub Administration page.

2. Click the Select a page link from the top menu.

3. Select (double-click) an HTML page such as Results.html page.

   1. Below, the Results.html page is shown for sample purposes.

   2. BA Insight recommends you use page and folder to modify. Leave the default files as templates.

      1. Example: Customizations/CustomResults.html. Default Results.html is under the top most SmartHub directory.

      2. See Creating Custom Pages.

4. Select the Advanced mode from the top right of the page.

5. Select Advanced settings edit.

6. Scroll down to line 235 (this may vary), which contains the text SH.ContentIntelligence.CustomSettings
   
   
   

7. Click the link Default Settings at the top right.

8. A new browser tab opens with all available SmartHub module settings.
   
   

9. Search for the word "ContentIntelligence" on the page to quickly navigate to the ContentIntelligence default settings, shown below:
   
Copy

    SH.ContentIntelligence = SH.ContentIntelligence || {};
    SH.ContentIntelligence.DefaultSettings = {
        Title: "Content Intelligence".toLocaleString(),
        ContentModalTemplatePath: SH.RootLevelURL + "/modules/ContentIntelligence/templates/modalTemplate.html",
        SearchInterfaceElement: ".CoveoSearchInterface",
        ZeroSearchParentContainerID: "contentIntelligence",
        EnableLandingZeroSearch: false,
        DefaultUrlFunction: '(function (concept) { return "http://wikipedia.org/wiki/"  + concept.replace(/ /g, "_")  })',
        ModuleDetails: {
            label: 'Insights'.toLocaleString(),
            iconClass: 'fas fa-info',
            btnClass: 'contentIntelligenceBtn'
        }
    }

10. Copy the ContentIntelligence settings section from SH.ContentIntelligence.DefaultSettings.
11. Go back to your Advanced settings edit tab.
    
    
12. Paste the copied settings inside section SH.ContentIntelligence.CustomSettings.

13. Modify settings as desired. Refer to the "Content Intelligence Settings" table below.

14. (Optional) Modify the labels and values from the template file modalTemplate.html, described below as you desire.
    
    
    1. Note: You must change the name of the modalTemplate.html template file before modifying it, as it is overwritten at upgrade time.
    2. You then point your settings (see "Content Intelligence Settings" immediately below) to the new template file name.
       
15. (Optional) If you want to render the Content Intelligence feature on landing page on load, embed the ZeroSearchParentContainerID ("contentIntelligence") found in the Content Intelligence settings (see below), in the desired (custom) landing HTML page file.

16. Click Save changes.

17. Click the link Preview <html> file.html at the top of the code editor.

18. Review your HTML page in the new tab that opens.

    • Test the feature by performing a query on your SmartHub site.

19. Make any necessary changes back in the code editor. Repeat steps 14-18 as necessary.

20. Click Save changes.

Content Intelligence Settings

Content Intelligence settings are leveraged via the UI Builder tool.

ActionBar Component

• The ActionBar component is a <div> tag that must be embedded where you intend to use Content Intelligence.

• The location of the <div> tag does not matter.

<div class="CoveoActionBar core-action-bar"></div>

SH.TabularView.CustomSettings = {
     "TabularResultList":{
         "EnableContentIntelligence": "true"     }
};

modalTemplate: Default Labels and Values

Note: Copy and rename the provided default modalTemplate.html template file before modifying it.
It is overwritten when SmartHub is upgraded. 

The provided modalTemplate.html template includes the following pieces, all of which effect what is shown in the UI:

• Classes
• Form groups
• Labels
• Values
• Titles

Note the following:

• Each Label corresponds to a property.

• Labels and their corresponding properties, stored in the search index, are shown in the graphic below.

• All properties (some highlighted in the graphic below) MUST be set in your custom modalTemplate HTML file or the fields in the UI will not be populated with values.

Changing the modalTemplate Name or Path

• Changing the modalTemplate.html filename requires the new file to be declared and defined in any custom page settings files.

• For more about custom files, see How to Use the UI Builder.

Example

• For example, in the custom Results page settings file example below, CI custom settings (SH.ContentIngelligence.CustomSettings) are stored in a modal template file named CI.html in a custom directory (/SmartSearchNew/templates/CI.html).

• This custom file is not overwritten when SmartHub is upgraded.

ResultCustomSettings.js Example

How to Configure Content Intelligence Labels and Metadata

• The provided modalTemplate is an HTML page that can be modified as you see fit.

• Form groups, classes, labels, values, etc. can be reused and/or renamed.

Populating Content Intelligence with Metadata

Populating your Content Intelligence fields with properties (metadata) requires two things:

• Properties declared in a custom modalTemplate HTML file, shown and described above.
  • DO NOT modify the modalTemplate.html file provided out of the box; the file is overwritten at upgrade time.
• Properties listed in your Results or custom Results HTML page.
  • The parameter "data-fields-to-include" (shown below) contains the list of data fields shown in the UI.
    • Some values are provided by default (around line 126).
    • See the example and graphic below.

Example

Below is an example which contains:

• Class "CoveoResultList" which contains "data-fields-to-include,"
  • "data-fields-to-include": includes the properties made available in CI.
    • Properties are entered as a comma-separated list, each preceded by an '@' character.
    • Any fields in your modalTemplate.html file that are NOT included in the "data-fields-to-include" comma-separated list, are not populated with values in CI, even if the properties exist in your index. 

Example: Content Intelligence Template

The CI example below contains:

• Sections with values: A "metaContainer" class, shown below with label "Summary."
  • Can also contain titles (div class "metaTitle") and values (div class "metaValue") under the section.
• Form Groups: Such as the box that includes the metadata labels:
  • Author
  • Last Modified
  • Content Source
  • Result Type
• Labels: Such as "Author," "Extracted Text in Images," "Content Source," and so on. 
• Values: Attached to Labels below, such as "SharePoint Content," "pdf," "2020-04-23T13:5901.000Z," and so on.

Content Intelligence Example With HTML Source Code

Below is another modalTemplate HTML file with various CI classes, Sections, Form groups, Labels, and Values, and the corresponding user interface provided to the user.

Note: In the screenshot below, the fields are shown for example purposes.
They are not populated.

How to Select Properties to Display in UI

• The properties shown below are provided by the search index.
• The properties pushed to the index are the properties available to Content Intelligence. 
  • For example, if you use BA Insight ConnectivityHub to populate the index, the properties come from ConnectivityHub, if you use a SharePoint search engine, the properties come from the SharePoint Index.
    Note: Connectivity Hub can map properties from source content to custom, defined properties.
• The properties shown below have been listed in the Results HTML page (or custom Results HTML page) 

ZeroSearch Feature

What is ZeroSearch?

ZeroSearch renders an HTML element that combines Advanced Search functions with Content Intelligence functions.

The ZeroSearch feature can be used on a custom Index or Landing page.

• In the screenshot of a ZeroSearch frame below observe the following:
  • Advanced Search functions appear on the left
  • When query text and options are selected, and the Search button clicked:
    • On the right side, under Search preview, the top search returns are displayed.
    • A Content Intelligence "Insights" icon is displayed for each returned result.
    • Selecting the "Insights" link under each returned item displays the Content Intelligence properties described above.

Example

The example below supposes a SmartHub site that uses the following custom Index files for the sake of example:

• HTML Index Page:
  • IndexCustom.html
• Index Page Settings File:
  • IndexCustomSettings.js

How to Enable ZeroSearch

To enable the ZeroSearch feature on a landing/index HTML page, perform the following general steps:

1. Open (or create) your custom Index HTML page.
   
   • For example: <SmartHub_root>\IndexCustom.html.
     

2. Choose a location where you want the Content Intelligence ZeroSearch element to be rendered and add the following code:
   Note: Where you place the code affects where on the page the ZeroSearch box appears. In the example below, the ZeroSearch box appears on the bottom of the Index page.

   <div id="contentIntelligence" class="contentIntelligence"></div>

   
   
   

3. Open the file <SmartHub_root>\modules\SmartHubResourceLoader\DefaultModuleSettings.js and copy the Content Intelligence settings (from around line 710).
   
4. Open your page's custom settings file, such as a custom Index page's custom settings file (ex. IndexCustomSettings.js for the page IndexCustom.html).
   Locate the SH.ContentIntelligence.CustomSettings line.
   
5. Insert the copied Content Intelligence settings (starting with "Title") into your Index custom settings file.
   See the screenshot below as an example.
   
   
   
6. Change the following settings:
   
   1. ZeroSearchParentContainerID: If you choose another ID for your <div> element at step 2, change this setting to contain that ID.
   2. EnableLandingZeroSearch: Set to true.
   3. LandingEnabled: Make sure this setting is set to true.
   4. Title: Optional. Add a new title for your element.
      
7. Ensure the code is valid, well-formed, and all tags are properly opened and closed.
   
8. Save and close all files.