Merge pull request #188622 from whhender/catalog-updates-3

Updating author, date, and Acrolinx

Author: ShannonLeavitt

articles/data-catalog/data-catalog-how-to-manage.md

@@ -1,64 +1,64 @@
 ---
 title: Manage data assets in Azure Data Catalog
 description: The article highlights how to control visibility and ownership of data assets registered in Azure Data Catalog.
-author: JasonWHowell
-ms.author: jasonh
+author: ChandraKavya
+ms.author: kchandra
 ms.service: data-catalog
 ms.topic: how-to
-ms.date: 08/01/2019
+ms.date: 02/15/2022
 ---
 # Manage data assets in Azure Data Catalog
 
 [!INCLUDE [Azure Purview redirect](../../includes/data-catalog-use-purview.md)]
 
 ## Introduction
-Azure Data Catalog is designed for data-source discovery, so that you can easily discover and understand the data sources you need to perform analysis and make decisions. These discovery capabilities make the biggest impact when you and other users can find and understand the broadest range of available data sources. With these elements in mind, the default behavior of Data Catalog is for all registered data sources to be visible to and discoverable by all catalog users.
 
-Data Catalog does not give you access to the data itself. Data access is controlled by the owner of the data source. With Data Catalog, you can discover data sources and view the metadata that's related to the sources that are registered in the catalog.
+Azure Data Catalog is designed for data-source discovery, so that you can find and understand the data sources you need to perform analysis and make decisions. These discovery capabilities make the biggest impact when you and other users can find and understand the broadest range of available data sources. With this information in mind, the default behavior of Azure Data Catalog is for all registered data sources to be visible to and discoverable by all catalog users.
 
-There might be situations, however, where data sources should only be visible to specific users, or to members of specific groups. In such scenarios, users can take ownership of registered data assets within the catalog and then control the visibility of the assets they own.
+Azure Data Catalog doesn't give you access to the data itself. Data access is controlled by the owner of the data source. With Azure Data Catalog, you can find data sources and view descriptive information about the sources that are registered in the catalog.
+
+There might be situations, where data sources should only be visible to specific users, or to members of specific groups. In such scenarios, users can take ownership of registered data assets within the catalog and then control the visibility of the assets they own.
 
 > [!NOTE]
-> The functionality described in this article is available only in the Standard Edition of Azure Data Catalog. The Free Edition does not provide capabilities for ownership and restricting data-asset visibility.
->
->
+> The functionality described above is available only in the Standard Edition of Azure Data Catalog. The Free Edition does not provide capabilities for ownership and restricting data-asset visibility.
 
 ## Manage ownership of data assets
-By default, data assets that are registered in Data Catalog are unowned. Any user with permission to access the catalog can discover and annotate these assets. Users can take ownership of unowned data assets and then limit the visibility of the assets they own.
 
-When a data asset in Data Catalog is owned, only users who are authorized by the owners can discover the asset and view its metadata, and only the owners can delete the asset from the catalog.
+By default, data assets that are registered in Azure Data Catalog are unowned. Any user with permission to access the catalog can discover and annotate these assets. Users can take ownership of unowned data assets and then limit the visibility of the assets they own.
+
+When a data asset in Azure Data Catalog is owned, only users who are authorized by the owners can discover the asset and view its metadata, and only the owners can delete the asset from the catalog.
 
 > [!NOTE]
-> Ownership in Data Catalog affects only the metadata that's stored in the catalog. Ownership does not confer any permissions on the underlying data source.
->
->
+> Ownership in Azure Data Catalog affects only the metadata that's stored in the catalog. Ownership does not confer any permissions on the underlying data source.
 
 ### Take ownership
+
 Users can take ownership of data assets by selecting the **Take Ownership** option in the Data Catalog portal. No special permissions are required to take ownership of an unowned data asset. Any user can take ownership of an unowned data asset.
 
 ### Add owners and co-owners
-If a data asset is already owned, other users cannot simply take ownership. They must be added as co-owners by an existing owner. Any owner can add additional users or security groups as co-owners.
+
+If a data asset is already owned, other users can’t take ownership. They must be added as co-owners by an existing owner. Any owner can add other users or security groups as co-owners.
 
 > [!NOTE]
 > It is a best practice to have at least two individuals as owners for any owned data asset.
->
->
 
 ### Remove owners
+
 Just as any asset owner can add co-owners, any asset owner can remove any co-owner.
 
-An asset owner who removes themself as an owner can no longer manage the asset. If the asset owner removes themself as an owner and there are no other co-owners, the asset reverts to an unowned state.
+An asset owner who removes themselves as an owner can no longer manage the asset. If the asset owner removes themselves as an owner and there are no other co-owners, the asset reverts to an unowned state.
 
 ## Control visibility
+
 Data-asset owners can control the visibility of the data assets they own. To restrict visibility as the default, where all Data Catalog users can discover and view the data asset, the asset owner can toggle the visibility setting from **Everyone** to **Owners & These Users** in the properties for the asset. Owners can then add specific users and security groups.
 
 > [!NOTE]
 > Whenever possible, asset ownership and visibility permissions should be assigned to security groups and not to individual users.
->
->
 
 ## Catalog administrators
-Data Catalog administrators are implicitly co-owners of all assets in the catalog. Asset owners cannot remove visibility from administrators, and administrators can manage ownership and visibility for all data assets in the catalog.
+
+Data Catalog administrators are implicitly co-owners of all assets in the catalog. Asset owners can’t remove visibility from administrators, and administrators can manage ownership and visibility for all data assets in the catalog.
 
 ## Summary
-The Data Catalog crowdsourcing model to metadata and data asset discovery allows all catalog users to contribute and discover. The Standard Edition of Data Catalog is designed for ownership and management to limit the visibility and use of specific data assets.
+
+The Data Catalog crowdsourcing model to metadata and data asset discovery allows all catalog users to contribute and discover information. The Standard Edition of Data Catalog is designed for ownership and management to limit the visibility and use of specific data assets.

articles/data-catalog/data-catalog-terminology.md

@@ -1,11 +1,11 @@
 ---
 title: Azure Data Catalog terminology
 description: This article provides an introduction to concepts and terms used in Azure Data Catalog documentation.
-author: JasonWHowell
-ms.author: jasonh
+author: ChandraKavya
+ms.author: kchandra
 ms.service: data-catalog
 ms.topic: conceptual
-ms.date: 08/01/2019
+ms.date: 02/15/2022
 ---
 # Azure Data Catalog terminology
 
@@ -15,31 +15,31 @@ This article provides an introduction to concepts and terms used in Azure Data C
 
 ## Catalog
 
-The Azure Data Catalog is a cloud-based metadata repository in which data sources and data assets can be registered. The catalog serves as a central storage location for structural metadata extracted from data sources and for descriptive metadata added by users.
+The Azure Data Catalog is a cloud-based metadata repository in which data sources and data assets can be registered. The **catalog** serves as a central storage location for structural metadata that was extracted from data sources and for descriptive metadata added by users.
 
 ## Data source
 
-A data source is a system or container that manages data assets. Examples include SQL Server databases, Oracle databases, SQL Server Analysis Services databases (tabular or multidimensional), and SQL Server Reporting Services servers.
+A **data source** is a system or container that manages data assets. Examples include SQL Server databases, Oracle databases, SQL Server Analysis Services databases (tabular or multidimensional), and SQL Server Reporting Services servers.
 
 ## Data asset
 
-Data assets are objects contained within data sources that can be registered with the catalog. Examples include SQL Server tables and views, Oracle tables and views, SQL Server Analysis Services measures, dimensions and KPIs, and SQL Server Reporting Services reports.
+**Data assets** are objects contained within data sources that can be registered with the catalog. Examples include SQL Server tables and views, Oracle tables and views, SQL Server Analysis Services measures, dimensions and KPIs, and SQL Server Reporting Services reports.
 
 ## Data asset location
 
-The catalog stores the location of a data source or data asset, which can be used to connect to the source using a client application. The format and details of the location vary based on the data source type. For example, a SQL Server table can be identified by its four part name – server name, database name, schema name, object name – while a SQL Server Reporting Services Report can be identified by its URL.
+The catalog stores the **location** of a data source or data asset, which can be used to connect to the source using a client application. The format and details of the location vary based on the data source type. For example, a SQL Server table can be identified by its four part name – server name, database name, schema name, object name – while a SQL Server Reporting Services Report can be identified by its URL.
 
 ## Structural metadata
 
-Structural metadata is the metadata extracted from a data source that describes the structure of a data asset. This includes the assets location, its object name and type, and additional type-specific characteristics. For example, the structural metadata for tables and views includes the names and data types for the object’s columns.
+**Structural metadata** is the metadata extracted from a data source that describes the structure of a data asset. Structural metadata includes the asset's location, its object name and type, and other type-specific characteristics. For example, the structural metadata for tables and views includes the names and data types for the object’s columns.
 
 ## Descriptive metadata
 
-Descriptive metadata is metadata that describes the purpose or intent of a data asset. Typically descriptive metadata is added by catalog users using the Azure Data Catalog portal, but it can also be extracted from the data source during registration. For example, the Azure Data Catalog registration tool will extract descriptions from the Description property in SQL Server Analysis Services and SQL Server Reporting Services, and from the [ms_description extended property](/previous-versions/sql/sql-server-2008-r2/ms190243(v=sql.105)) in SQL Server databases, if these properties have been populated with values.
+**Descriptive metadata** is metadata that describes the purpose or intent of a data asset. Usually, descriptive metadata is added by catalog users using the Azure Data Catalog portal, but it can also be extracted from the data source during registration. For example, the Azure Data Catalog registration tool will extract descriptions from the Description property in SQL Server Analysis Services and SQL Server Reporting Services, and from the [ms_description extended property](/previous-versions/sql/sql-server-2008-r2/ms190243(v=sql.105)) in SQL Server databases, if these properties have been populated with values.
 
 ## Request access
 
-A data asset's descriptive metadata can include information on how to request access to the data asset or data source. This information is presented with the data asset location, and can include one or more of the following options:
+A data asset's descriptive metadata can include information on how to **request access** to the data asset or data source. This information is presented with the data asset location, and can include one or more of the following options:
 
 * The email address of the user or team responsible for granting access to the data source.
 * The URL of the documented process that users must follow to gain access to the data source.
@@ -48,38 +48,37 @@ A data asset's descriptive metadata can include information on how to request ac
 
 ## Preview
 
-A preview in Azure Data Catalog is a snapshot of up to 20 records that can be extracted from the data source during registration, and stored in the catalog with the data asset metadata. The preview can help users who discover a data asset better understand its function and purpose. In other words, seeing sample data can be more valuable than seeing just the column names and data types.
+A **preview** in Azure Data Catalog is a snapshot of up to 20 records that can be extracted from the data source during registration, and stored in the catalog with the data asset metadata. The preview can help users who discover a data asset better understand its function and purpose. In other words, seeing sample data can be more valuable than seeing just the column names and data types.
 Previews are only supported for tables and views, and must be explicitly selected by the user during registration.
 
 ## Data Profile
 
-A data profile in Azure Data Catalog is a snapshot of table-level and column-level metadata about a registered data asset that can be extracted from the data source during registration, and stored in the catalog with the data asset metadata. The data profile can help users who discover a data asset better understand its function and purpose. Similar to previews, data profiles must be explicitly selected by the user during registration.
+A **data profile** in Azure Data Catalog is a snapshot of table-level and column-level metadata about a registered data asset. This information can be extracted from the data source during registration, and stored in the catalog with the data asset metadata. The data profile can help users who discover a data asset better understand its function and purpose. Similar to previews, data profiles must be explicitly selected by the user during registration.
 
 > [!NOTE]
 > Extracting a data profile can be a costly operation for large tables and views, and may significantly increase the time required to register a data source.
 
-
 ## User perspective
 
-In Azure Data Catalog, any user can provide descriptive metadata for a registered data asset. Every user has a distinct perspective on the data and its use. For example, the administrator responsible for a server may provide the details of its service level agreement (SLA) or backup windows; a data steward may provide links to documentation for the business processes the data supports; and an analyst may provide a description in the terms that are most relevant to other analysts, and which can be most valuable to those users who need to discover and understand the data.
+In Azure Data Catalog, **any user can provide descriptive metadata** for a registered data asset. Every user has a distinct perspective on the data and its use. For example, the administrator responsible for a server may provide the details of its service level agreement (SLA) or backup windows. A data steward may provide links to documentation for the business processes the data supports. An analyst may provide a description in the terms that are most relevant to other analysts, and which can be most valuable to those users who need to discover and understand the data.
 
 Each of these perspectives is inherently valuable, and with Azure Data Catalog each user can provide the information that is meaningful to them, while all users can use that information to understand the data and its purpose.
 
 ## Expert
 
-An expert is a user who has been identified as having an informed “expert” perspective for a data asset. Any user can add themselves or another user as an expert for an asset. Being listed as an expert does not convey any additional privileges in Azure Data Catalog; it allows users to easily locate those perspectives that are most likely to be useful when reviewing an asset’s descriptive metadata.
+An **expert** is a user who has been identified as having an informed “expert” perspective for a data asset. Any user can add themselves or another user as an expert for an asset. Being listed as an expert doesn't convey any other privileges in Azure Data Catalog; it allows users to easily locate those perspectives that are most likely to be useful when reviewing an asset’s descriptive metadata.
 
 ## Owner
 
-An owner is a user who has additional privileges for managing a data asset in Azure Data Catalog. Users can take ownership of registered data assets, and owners can add other users as co-owners. For more information, see [How to manage data assets](data-catalog-how-to-manage.md)  
+An **owner** is a user who has more privileges for managing a data asset in Azure Data Catalog. Users can take ownership of registered data assets, and owners can add other users as co-owners. For more information, see the [article on how to manage data assets](data-catalog-how-to-manage.md).  
 
 > [!NOTE]
 > Ownership and management are available only in the Standard Edition of Azure Data Catalog.
 
 ## Registration
 
-Registration is the act of extracting data asset metadata from a data source and copying it to the Azure Data Catalog service. Data assets that have been registered can then be annotated and discovered.
+**Registration** is the act of extracting data asset metadata from a data source and copying it to the Azure Data Catalog service. Data assets that have been registered can then be annotated and discovered.
 
 ## Next steps
 
-[Quickstart: Create an Azure Data Catalog](data-catalog-get-started.md)
+[Quickstart: Create an Azure Data Catalog](data-catalog-get-started.md)