Integration of a Enterprise Data Model into Collibra

Hi Manrich - I am interested if you got any answers on this or were able to figure out an approach. I was just about to post the same question . I thought of a similar approach to yours, or the possibility of parsing an XMI file via an integration. However interested if you have made any progress.

Here’s an example with Solidatus: https://marketplace.collibra.com/listings/solidatus-collibra-integration/
I think there are also integration with tools such as Idera.

Importing from collibra with the import API or exporting through the outputmodule are easy and efficient. It’s quite simple to map an xml or json file (through a static file, REST API or WS) with integration tools (Mulesoft, etc.) or custom scripting (Python, javascript, etc.)

Hello Manrich, i do not have an answer but I do have same objective in 2021. Currently trying to figure out what to do / how to define application integration layer in Collibra data model with drill down to more details. We have large number of interfaces and I dont think we will be able to to get auto discovery / lineage to see through all these mappings, but they are extremely important for us to evaluate impact of metadata changes. Have you done any of these in Collibra ?

I think this is a critical topic…thanks for starting the conversation @manrich.kotze.

So the summary conclusions are:

• organizations need a Conceptual (Subject Area Model, Conceptual Data Model), Logical (3rd Normal Form and application specific) , and Physical Model (view of physical objects) to understand the Enterprise Information Model
• Collibra is great at storing the individual metadata objects but not so for creating a model
• the Logical and Conceptual layers need to be created “manually” via collaboration between your 'Technical Data Steward" or “Data Custodian” (i.e. the IT person) and the Business Steward (business SME).
  - understanding Collibra is working some automation based on profiling results but lets leave that out for now.
• linking the Logical layer (Entity.Attribute) to the Collibra business layer (conceptual and Business Terms where applicable) is a manual effort carried out by the Business Steward with support from the Data Custodian
• linking the Logical Layer (Entity.Attribute) to the physical layer (Tables.Column) can be done in any data modeling tool … they all are able to reverse engineer a physical database with referential integrity into a logical data model.

So the question is…has anyone uploaded the physical and logical model from an ERD / data modeling tool into collibra Data Entity.Data Attribute logical structures and the Table.Column physical structures INCLUDING the link between the two (i.e. this table is the physical implementation of that entity; attributes -> columns; and foreign keys to collibra’s foreign key model)?

If so, what was the modeling tool? ERWin , Oracle SQL Developer Data Modeler (free), …

cc: @frank.thomas.enbridge.com

We will be doing this manually first, and looking at automating the updating. We don’t have one of these ‘established’ data modelling tools, but will look to update manually, driven through processes and people.

Any updates on the question of importing an ERD? Even if there is no automation for linking logical models to conceptual and physical models, a mechanism to get an ERD into a Collibra logical model would be a big help in gaining Engineering support for using Collibra.

This solution from Hackolade is now available to publish data models including Entity Relationship Diagrams to Collibra. More information can also be found here.

Does anyone have a solution for ingesting Erwin models?

Does anyone have a solution for integrating ER studio data models ?

Hi All,
what all roles does the integration account require for migrating the models to Collibra from ER studio

ER/Studio has a very tight integration with Collibra nowadays. You can push data models and their mappings to business terms to the Collibra catalog. Get your data architects helping out populating the catalog.