Siren Platform User Guide

Index to entity Identifier relations

When two entities are connected using Entity Identifier

For example, let’s take the following indices:

company

an index containing information about companies; each document in the index has a field called city that contains the name of the city this company is located in

investor

an index containing articles; each document in the index has a field called city that contains the name of the city this investor is located in

city

an entity identifier which represent the concept of a city

There is no direct relation between investor and company but thanks to the city entity identifier the Relational Navigator is able to join the two. The following image shows a light-blue button for a relation using entity identifier described previously.

Relational Navigator on the Investor dashboard

There are two possible locations using is located in relation from 15k investors currently displayed

  • 54028 companies on all companies dashboard
  • 3 companies on Companies timeline analysis dashboard
Ordering

Click Order (si-order.png) to switch the ordering

There are two possible ways to navigate the tree of possible destinations, we can order by:

dashboards - where you first see the relation and then the destination dashboards

Order by dashboards first

relations - where you first see the destination dashboards and then which relation you can reach it with

Order by relation first

Configuration

All possible relations are discovered automatically.

Relational Navigator settings
Hierarchy types (layout)

There are two possible values:

Normal - the entity identifiers subtree layout is EIDs → relations → dashboards or EID → dashboards → relations

Light - the entity identifiers subtree layout is collapsed into EIDs → relations → dashboards or EID → dashboards → relations

The following image shows the Light layout activated

Relational Navigator settings, layout
Visibility

In the component setting, one can change the visibility status of each individual connection at multiple levels.

The three state eye component enables you to specify "never show", "always show" or "inherit show from the previous".

User can restrict which destinations are visible by clicking the eyes symbols next to listed destinations

For example, lets hide one company dashboard destination when we are on "articles" index

Relational Navigator settings, hide one destination

As we can see now the Companies timeline analysis is no longer displayed on Articles dashboard

Relational Navigator on the Articles dashboard, one destination hiddedn

Search results

    No results found