Skip to main content

Why to use the Portal


Talend DQ Portal can act as a Business Intelligence layer that connects to the data quality datamart. The Portal can be used to publish and distribute data quality reports to various groups in the organization. These reports can act as technical specifications of data quality and will help technical teams to achieve a business decision on the data.

Users can publish to the Portal reports about the results of the profiling analyses done in the Profiling perspective of Talend Studio. These reports help managers or business users to see the improvement or degradation in the quality of the enterprise data.

It is also possible to create custom reports using the Jasper or Birt engines and publish them to the Portal, or to create user groups and publish separate reports to each user group.

A typical life cycle in the Portal could be:
  • Users of the Profiling perspective of Talend Studio create analyses/reports and use a MySQL or an Oracle database to store the profiling results in the data quality datamart. For further information, check the data profiling part in the Talend Studio User Guide

  • Users use Talend Studio to create and deploy Jobs to run the reports periodically using the tDqReportRun component. For further information about this component, check the data quality chapter in the Talend Components Reference Guide.

  • Business users can access the Portal in order to visualize/export/share the reports without launching the studio, and eventually provide feedbacks to the management groups.

    Business users would watch the data quality reports on a regular basis when data often change, due to batch loads for example, in order to make sure that the data quality rules and constraints (thresholds) are still verified after every load.

  • Experience users may do customize analyses on the datamart with extra utilities like Custom Reports, provided in SpagoBI on which Talend DQ Portal is based.

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!