Collibra Community

Developers

Damien R2 days ago

Creating Explicit Relationships between Communities and "external" Assets

We have been struggling with the lack of relationships between communities (or domains) and assets located outside of their path. So if we have a "Customer" community and a "Customer" business data domain asset that's located under a "Business Data Domains" community, we would want to go from the one to the other, for example to check the status of the Customer business data domain asset and if it's "active" get the business terms that sit within the Customer community To help with this we've added a "Community Anchor" asset type and use it whenever we want to make the relationship between a Community and an Asset explicit: the "Customer" community has an "Anchor" domain with a "Customer Community Anchor" anchor asset. We can then easily create a relationship between the anchor asset and the business data domain asset. This pattern is especially convenient for workflows that often need to move from the one to the other with confidence. We used to do this by matching names only, and it was not always reliable. Hopefully it might help some people with the same issue but I'm also very curious to hear how you handle this situation? Do you use similar patterns?

Data Quality & Observability

emiliawalencik11 month ago

Asset Quality Page

Hello there, Can anyone guide me on how to set up the aggregation path and relations to view different charts representing various quality dimensions? I'm failing to do so, I have no idea where I'm making a mistake. This is the quality tab view I currently see: This is the aggregation path I created: This is a traceability diagram:

Data Catalog

Grant Rollerson1 month ago

Building Reporting Specifications in Collibra

Reporting Specifications I want to Build out my reporting specification in Collibra hand it to a Tableau builder dude Tableau report is subsequently built and harvested into Collibra, along with lovely lineage to Redshift My Q is, what asset types do you use to build the report specification? This is a business asset so it feels wrong to use Data Product b/c while Blue like Report, it takes inputs and outputs (both data assets). Data Set & Data Element, but again both are data assets whereas a report specification is a business construct. I could use Report, with Business Terms, Metrics & KPI for the report grain/constituents. Then; relate the Report to the actual Tableau blue assets (Dashboard or Worksheet) via OOTB Business Asset groups Business Asset. if keen, relate the functional grain to the Tableau Data Attribute via Business Asset represented by Data Attribute. I ask also b/c we have legacy Report Catalogs with Tableau reports built manually as Report and Report Attributes that I want to keep, because our business users get confused by the Tableau Op Model.... so it's easier to leave them there and just relate them to the harvested Dashboard etc. In the end the conclusion was KISS Specifications > Business Term Business data points in the Specification > Business Term (and Metrics, where relevant) Anyway, keen to hear what others have done.

Operating model

Nuriia Rose1 month ago

Attribute (Selection) | Is it possible to add more items for selection later?

Hi everyone, for our purposes I created a custom Attribute data-refresh-rate with the following selection : daily daily, on-trigger weekly monthly yearly on-demand on-demand (user call) Would it be possible to add more items to Selection? or should I delete the old Attribute and create the same one from scratch again, in case more selection items should be added? adding the screenshot here:

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

Best practices

Julie Prigge2 months 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?

Operating Model

Creating Explicit Relationships between Communities and "external" Assets

Asset Quality Page

Building Reporting Specifications in Collibra

Attribute (Selection) | Is it possible to add more items for selection later?

Weird Validation Situation

Best Practices for Archiving Assets in Collibra

Operating Model

Creating Explicit Relationships between Communities and "external" Assets

Asset Quality Page

Building Reporting Specifications in Collibra

Attribute (Selection) | Is it possible to add more items for selection later?

Weird Validation Situation

Best Practices for Archiving Assets in Collibra