Skip to content

Commit 86d3de0

Browse files
Pencil fixes to merge
1 parent 35be94d commit 86d3de0

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

articles/purview/concept-best-practices-governing-domains.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -15,9 +15,9 @@ Understanding your domains is critical for effective data governance. In this ar
1515

1616
We also review how to apply several Purview features to data governance. We show how to:
1717

18-
- Use collections for creating a domain structure, segregating governance roles and responsibilities, and managing access to metadata
19-
- Use the glossary to define key terms and data elements, and cover when it might be helpful to separate glossaries for different business areas
20-
- Use business assets to model the real-world concepts and objectives within a domain
18+
- Use collections for creating a domain structure, segregating governance roles and responsibilities, and managing access to metadata.
19+
- Use the glossary to define key terms and data elements, and cover when it might be helpful to separate glossaries for different business areas.
20+
- Use business assets to model the real-world concepts and objectives within a domain.
2121

2222
Let's dive into the world of domains and discover how Purview can help improve your data governance practices.
2323

@@ -41,7 +41,7 @@ In the next sections, we'll walk through how to:
4141
- Define responsibilities for the domain.
4242
- Implement a domain-driven governance approach in Purview.
4343

44-
## Analyzing a domain
44+
## Analyze a domain
4545
When you establish an approach to data governance, a domain model can help create a shared understanding of the domain between technical and business experts. A domain model is a description of the real-world concepts and activities inside the business domain you want to govern. You’ll start by sketching an abstract view of your problem space, then refine it as you work toward the solution you implement in Purview. Don’t be afraid of change. You’ll learn and improve your approach as you tackle new domains.
4646

4747
Begin by describing business activities and their connections. This should be a collaborative effort that involves data and business stakeholders. This doesn’t have to be formal—use a whiteboard to create a picture that makes sense to everyone.
@@ -117,11 +117,11 @@ In this step, we create a blueprint for the context we want to show in Purview.
117117

118118
Adding these relationship definitions means we’ll now be able to link datasets to business process assets in Purview. This will help us contextualize data for both business and technology stakeholders.
119119

120-
### Step 3.2: Adding business assets
120+
### Step 3.2: Add business assets
121121

122122
Now let’s add the business processes (ledger management, order placement, etc.) and two systems (Contoso billing, General ledger) from our diagram.
123123

124-
:::image type="content" source="media/concept-best-practices-domains/08-business-assets.png" alt-text="Screenshot from Purview business assets page shows a list of business assets including 6 business process assets for 'ledger management', 'order placement', and others along with 2 systems assets called 'Contoso billing' and 'General legder.":::
124+
:::image type="content" source="media/concept-best-practices-domains/08-business-assets.png" alt-text="Screenshot from Purview business assets page shows a list of business assets including 6 business process assets for 'ledger management', 'order placement', and others along with 2 systems assets called 'Contoso billing' and 'General ledger.":::
125125

126126
We’ll create data domain assets for 'account' and 'order' as well because these are not only important terms but key entity concepts in these business areas. This will help us show business context for key data entities.
127127

@@ -137,7 +137,7 @@ Analytical data sources often centralize data that’s shared by multiple depart
137137

138138
Then we’ll set up scoped scans to divide the data between areas of responsibility. When you set up a [scoped scan](concept-scans-and-ingestion.md#scope-your-scan), you can choose specific folders or tables that apply to each area of responsibility so you can scan the right data into a collection.
139139

140-
:::image type="content" source="media/concept-best-practices-domains/11-scope-scan.png" alt-text="Screenshot of Purview scan settings showing that data will be scanned into the Finance domain collection next to a screen shot showing the Purview 'scope your scan' panel with individual tables selected for scanning under the main database.":::
140+
:::image type="content" source="media/concept-best-practices-domains/11-scope-scan.png" alt-text="Screenshot of Purview scan settings showing that data will be scanned into the Finance domain collection next to a screenshot showing the Purview 'scope your scan' panel with individual tables selected for scanning under the main database.":::
141141

142142
### Step 5: Contextualize your data
143143

0 commit comments

Comments
 (0)