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.

AMDEX Corporation, a government contractor in the DC metro area, is seeking a Collibra engineer to join our team supporting DHS. This is a full-time, fully remote role that requires DHS suitability clearance. If you would like to learn more about this opening please respond. I have pasted the job description below this message for your review, or you can see it on our company's Careers page at  https://www.amdexcorp.com/amdex-ai-jobs .  Thank you! AMDEX.ai The Art of Data Science We are a seasoned Full-spectrum data solutions firm. We deliver insights, strategies, data analytics, and technical expertise to accelerate data modernization. We specialize in data sciences and cloud solutions, application development and maintenance, program management, and health IT operations leveraging experience and trusted talent to solve the federal government’s most pressing business and technical challenges. Without you, it’s just data. AMDEX is seeking an experienced Collibra Developer to join our dynamic team supporting a federal client.  Responsibilities: The focus of the work is to facilitate the customer’s mission fulfillment through data management support, i.e. continuously improving the degree to which data is visible, understandable, consistent, complete, and interoperable. Manage and improve manual and automated processes in the Collibra data governance tool and develop additional methods to automate workflows in that tool. Develop, implement, and manage an organization’s data catalog to ensure that data across all systems is accurately cataloged, described, and accessible to stakeholders. Maintain and enhance metadata standards to facilitate data discoverability. Responsible for facilitating data access and sharing across the organization. Have a strong understanding of data management processes and technologies, such as data warehousing, and data governance software. Be able to enhance the data governance platform with data quality, metadata, process management, etc. Develop, adhere to, and advise development teams on logical data models, to include plain language naming and description standards for database assets.  Required Qualifications: 8+ years' experience in Data Governance, Reporting, and/or Metadata management 2+ years' experience in configuring and supporting Collibra or other Metadata / Data Governance tool (s); completion of Collibra developer pathway training is required. Experience installing and maintaining software tools in Linux Experience with full-stack development and Java Experience in setting up complex database connections and queries Experience in designing and enhancing Collibra Workflows, Groovy/Java, BPMN  Exceptional communication and language skills pertaining to metadata tagging, naming, definitions, and cataloging Desired but not Required Qualifications: Experience in design of Big Data Environments which utilize technologies such as distributed processing, graph databases, AI, etc. Experience in the creation of IT data exchanges that adhere to National Information Exchange Model (NIEM)-based data structures and architectures, as well as experience in the creation of NIEM Domains. Experience in implementing a formal data quality improvement program, including data profiling, monitoring, and reporting Experience in implementing automated testing Experience in implementing DevOps or DevSecOps Education and Certifications: Bachelor’s Degree in Engineering, Computer Science, Information Systems, Library and Information Sciences (coupled with strong database/developer experience), or a related academic focus area.  Must have active DHS suitability / clearance Due to the nature of the contract, US citizenship is required.

AMDEX Corporation, a government contractor in the DC metro area, is seeking a Collibra engineer to join our team supporting DHS. This is a full-time, fully remote role that requires DHS suitability clearance. If you would like to learn more about this opening please respond. I have pasted the job description below this message for your review, or you can see it on our company's Careers page at  https://www.amdexcorp.com/amdex-ai-jobs .  If you're not currently looking for a new role but know someone that may be interested, please feel free to forward this information to them. Thank you! Deb Shalom AMDEX Corporation Collibra Engineer / Data Governance JOB NUMBER: 1637 | LOCATION: Remote CLEARANCE/ACCESS LEVEL: DHS Suitability AMDEX.ai The Art of Data Science We are a seasoned Full-spectrum data solutions firm. We deliver insights, strategies, data analytics, and technical expertise to accelerate data modernization. We specialize in data sciences and cloud solutions, application development and maintenance, program management, and health IT operations leveraging experience and trusted talent to solve the federal government’s most pressing business and technical challenges. Without you, it’s just data. AMDEX is seeking an experienced Collibra Developer to join our dynamic team supporting a federal client.  Responsibilities: The focus of the work is to facilitate the customer’s mission fulfillment through data management support, i.e. continuously improving the degree to which data is visible, understandable, consistent, complete, and interoperable. Manage and improve manual and automated processes in the Collibra data governance tool and develop additional methods to automate workflows in that tool. Develop, implement, and manage an organization’s data catalog to ensure that data across all systems is accurately cataloged, described, and accessible to stakeholders. Maintain and enhance metadata standards to facilitate data discoverability. Responsible for facilitating data access and sharing across the organization. Have a strong understanding of data management processes and technologies, such as data warehousing, and data governance software. Be able to enhance the data governance platform with data quality, metadata, process management, etc. Develop, adhere to, and advise development teams on logical data models, to include plain language naming and description standards for database assets.  Required Qualifications: 8+ years' experience in Data Governance, Reporting, and/or Metadata management 2+ years' experience in configuring and supporting Collibra or other Metadata / Data Governance tool (s); completion of Collibra developer pathway training is required. Experience installing and maintaining software tools in Linux Experience with full-stack development and Java Experience in setting up complex database connections and queries Experience in designing and enhancing Collibra Workflows, Groovy/Java, BPMN  Exceptional communication and language skills pertaining to metadata tagging, naming, definitions, and cataloging Desired but not Required Qualifications: Experience in design of Big Data Environments which utilize technologies such as distributed processing, graph databases, AI, etc. Experience in the creation of IT data exchanges that adhere to National Information Exchange Model (NIEM)-based data structures and architectures, as well as experience in the creation of NIEM Domains. Experience in implementing a formal data quality improvement program, including data profiling, monitoring, and reporting Experience in implementing automated testing Experience in implementing DevOps or DevSecOps Education and Certifications: Bachelor’s Degree in Engineering, Computer Science, Information Systems, Library and Information Sciences (coupled with strong database/developer experience), or a related academic focus area.  Must have active DHS suitability / clearance Due to the nature of the contract, US citizenship is required.

We're pleased to share that Collibra has been named a Leader in the I DC MarketScape: Worldwide Data Intelligence Platform Software 2026 Vendor Assessment (doc #US54118226, August 2026).The assessment evaluated 15 vendors across capabilities and strategies.  The excerpt includes IDC's view of the market, its advice for technology buyers, and the full evaluation of Collibra. If you're building the case for governed data and AI inside your organization, we think it's a useful read to share with your stakeholders. Read the excerpt: https://www.collibra.com/resources/idc-marketscape-worldwide-data-intelligence-platform-software-2026-vendor-assessment

Hi everyone, I'm facing a workflow design challenge and would appreciate any guidance from those who have implemented similar patterns. Background Originally, our Data Definition workflow was started directly from a Business Term asset page. In that scenario, each user task displayed the asset as the Related Resource in the user's Inbox and task details. Users could immediately understand which asset they were working on and navigate to it easily. We have recently redesigned the process. The new flow is: User launches a workflow from a start form (not from an asset page). The workflow creates a new Initiative asset. The workflow creates relationships between the Initiative and multiple Business Terms. A Call Activity launches a child workflow (Data Definition Process). Users receive tasks within the child workflow. The Problem Because the workflow is initiated from a form rather than from an asset page, the resulting user tasks do not display a Related Resource . The Initiative asset is successfully created and its ID is available throughout the process. I can retrieve the asset and its metadata in Script Tasks without any issue. However, the user tasks still do not show the Initiative as the Related Resource, making it difficult for users to identify which Initiative a task belongs to. What I've Already Tried Passing the Initiative ID through Call Activity input mappings. Passing an item variable through the Call Activity. Recreating the Initiative asset context in the child workflow using: Recreating the Initiative asset context in the child workflow using: UUID initiativeId = string2Uuid(execution.getVariable("initiative")) def initiativeAsset = assetApi.getAsset(initiativeId) Storing the Initiative asset ID and name as workflow variables. The child workflow receives these values correctly, but the Related Resource remains empty. My Question Is it possible to associate a workflow instance or user task with an asset after the workflow has already started , so that the asset appears as the Related Resource in the Inbox? More specifically: Can a workflow started from a global form dynamically set a Related Resource later in the process? Is there a specific workflow variable (such as item , resourceId , etc.) that controls this behavior? Or is the Related Resource only determined at workflow instantiation time when the workflow is launched directly from an asset page? Any recommendations, best practices, or examples would be greatly appreciated. Thanks in advance!