• Prerequisites
• Creating flows with text query
• Composition of a text query
• Results for a text query
• Choices of graphics
• Sorting
• Trend of a measure
• The best / the worst, the top / bottom
• Aggregation
• Targets
• Use of synonyms
  • Creating synonyms dictionaries
  • Activating synonyms dictionaries
  • Use case
• Scores for a result of a text query

Prerequisites

• Cubes in your wallets recently synchronized

Creating flows with text query

Digdash offers the possibility to create flows in some clicks with natural language.

• Via the dashboards editor

	Dashboards editor > Creating new graphics > In natural language
	In the showing dialog, you can enter you query in the search bar.
	Choose a flow in the results list (we are going to pick the first one)
	And save the flow in the current wallet.
	Give a name to your flow.
	The new flow will be added to your dashboard editor and you will find it in the existing graphics list.

• Via the dashboard

It is also possible to add a « Text query » element in your dashboard in order to create flows on the fly.

	Dashboards editor > Additional content > Elements > Text query
	Add the element in your dashboard editor.
	According to your query, you may filter on some measures/dimensions. You would better have a « Filtered elements » element in your dashboard to remove these filters for the potential next queries. Dashboard editors > Additional content > Elements > Filtered elements
	You will find those elements dashboard side.

Composition of a text query

Digdash allows you to create flows from data models in natural language.

Digdash mainly rests on keywords to suggest you the most relevant flows and the names of your data models’ columns.

So a query is basically composed of measures names from your data model and/or dimensions names, followed (or not) by flows names and/or sorting operations.

We shall later explain how important query terms are important.

Results for a text query

Screenshot: Results for a text query

Results for a text query are presented in list, with its associated flow, sorted by its relevance and a score. The more the score is high, the more the suggested flow is considered as relevant. Also, the cube name is mentioned so is a description of the flow.

We shall later see in this document which are the criteria that could have an influence on the score of a result.

Choices of graphics

For a given query, you will be suggested a list of results of multiple graphics, depending on your query members.

Nevertheless, you can require a particular graphic, as long as it remains coherent (the query « Cost in line » has no sense).

The numbers of members for a cube has an incidence. Indeed, when a query, even coherent, has too many members to show, you will be suggested a more adapted graphic.

Here are the keywords to use for the choice of graphics:

Table presenting keywords for the different flows

Sorting

It is possible for you to use sorting operations with the following keywords :

Table presenting keywords for sorting operations

Trend of a measure

A measure has a trend. It can be stable (trend by default), increasing or decreasing:

Table presenting possible trends for a measure

You can change the trend of a measure via the Digdash Enterprise Studio, in the data source advanced configuration, in the properties part of a measure.

Definition of a measure’s trend in Digdash’s Studio Enterprise

• Impact of a measure’s trend

Trend has an impact on the sorting order. Indeed, if the type of sorting is not explicitly mentioned, the kind of sorting will be based on the measure’s trend. Consequently, we will get an ascending sort for a stable or increasing trend and a descending sort for a decreasing trend.

Table with examples presenting impact of a measure’s trend on sorting orders

The best / the worst, the top / bottom

It is possible to get the X best/worst members of the results of your query using these keywords:

Table presenting keywords for best/worst, top/bottom

Aggregation

You can define an aggregation method for the measures of your query using these keywords :

Table presenting keywords for aggregation

Targets

It is possible to apply targets on measures mentioning the following keyword :

Table presenting the keyword for targets

You can also directly mention the name of the targets you want to apply.

Table with example presenting the use of target in text query

Use of synonyms

Text query takes in charge synonyms of your query members.

Creating synonyms dictionaries

To use synonyms in text query, you first need to import a synonyms dictionary in Digdash.

Please refer to the documentation called « synonyms_dictionary_en.pdf » to import a synonyms dictionary in Digdash.

Activating synonyms dictionaries

You then need to check if the use of synonyms dictionaries is activated for text query in the server configuration.

In the server configuration page, at the bottom of the page > Advanced >> > Category Synonyms dictionaries > Checkbox Use synonyms dictionaries for text query

Screenshot: Activation of the use of synonyms dictionaries for text query

Use case

Table with example presenting a use case of text query with synonyms

Scores for a result of a text query

Queries results are ordered according to their relevance and the best score can reach a 5 out of 5.

The score for a result may vary for different reasons.

• Importance of the query members

Indeed, a result will be better marked if the query is composed of the exact columns’ names of your data models.

A query is then considered as less good if it contains partial names of your columns, or synonyms.

Table with example presenting how important query members are important

• Importance of the suggested type of graphics

The results list for a query suggests graphics more or less relevant for what is expected. Given the nature of the query members, some flows will be considered less relevant, hence a lower score for them.