.Stat Suite documentation

Search results

Table of Content

Version history:
Introduction of the short URL generation with June 13, 2024 Release .Stat Suite JS arc
Result ordering introduced with April 11, 2022 .Stat Suite JS 14.0.0
Result boosting introduced with April 11, 2022 .Stat Suite JS 14.0.0
Download additional files through the SDMX EXT_RESOURCE annotation since March 10, 2021 Release .Stat Suite JS 7.1.0


When users perform a free text search or browse by a facet from the .Stat DE homepage, then a page with the results of the search is presented. The search result page displays a list of all the corresponding hits from the search, along with the associated facets depending on the current search context (see documentation on Facets).

Result content

The total number of search hits is displayed on top of the search result page content above the thick grey line, followed by the first set of the most relevant search results. In reduced (responsive) mode, the [x] results moves right to Applied filters.

The search results page is paginated and lists all result hits.

Each search result is divided into three parts:

  1. The first part displays the basic information by default (in the collapsed mode);
  2. The second part displays extended information in the expanded mode;
  3. third part is the set of options on the right side.

de facet result

The following information is displayed for each search result:

  1. Default display of basic information (collapsed mode)
    • The localised dataflow name (or its ID if no localised dataflow name exists) linking to the table data preview. The link takes the current search terms into account.
    • The localised dataflow description if exists. It is shortened to 3 lines if too long.
    • The localied comma-separated list of dataflow dimension names (in the order of their definition in the DSD) that have more than one dimension value with real data (according to actual data availability).
    • The localised name of values of dataflow dimensions (togther with the localised dimension name), which have search hits. One line per dimension.
    • An Expand icon to display extended information (see below).
    • A Download icon to download the entire dataflow content in SDMX-CSV format. (For details see the sub-section below.)
  1. Display of additional extended information (expanded mode)
    • The entire description becomes visible if it was shortened in the default display.
    • The comma-separated values for all home page facets for this dataflow prefixed with ‘... > ’ when a value has a parent hierarchy, and with the facet names, e.g., ‘Topic: ... > Health Status, ... > Production, Environment’, unless the facet is already listed as a dimension with a free-text search hit under the basic information. One line per facet. All values not fitting on one line are replaced by 3 dots .... When there is a hierarchy, then the whole parent hierarchy is made available in a black tooltip on mouseover (similar to “Applied filters”).
    • The date/time of the last update of the dataflow
    • The Collapse icon (instead of the Expand icon) in order to return to the default display (see above).

Optional download feature

When this option is enabled (see the configuration documentation), then two options of download are made available in the search result objects:

  • Download of the complete unfiltered dataflow data in tabular text (SDMX-CSV format) using the current language;
  • Download any additional files that are attached to the dataflow through the SDMX EXT_RESOURCE annotation (see the related specifications).

de search result content highlight

Result ordering

By default, the search result dataflows are sorted in this order:

  1. Descending relevance (where the free-text was found, dataflow boost)
  2. Ascending alphabetical (localised dataflow name)
  3. Descending “Last updated” date

In order to easier find specific dataflows, the user can change the sort order by selecting one of the predefined criteria using the dropdown menu:

de search result order

Short URL

The search result page URL can be shortened, allowing users to easily share the search results with others.
The “Share” option is displayed in the search result header next to the “Sort” option, and only when users are logged in.

de search result short url

Clicking on “Share” expands a drawer with a button “Generate short URL” and an empty text field. Clicking on the button generates a short URL and copies it to the clipboard. The button text is changed to “Copied”. Generating a new short URL will be possible only if the content of the search result page is altered (e.g., when filtering the result, or when searching for new content).

de search result short url

Result boosting

The default relevance score used to order the search results depends on where the search term was found, which can be customised as documented here.

Weight value and Solr search engine score

The .Stat faceted search allows using the dataflow annotation of type SEARCH_WEIGHT to boost dataflows in the search result order when ordered by “Relevance”.

The weight value is a positive number and should be set:

  • in the localised Annotation Text, in case the boost is language-dependent, otherwise
  • in the non-localised Annotation Title
    <common:AnnotationText xml:lang="en">1.0000001</common:AnnotationText>
    <common:AnnotationText xml:lang="es">0.9999998</common:AnnotationText>
    <common:AnnotationText xml:lang="fr">1.0000008</common:AnnotationText>

The localised boost value, if available, or alternatively the non-localised boost value is used to multiply the dataflow score calculated by the Solr search engine automatically depending on the count and location of search hits in the different dataflow properties (searched fields). The bigger the so calculated overall score value, the higher is the listing of the dataflow in the search results.

The SEARCH_WEIGHT should be between 0 and 1 to decrease the score, and it should be greater than 1 to increase the score. The value has no limits other than the ones defined by the internal number type. However, it is strongly recommended to not use too high numbers to avoid overboosting, which means pushing dataflows too strongly in irrelevant contexts. E.g., if the sole goal of the boosting is to achieve a specific ordering of dataflows when browsing through a categoryscheme, like for displaying a list of dataflows categorised under a topic, then the boost values should be extremely close to 1, e.g. 1.0000001 in order to not impact the order of results from free-text searches, see above example annotation.

The “developer tools” of the web browser (accessibly through the F12 key) allow seeing the current final Solr score per dataflow for a specific query in the response message of the search requests (look out for queries to https://example.org/api/search?tenant=xxxxx). This analysis can be used to determine the optimal SEARCH_WEIGHT boost values.

de search result Solr score

Result pagination

Search results are paginated, and the number of results per page is configurable (see Documentation).
By using the feature at the bottom right side of the search results page, the user can move to the next, first or last page by using the corresponding arrows |< < > >|. The user can also enter a page number in the appropriate box.

de search result content

Result page URL

The search result page(s) can also be accessed through a direct link, because some of the user’s choices and options are part of the URL, which can thus be shared or bookmarked.
The configurations of the search results included in the URL are listed and explained in the following table:

key type definition exemple
locale string locale of the app lc=fr
facet string open box in side in search results fc=qmsoRy4r
term string search term tm=people
start integer page index of the search pg=0
constraints array selected facets of the search constraints[0]=SIS-CC-stable
hasAccessibility boolean a11y mode of the app ac=false
hasDataAvailability boolean sdmx data availability mode hasDataAvailability=false

Note that the full set of configurations of the URL is listed in the Viewing data topic.

When the user clicks on a search result name from the search result page, then she/he is forwarded to the DE data visualisation page that corresponds to the selected result.
The filter selections are also kept to the visualisation page that uses it to make the automated filter selections. For example, if the user has selected a reference area in the reference area facet of the search result page, then this selection is maintained in the reference area filter in the data visualisation page.

(since May 19, 2021 Release .Stat Suite JS 8.0.0) If the free-text search is used and a “perfect match” (excluding non-alphanumeric characters) search hit is found within a dimension value, and if such dimension has no facet selection, then instead of DEFAULT selections, automatically the (perfect match) value(s) is selected in the filter of the data visualisation page for that dimension.

Example with searching terms “GDP current prices France”:

de search result content visualisation page

  • In the visualisations of all 3 displayed result dataflows:
    • The “Prices” dimension will only be filtered on the value “Current prices”;
    • The “Reference Area” dimension will only be filtered on the value “France”;
    • The DEFAULT selections -if any- will apply on the other dimensions not concerned by the hit of the free-text search.