Team, sub domains are critical for metadata management. To create a sub-domain like Customer/Activity is the option to use: table_pattern: allow regex to control only the entitles in the sub domain transformers: - type: "set_dataset_browse_path" To create the subdomain in the UI would that be the correct approach to have datasets broken out by sub domains?

Hi @nice-autumn-10105! @big-carpet-38439 & @dazzling-judge-80093 are currently working on support for Domains & Containers - they should be able to provide some direction!

@nice-autumn-10105 -- Why are sub domains so critical? Could you not achieve this using flat domain hierarchy?

The logical, and sometime physical grouping of data is so critical. You have a store domain. 1000 entities. Inside that domain there are 10 entities about Store hours. While directly related to the store, those entities have a different source, different owners, etc. For example a sample transform to make this look right: - type: "set_dataset_browse_path"     config:       path_templates:         - "/Store/Store Hours/<entities>" - type: "set_dataset_browse_path"     config:       path_templates:         - "/Store/Store Locations/<entities>"

Thanks for that context

Like our top level domain has over 1000 entities. Even just having the UI able to break those out with simple default dataset path (current state) helps. I know in things like Erwin and other modeling tools sub-domains can be quite complex. My question was really around making navigating the UI easier,