Hierarchical Facet Output - Fluid Topics - 3.6

Use Fluid Topics Web API

Product
Fluid Topics
FT_Version
3.6
Category
Technical Notes
language
English

In this scenario, the hierarchical facets can be represented through a tree architecture as follows:

Content Type
|_Structured Documents
|_Structured Documents|Author-It
|_Etc.
|_Etc.
|_Unstructured Documents
|_Unstructured Documents|PDF
|_Etc.
|_Etc.

Where:

  • Content Type is the rootNode.
  • Structured Documents and Unstructured Documents are Content Type childNodes.
  • Structured Documents|AIT is Structured Documents childNode.
  • Unstructured Documents|PDF is Unstructured Documents childNode.

The depth of the tree architecture depends on the maxDepth value defined in the JSON input.

The following lines show an example for an empty query with the hierarchical facet for the Content_Type_Custom metadata element.

{
"facets": [
{
"key": "Content_Type_custom",
"label": "Content Type",
"hierarchical": true,
"multiSelectionable": true,
"rootNodes": [
{
"value": "Structured Documents",
"label": "Structured Documents",
"selected": false,
"totalResultsCount": 533,
"childNodes": [
{
"value": "Structured Documents|Author-it",
"label": "Author-it",
"selected": false,
"totalResultsCount": 532,
"childNodes": [...],
"descendantSelected": false
},
{...}
],
"descendantSelected": false
},
{
"value": "Unstructured Documents",
"label": "Unstructured Documents",
"selected": false,
"totalResultsCount": 2,
"childNodes": [
{
"value": "Unstructured Documents|PDF",
"label": "PDF",
"selected": false,
"totalResultsCount": 2,
"childNodes": [...],
"descendantSelected": false
}
],
"descendantSelected": false
}
]
}
],
"results": [
{
"entries": [...],
...
},...
],
"paging": {
"currentPage": 1,
"totalResultsCount": 535,
"totalClustersCount": 284,
"isLastPage": false
}
}