domain types

hi - is it good practise to create new domain types to control where assets can be created, or should the 'out of the box' domain types be the utilised in favour of any new domain types?

thanks

matthewtaylor

Posted 11 months ago·Last reply 10 months ago

3 comments

Eleftheria Makrydaki

·10 months ago · Edited

Hello! Thank you for your question! As @Lance Harlan pointed it really depends on your goal. I'll just give you some pros and cons of both options, as there are several factors to consider:

Using OOTB domain types

Pros:

Simple and standard: they align with the standard operating model, making it easier to use standard solutions.
Ease of management: fewer asset types mean less effort in managing the asset model, right?
they're more user-friendly: well-known asset type names make it simpler for end-users to understand the content.

Cons:

Not so flexible as they may not cover all use cases

Creating new domain types

Pros:

Customisable : new domain types allow for direct relation types, avoiding incorrect relations.
Flexible: you can tailor asset types to specific needs

Cons:

The asset model can become complex, and requires significant effort to configure and maintain
UI becomes more complex

Overall, your decision should be based on the specific use case and the complexity of the metamodel. I hope this helped!

Thank you !

Eleftheria Makrydaki | Product Operations Manager

Brittany Crews

·10 months ago · Edited

One thing to consider is that when you add custom assets, you are potentially creating more work for yourself in the long run as they may require custom diagrams to accommodate those custom assets. If you stick with OOTB, the OOTB diagrams will display properly. This is why my organization is trying to only use OOTB relations/assets/etc.

Lance Harlan

·10 months ago · Edited

Obviously, it depends on the goal and stategy for your data program, but I would use the OOTB domain types first and then go from there. I did make one custom type called Policy Glossary and added it under the Policy Domain, but that was the only one I felt the OOTB didn't show adequately