Skip to main content

Steps to use the Semantic-aware analysis

From Talend Studio, you can use the Semantic-aware analysis to:

  • Explore the semantic categories and query complex semantic relationships in the data you analyze.
  • Create table analyses preconfigured with indicators and patterns that best suit the data.
  • Index and enrich the ontology repository on the Elasticsearch server with semantic categories and analysis results.

The sequence of using the Semantic-aware approach to create pre-configured table analyses involves the following steps:

  1. Connecting to a data source from Talend Studio, whether it is a database, a delimited file or Hive.

    For further information, see Creating connections to data sources.

  2. Launching the Elasticsearch server where ontology indexes are stored.

    For further information, see Launching the server and setting preferences.

  3. Selecting a table in the data source or a view in a database connection and exploring semantic categories of data columns.

    You can also select to start a Semantic-aware analysis on a set of columns in a table. For further information, see Exploring semantic categories of data columns.

  4. Matching column metadata and semantic categories with the concepts from the Ontology repository and outputting the matching results to show the most relevant concepts.

    For further information, see Matching column metadata and semantic categories with the concepts in the ontology repository.

  5. Defining attributes (semantic) for columns and enriching the Ontology repository with column metadata and semantic categories.

    For further information, see Enriching the ontology repository.

  6. Running the recommended table analysis and enriching the Ontology repository with analysis results and indicators and patterns used on the analyzed columns.

    For further information, see Defining the recommended table analysis.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!