Collibra Community

I just learned our SQL DBAs have been manually exporting metadata from Collibra and importing it to Snowflake. They are migrating all data on virtual machines to Snowflake Cloud. I know there are API on both sides. Has anyone written a script that would export Collibra metadata (Collibra holds everything, old databases are barren) and create a Snowflake DDL file to recreate databases in Snowflake?

Hello everyone! You can find the slides presented at this link . See you at the next User Group Francophone session (Oct 30)! Best regards, Nicolas Pirou

Hi, We would like to govern APIs, by ingesting them with the Python openAPI integration. When doing so, you get a nested structure of API > API Endpoint > data structure > data element. However, how do you relate the data attributes with the data elements. For this, we would like to use a data product and data product port. Some of my colleagues do not think that this can be a data product as it does not contain any data. You just link an ingested API to data attributes and would not need a data product. But then, how can you consume the API as a user? Then it is still usefull to use a data product. Any other opinions?

Data requests used to come from people. Now they come from AI agents too, and both expect answers at self-service speed. The challenge: how do you move that fast without losing control over your most sensitive data? Join us on October 20, 2026 (5 PM CET / 11 AM ET / 8 AM PT) to see how Collibra Data Access makes it possible. We'll cover how to: Centralize access at scale — request, approve, provision, and govern it all from one place Keep sensitivity with the data — classifications travel with your data, dynamically masking PII based on role, attributes, or policy Govern agents like users — apply the same policies and guardrails to AI agents that you apply to people Deliver speed with oversight — get people and agents the data they need in minutes, with full auditability You'll hear from Bart Vandekerckhove (Principal Product Manager), Meredith Bailey (Product Marketing Director ), and Chad Woodhead (Staff Sales Engineer). Register now to save your spot →

Hi all, We use Collibra as our data catalog and governance platform, and our data office is about to start scoping a group-wide data quality tool. I've been asked to look at how it should fit with Collibra. I'd love to hear from anyone who has already done this. How did you set it up in practice? Where do you define your business quality rules, in Collibra or in the DQ tool? Where do you manage ownership and stewardship? Did the out-of-the-box operating model work for you, or did you have to adapt it? And was the integration easy, or did it take a lot of development effort? Most of all, I'd like to know what difficulties you ran into, and what you would check on the tool's side to make sure it works well with Collibra, how quality results come back into Collibra, how the tool links its controls to the assets already in the catalog..etc Thanks a lot in advance, any feedback is welcome!

I've configured a workflow with a start event set as 'asset added' and 'status changed.' It triggers perfectly when I manually add an asset or update its status, but it doesn't trigger when assets are imported using the Import API. I've read the documentation mentioning that the Import API bypasses workflow triggers. Given this, I'm seeking advice on the best approach to ensure that workflows trigger appropriately upon asset import.