F

4 Messages

 • 

1K Points

Friday, October 4th, 2024 2:51 PM

Tips for Simplifying Asset Types and Attributes?

Hello Collibra Community,

We are in the process of implementing the data catalog in our organization and are looking for some advice.

Specifically, we want to streamline the model by limiting the number of domain types, asset types, and attributes at the start.

While we recognize the value in the full range of options Collibra provides, our approach is to begin with a simplified model to make things easier for our users.

As adoption grows, we plan to gradually introduce more elements. For now, we'd like to reduce the number of pre-configured objects, but we haven’t found a way to delete or hide those we don’t plan to use at this stage.

Has anyone faced a similar need and found a way to hide unused attributes in the configuration?

Thanks in advance for your help!

11 Messages

 • 

1.1K Points

8 days ago

The approach you have chosen is very good. You should not try to map everything that is possible at once in a big bang approach. Rather, it is advisable to build use cases in Collibra step by step and add further asset types as required.

To reduce the amount of asset types and attributes visible to the users, you can edit the asset type's assignment and remove the characteristics (relation types, attribute types) and domain types that you want to hide.

117 Messages

 • 

8K Points

5 days ago

A few tips

  • Scopes.
    • Leave Global Assignment in place and treat is as a library artifact / shunting yard for new attributes & r/ships (as Collibra add them)
    • And have (at least 1) site-specific Scope and just put in there the Characteristics you need
    • Be aware if you have Default Scope in the Root of your Community then new Domains will inherit Default, rather than your company-specific Scope. This can case confusion. 
    • With Reference Data, treat a Scope as a message-type and then spin up one for each msg-type. Put Reference Data in a dedicated Community.
  • Metamodel, use the power of inherited roles to cascade rather than manually (or via WFs) complete your stewardship
  • Assets, tip if they don't belong to any Domain Types then they can't be used
  • and KISS
Loading...