Collibra Community

Best practices

Created Nov 17, 2023

7 members

144 discussions

Welcome to the Best Practices Discussions space—a forum dedicated to sharing and exploring effective strategies for utilizing Collibra's Data Intelligence Platform. Engage with peers and experts to discuss real-world implementations, share success stories, and gain insights into maximizing the value of Collibra within your organization.

Kaushal Hissaria
15 days ago
Improving User Attribution in Collibra API
We're using Collibra as our data catalog and face challenges with user attribution. Currently, external applications interact with Collibra using a single account, making it difficult to track who made specific changes. We are considering: User Impersonation : Passing individual user identities through the API. Enhanced Logging : Capturing user info at the application level. API Gateway : Managing authentication to forward user credentials. Alternative Authentication : Using individual user tokens if supported. We seek solutions that ensure accountability while maintaining security and performance. Any insights on similar challenges are appreciated.

0
Julie Prigge
1 month ago
Best Practices for Archiving Assets in Collibra

What best practices have you implemented to archive obsolete assets? After time, Obsolete assets clutter current assets and our stewardship teams are looking for solutions to archive those into a separate area to keep current assets clean. How have you used Collibra to do this and what policies or procedures have you established?
1
ChristianK
3 months ago
Any limitations creating / building a lot of validation rules?
Hello Community Has anybody experienced any issues or limitations if you were creating / building a lot of validation rules? Anything specific to be considered while scripting the validation rules? Limitations could be effectivity, speed, easiness, bundling of rules in scripts. Where would I find any relevant information? Thanks & regards, C

0
user_dfbd9d
7 months ago
Actions Dropdown on Asset Views
Hello Collibra Community, I am reaching out to seek advice regarding an issue we've encountered while testing the new UI in our development and test environments before we deploy it at the end of month. In the previous UI, on an asset page there was an 'Actions' dropdown that held all the workflows for each asset. However, in the new UI, the dropdown is no longer labeled 'Actions' and instead lists the workflows in alphabetical order and by clicking the box, whichever workflow is listed first is kicked off. We see this causing a lot of unnecessary confusion for our business users who aren't in Collibra every day, as the previous 'Actions' dropdown was far more user-friendly. Our current workaround is to create a dummy workflow listed first to prevent users from causing any accidental workflow instances, but we wanted to see if there was a better recommendation. Has anyone else experienced this issue? If so, how did you address it? Thanks in advance!

1
ivantokic
10 months ago
Sample data shows "invalid value" as a result for columns that have Technical Data Type different than CHAR
Hi, I've been using sample data functionality and have encoutered a problem that I can't solve. I am s Sysadmin user and from what i can see all the requirements for using sample data are met. When requested, sample data is shown for columns that have Technical DataType listed as CHAR and for all other columns the result is shown as "invalid value". The table from which the sample is being extracted has real values. If someone can point me in the right direction to solve this problem, I would be really grateful.

3
barrefors
11 months ago
Most efficient way to update attribute values and responsibilities
Hello, I have a workflow which takes a set of values from a form and "upsert" these to an attribute. What I mean with upsert is that any value which does not exist in the new list should be removed an any values which only exist in the new list of values should be added. I had a few different approaches to this: Try to update existing values and if not the same amount of values, remove or add. I didn't like this because I don't have IDs on the incoming values and hence I don't know which should be updated and not. Compare values and create two sets, to be added and to be removed. This became a bit complex and caused a lot of API calls. Delete all existing, add all new. In the end I went with this because I could leverage bulk APIs and didn't have to do a lot of comparing. But of course it's a bit overly aggressive. The best would be some sort of upsert api call, but that doesn't exist. I've now ran into the same issue when propagating responsibilities to linked assets when responsibilities of the existing asset is changed. So would like to see how others have decided to solve this type of problem with the lack of an upsert function. Is there maybe a way to see what change triggered the workflow? I have it start when a role is added or removed. Or would it be smarter to use the history somehow? Thanks in advance, Björn

1
nuriia_rose
1 year ago
Collibraverse on 16th May in Brussels | take-aways from the event
Thanks to Collibra and Datashift colleagues for organizing this onsite Event! Next one customer events at Collibra office in Brussels : Data Deep Dive on 16th September Collibraverse in November There were interesting Customer and Collibra presentations. I would like to share my take-aways: Euroclear Collibra Customer since 2019 (?) Euroclear has a Change Manager and Data Community Lead, who together with colleagues from Datashift work together with Data Governance lead on adoption of Collibra. Role-based training E-learning Knowledgebase articles in Collibra (asset type "knowledge base" in "create and document" domain in Collibra). User journey is individual, the users all follow the same steps but at individual pace . Leassons learned Change management should be from Day1 of Collibra introduction Put the Data Community Approach much earlier KBC I remembered only, that KBC uses a lot of validation rules in Collibra to make a lot of checks. These validation rules apply to certain asset type IDs. If you can program in pyton, then ChatGPT can translate your code into groovy (for the workflows). Collibra Data Product asset type, available in October 2024 Very insightful presentation of Peter Princen, I hope the slide deck will be shared with participants! Collibra is planning Data Product asset type available in October 2024.

2
franksprague
1 year ago
Community and Domain Structure Help
Hello, My organization is trying to understand how to structure our communities and domains. We currently are struggling to understand the best way to architect our community and domain structure. We have reviewed Collibra's documentation on this and we are still unsure as to how to proceed. It was suggested that we use AD as a model, but our AD structure is flat. This leaves us needing to create something custom. If there are any organizations that had a create a custom structure that can share insights into the process I would appreciate hearing how you arrived at the current structure you have! Thank you, -Will

1
kirkvilhauer
1 year ago
Best practice for handling "missing from source" assets?
Hello, Is there a best practice for handling “missing from source” assets? For example, we have renamed some columns in a table and now the old columns show as a status of “missing from source”. This would also apply if we moved a table from one schema to another as we made a mistake with a mass cloud migration. Should we delete these “missing from source” assets or is there a flag to eliminate these when refreshing the metadata? Thanks!

2
Brian Lloyd
1 year ago
Best practice when Data Asset names change on a refresh?
What is the best practice to handle the situation of a data asset (Schema, Table, Column, etc) name changes on a refresh and the cataloged assets have human entered metadata and additional characteristics defined? I know the existing cataloged asset has its status changed to “Missing from source” but how do we move the custom metadata provided by my stewards from the old (missing) assets to the newly cataloged assets? If this happens on a table with hundreds of columns what is the best way to migrate the information supplied by people to the newly cataloged stub records? Thank you for helping us with this issue! -Brian

2

Improving User Attribution in Collibra API

Best Practices for Archiving Assets in Collibra

Any limitations creating / building a lot of validation rules?

Actions Dropdown on Asset Views

Sample data shows "invalid value" as a result for columns that have Technical Data Type different than CHAR

Most efficient way to update attribute values and responsibilities

Collibraverse on 16th May in Brussels | take-aways from the event

Community and Domain Structure Help

Best practice for handling "missing from source" assets?

Best practice when Data Asset names change on a refresh?