Organizational concepts best practices

Updated 

Applies to: Attributes, Relations, Complex Relations and Asset types and Statuses

Recommendation

After creating an attribute type, relation type or status, ensure that you assign it to an asset type or complex relation type.

  • For relation types, ensure that you assign the relationship type on both sides of the relation, source, and target.

  • For attribute types, define the appropriate data type, for example, selection versus multiple selection. Ensure that you assign appropriate statuses to assets.

Impact

By not assigning the new attribute types, relation types or statuses to asset types or complex relation types, you risk the following:

  • Your

     

    Collibra

     

    platform performance may degrade due to:

    • The creation of unnecessary characteristics for an asset type.

    • The creation of access calls for unwanted characteristics, which then display in views and diagrams.

  • Your users' experience can suffer resulting in:

    • Confusion surrounding which items to use or populate.

    • Challenges navigating to the desired page.

  • You may have challenges migrating your

     

    Collibra

     

    platform, resulting in:

    • The creation of synchronization issues across environments such as Dev, Test and Prod.

    • Avoidable system errors during the migration process.

  • The lifecycle of your assets and workflows are weakened.

Migration challenges:

  • Can create synchronization issues across environments, for example, Dev/Test/Prod.

  • Can cause system errors during migration process.

Remediation approach

  • Review the requirements and design causing the need to deviate from the guidelines.

  • Run the Operating Model Reverse Engineering, OMRE, on a regular basis to identify unidentified or orphan assets, statuses, relations and attribute types and remove unused or unassigned resource types.

Topic area

Structural Concepts (Metamodel)

Criteria measurement type

Configuration

Review Meta model configuration to ensure all custom Attribute Types are assigned to an Asset Type or Complex Relation Type. You can write a custom workflow to check for this condition.

Additional information

For more information, go to following resources: