Collibra Community

Announcements

Meredith Bailey6 days ago

Notifications Reimagined: Slack Integration and Notification Center

Hey Collibra Community, We're excited to launch two powerful upgrades to bring data governance directly into your workflow: Collibra for Slack and our new Notification Center . This means less inbox clutter, fewer missed tasks and more efficient collaboration. With our new Slack Integration, you can: Receive real-time alerts on mission-critical tasks. Reply directly to comments and assessments from within Slack. Search and share data assets without switching apps. With the new in-app Notification Center, you can: Centralize and manage all platform notifications in one place. Personalize your alerts by frequency, type, and channel (Email, Slack, and soon, Teams!). Star important items so you never lose track of key updates. These new features are all about making data governance more intuitive and efficient. Want to get started? Head over to our documentation or view our demo video to see the integration in action

UI and design

paulinefouquat2 months ago

Customisable homepage

Hi, I'd like to know if some of Collibra users have customised their homepage? Could some of you share what you have done in terms of customisation? And how you did it? The idea is to understand to what extend the homepage can be redesigned... Thanks a lot

Developers

scottbenson2 months ago

Weird Validation Situation

I have the unusual situation where I have 5 text attributes, each of which need to be validated against 20 colors and some other items in the same text field. The fields need to stay as text fields so a drop down is not an option. The example below shows a piece of the validation. rule{ anyOf{ condition{isEqual(attributes.'Field1'?.first(),'Red')} condition{isEqual(attributes.'Field1'?.first(),'Blue')} } } I could write 5 separate validations, but the problem occurs when a new color is added - I would need to update 5 separate validations. OR I could write 1 large validation which contains all 5 fields and under each field list the 20 colors - but the same problem occurs when a new color is added. Has anyone else run into a similar problem and be willing to share their solution? Thanks, Scott Sc

Developers

davidbotzenhart2 months ago

API to add Data Set to Collibra Data Basket

Is there an API Endpoint to add a Data Set to the Collibra Data Basket for an user?

Product Q&A

ivantokic2 months ago

Calculation of the Seats for the new Licensing Model

Hello, we have not yet transitioned to the new licensing model and there are some situations not clear. If someone who had the experience, can shed some light, it would be much appreciated. All is clear on the way a license is determined for individual user, based on the role or membership in a certain group - higher license always prevails. There is also the buffer of 20% to manage consumption and 9 weeks in which the consumption is monitored and then some restrictions are implemented. What is not clear is the counting of the licenses. Example: User A occupies Viewer license and is at some point assigned a role that requires Contributor license based on some permission. At that point user A is +1 for Contributor license count. What happens if the user A no longer has that role that requires Contributor license? Is he still counted in the Contributor license count even though he now occupies the Viewer license? Is there a time period in which you are counted in the higher license count or does it change the second you lose the role/are not in the group anymore? Documentation does not specify anything related to this and it is hard to explain to the clients and cover all the possible situations. And there are a lot of them, imagination goes wild, ex. someone puts wrong user in a group and he now occupies higher license forever even though never used permissions that counts for a higher license? Update: found a part on the Allowance limits if the consumption is calculated weekly that means that user A is counted for Contributor license only in weeks that he occupied a role/group that requires some permission from Contributor - is that correct and tested in the real world? Thanks in advance, Ivan

Classification

allisonwojcik2 months ago

Classification- Case Sensitivity

We have started using the classification with regex for Column names. So far the majority has been promising. But we are facing issues with case sensitivity. The documentation points out- You don't need to worry about capitalization in your regular expression because regular expressions are not case sensitive. But we are seeing inconsistencies where columns in some cases are lower case and some are upper case- same spelling. Lower is captured, upper is not? I have opened a ticket. But wondering what others are seeing. Ex. CLIENT_NAME vs Client_Name vs client_name. Both Client_Name vs client_name are classified correctly, but not CLIENT_NAME.

User Experience

Notifications Reimagined: Slack Integration and Notification Center

Customisable homepage

Weird Validation Situation

API to add Data Set to Collibra Data Basket

Calculation of the Seats for the new Licensing Model

Classification- Case Sensitivity

User Experience

Notifications Reimagined: Slack Integration and Notification Center

Customisable homepage

Weird Validation Situation

API to add Data Set to Collibra Data Basket

Calculation of the Seats for the new Licensing Model

Classification- Case Sensitivity