Creating Explicit Relationships between Communities and "external" Assets
Summary: Damien R discusses a challenge related to creating relationships between community domains and external assets, such as linking a "Customer" community to a "Business Data Domain." To address this, they have developed a solution using a "Community Anchor" asset type, enabling explicit relationships and facilitating reliable workflows. jurgentock appreciates the shared approach and suggests that Collibra could incorporate a feature for directly linking to a community.
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?
jurgentock
·1 year agoThanks for sharing this solution. It would be great if Collibra could somehow allow directly linking to a community.
Damien R
OP1 year agoIndeed, I'm so surprised it's not a default feature, it makes me wonder if I'm missing something or if there's a better way to do this...?