Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add tooltips around Domain Type to explain Domains #13879

Closed
Ashish8689 opened this issue Nov 7, 2023 · 1 comment · Fixed by #13909
Closed

Add tooltips around Domain Type to explain Domains #13879

Ashish8689 opened this issue Nov 7, 2023 · 1 comment · Fixed by #13909
Assignees
Labels
UI UI specific issues

Comments

@Ashish8689
Copy link
Contributor

Issue from #13316 (comment)

  • Needed some info/description around different domain types on UI

Screenshots or steps to reproduce

image

Version:

  • OS: [e.g. iOS]
  • Python version:
  • OpenMetadata version: [e.g. 0.8]
  • OpenMetadata Ingestion package version: [e.g. openmetadata-ingestion[docker]==XYZ]

Additional context
Add any other context about the problem here.

@Ashish8689 Ashish8689 added the UI UI specific issues label Nov 7, 2023
@sureshms
Copy link
Contributor

sureshms commented Nov 9, 2023

@Ashish8689 Here is some reference for domain types - https://www.datamesh-architecture.com/#mesh

Descriptions should be:
Source-aligned
Domains closer to online services and transactional databases that include events, and transactional data.

Aggregate
Domains that collect and curate the data from multiple source-aligned to provide aggregated data and data products, such as Customer 360, Customers sessions, etc., for other domains to consume.

Consumer-aligned
Domains that are user-facing where the end product of a combination of data from various domains are available for business users or data citizens for data-driven decision-making.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
UI UI specific issues
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants