In order to correctly indicate the physical location of the data, the Druid datasets in DataHub should have a public or private cluster designation. In addition, druid data has the following nesting: Druid > druid/v2/sql > druid. Should they be? Should this nesting be flattened instead?

Acceptance criteria:

• Druid datasets are nested under Druid > public are Druid > private depending on whether they are in the public or private cluster.