This article addresses common questions and concerns related to the integration between Team Server and Collibra. It provides insights into property mappings, relationship mappings, domain mapping, and model publishing processes, aiming to clarify and streamline the integration between the two platforms.
If you are facing:
Then this Article is for you!
When mapping properties between the two tools, you will need to understand the meaning of the properties in both tools and may need to consult with the Collibra administrators.
Built-In properties refer to out-of-the-box properties of objects such as Definition, Data Type, and PK / FK flags. Custom properties (Managed Attributes) are specific to Team Server Core and can be created, by the administrator, from attachments or scratch within Team Server Core.
This feature will scan your Collibra Properties and generate new custom ones in Team Server Core automatically. Exercise caution when using the Auto Create Properties tab, as this may create a large number of new properties in Team Server Core that may not be required.
Consult a Collibra expert to determine if custom properties need to be built for the interface to function effectively.
When running the Synchronization between the Team Server Definition properties to Collibra’s Definition properties can only be done on a 1-to-1 basis.
Consult Collibra experts to clarify Collibra-specific properties such as Sample Values and Sensitivity Category.
Relationship mappings between Glossary and Term objects in IDERA and Collibra follow a 1-to-1 mapping. This may require some consultation with the Collibra administrators on the semantics of the Collibra glossary. Out of the box Collibra has the following relationships, which we suggest the following mappings. Its important to get this right as the Collibra community need to understand how to navigate the ontologies we can form in Collibra using these relationships.
Note, Team Server recognizes the inherited relationships between parent asset types in Collibra.
| Source Type | Target Type | Collibra Relationship | Team Server Relationship | Flip Direction |
| Asset | Asset | related to/impacted by | Relates to/relates | No |
| Business Asset | Business Asset | groups/grouped by | Has attributes/ is attribute of | Yes |
| Business Term | Business Term | is synonym of/is synonym of | is synonym of/is synonym of | No |
The remaining Team Server relationship “types/type of” between business terms is an important one that represents taxonomies. This is where you need to consult with the Collibra team. It may be that the existing “groups/grouped” by relationship in Collibra could be used for taxonomies in which case this should be mapped to the “types/type of” relationship in Team Server. Alternatively you can create a new relationship between Terms in Collibra “types/type of” which can be mapped to the corresponding “types/type of” in Team Server.
Consider setting up a separate Collibra Community and Domains so that objects in Team Server maintain organizational clarity.
Align Collibra’s Physical and Logical Data Dictionaries with ER/Studio data model for seamless integration.
Establish a hierarchical structure in Collibra’s Community to map ER Studio data models effectively.
Define sub-communities and domains in Collibra to correspond with ER Studio physical and logical data dictionaries.
Unclear understanding of property mappings, relationship mappings, domain mapping, and model publishing processes between ER Studio Data Architect and Collibra can lead to confusion and inefficiencies in the integration process. If you need further assistance make sure to review our online documentation at:
https://docwiki.embarcadero.com/TeamServer/ERStudio/203/en/Understanding_Collibra_Integration
Was this article helpful?
