Added by IBM contributorIBM | Edited by Claudia R Elbourn on June 9, 2015
Rate this article 1 starsRate this article 2 starsRate this article 3 starsRate this article 4 starsRate this article 5 stars

No abstract provided.

This document describes the facet parameter of the Search API and the corresponding response elements. The 'facet' parameter allows obtaining the facets which are relevant for the search query. The facets supported in Connections Search include Tag, Person, Date, Source, and (for status updates only) Trend.

Request Format

The "facet" parameter of the Search API is optional. When absent, facets will not be returned with the search results.

The "facet" parameter can repeat multiple times. Each instance of the parameter defines a category for which facets should be computed. For example: 'Person', 'Date', 'Tag', etc. The value of the "facet" parameter is a JSON string. A number of attributes for the JSON string are supported. All of the attributes which have a default value are optional. Any unknown attributes will be ignored. The attributes are:

Default Value
id defines the ID of the category from which facets should be computed. This attribute is mandatory.
This value can be obtained from a response of a previous search request.
depth defines how deeply to collect facet values under the given category. If the depth is 0, only the category itself is returned. If the depth is 1, its immediate children are also returned, and so on. If the depth is the constant value "ALL", then there's no limitation on how deep to collect facet values. 1 Negative values are not allowed.
count defines the maximal number of values to return for this category. If the count is the constant value "ALL", then all the category's descendants in the provided depth are returned, up to the maximum. 10 Negative values are not allowed. The maximum is 1000.
sortOrder defines how results should be sorted: ascending or descending. Facets results are sorted by weight. DESC This attribute has only two allowed values: "ASC", "DESC".

The full structure of the parameter (in JSON format) is:

facet={"id": "<facet_id>", "depth": <depth>, "count": <count>, "sortOrder": "<order>"}


Some examples:
facet={"id": "Tag", "count": 50}

facet={"id": "Person", "count": 250}

facet={"id": "Date", "count": 250, "depth": 2}

facet={"id": "Source", "count": 50}

facet={"id": "Trend", "count": 50}

Response Format

The response format is designed to allow a faceted search client which is as generic as possible. The format is XML-based, and augments the existing Atom search feed with additional elements. All additional elements have the "ibmsc" namespace, where "ibmsc" is short for "http://www.ibm.com/search/content/2010". The root "atom:feed" element is augmented with "ibmsc:facet" elements, as defined in the following schema:

atomFeed = element atom:feed {

ibmscFacets ~//in addition to existing elements


ibmscFacets = element ibmsc:facets {

attribute taxonomyId { text},



ibmscFacet = element ibmsc:facet {

attribute id { text},

attribute type { text },



ibmscFacetValue = element ibmsc:facetValue{

attribute id { text},

attribute label { text },

attribute weight { float },



Description of response elements:


Root element for all facets information
Identifies the facets taxonomy - to be used in a category Constraint
defines the category for which facets were computed
the identifier of the category.
defines the type of facet. May be used as a hint to the client side on how to render the facet. For example, if type is "Person", can be rendered as a "live" person link. If type is "Tag", can be rendered as cloud. These values are predefined: "Date", "Tag", "Person", "String", "Number", "Integer".
defines a category for which search results were found. A facetValue may contain sub-elements, in a tree-like structure.
The identifier of the category for which search results were found.
A human-readable label for this facet value.
A number indicating the relative weight of this facet value within the search results. This number may correlate to the actual number of search results matching this query, but that is not mandatory.


When a facet value is selected by the user, the API provides the following way to reflect that selection in the faceted search request:

1. In order to limit search results to ones matching this facet value, use the "constraint" parameter. combine the "id" of the facetValue element with the "taxonomyId" attribute of the facets element on the response, in order to build the new service URL. This option can also be used in order to select two facet values or more simultaneously. The category value should match the Id of the selected facet value.

2. In order to explore facets in a subcategory of the selected facet value (if exists), use the the "id" of the facetValue element as the "id" attribute of the facet request parameter.



<ibmsc:facets taxonomyId="facets"> 

<ibmsc:facet id="Date" type="Date">

<ibmsc:facetValue id="Date/2012" label="2012" weight="1">

<ibmsc:facetValue id="Date/2012/07" label="07" weight="1"/>