Populate database with result of Collibra Output Module API

Some integration use cases related to the Collibra platform require structured content to be exported from Collibra using the Output Module API and processed further, for example, by being written to a database or a file. The goal of this integration template is to demonstrate how to best implement this type of use case. At the same time, the Output Module API cannot be used for all types of export use cases. You can consult with a qualified solution architect that has experience on the topic, who can provide you with an analysis as to whether the usage of the Output Module API is justified. Typically, to export content from the Collibra platform, you need to take into account the following factors before opting for a particular API:

1. The volume of the data in scope, for example, thousands of records or hundreds of thousands.
2. The frequency of the export, for example, on-demand, daily, weekly, and so on.
3. The nature of the data being exported, for example, assets, responsibilities, workflows.

Analysis of the above factors will determine if the Output Module API is appropriate for your use case. There are alternative methods such as the Collibra Reporting Data Layer (Insights) that may better suit your data export requirements.

Elements in Scope

Asset Types

The assets that are synchronized between your Collibra environment and the in-memory database are assets of type Code Value and Issue.

Relation Types

This section outlines the relation types that are synchronized:

• Code Value groups/is grouped by Code Value
• The issue impacts/impacted by Asset

To receive support on this item, you can engage our Professional Services team or post any questions in the Data Citizens Community.