+
+
+
+CluedIn offers three types of logs to assist in monitoring and troubleshooting your streams:
+
+- **Golden record stream logs** – view the streams that exported a specific golden record.
+
+- **Stream logs** – view golden records exported by a specific stream.
+
+- **Export target health checks** – view the health check status of the export target, updated every minute.
+
+**Golden record stream logs**
+
+Each golden record contains the **Streams** tab, where you can find the stream that exported the golden record and the date it was sent to the export target.
+
+
+
+This page lists active and paused streams that exported the golden record. However, if the stream is stopped, it is not displayed on the **Streams** tab because all of its logs are cleared. You can select the stream to view its details.
+
+**Stream logs**
+
+Each stream contains the **Stream Log** tab, where you’ll find all golden records that were exported by this stream. If the stream encounters an error while exporting golden records, it will be displayed on the page. This way, you can quickly identify and address any issues.
+
+
+
+You can filter the stream logs by two categories:
+
+- **Severity** – the level of importance or urgency of an event or issue. Learn about standard severity levels [here](https://learn.microsoft.com/en-us/dotnet/core/extensions/logging?tabs=command-line#log-level).
+
+- **Area** – the place in the streaming pipeline that produces logs:
+
+ - **Stream ingestion log** – logs coming from the stream.
+
+ - **Health check** – logs coming from the export target assigned to the stream. When the health check status of the export target changes, for example, from **Healthy** to **Unhealthy**, a new log is added to the page.
+
+ - **Export target** – other messages that the export target itself would like to log in the stream.
+
+This page displays logs only when the stream is active or paused. If you stop the stream, the logs are cleared.
+
+**Export target health checks**
+
+Each export target contains the **Health Checks** tab, where you can find the health check status of the export target.
+
+
+
+CluedIn runs health checks for the export target every 60 seconds. If the export target encounters any issues, its health status will be marked as **Unhealthy**. If the export target becomes **Unhealthy**, the stream associated with that export target is stopped and the corresponding log is added to the **Stream Log** page as well.
diff --git a/docs/160-release/002-release-2025-01.md b/docs/160-release/002-release-2025-01.md
new file mode 100644
index 00000000..7d7999d0
--- /dev/null
+++ b/docs/160-release/002-release-2025-01.md
@@ -0,0 +1,77 @@
+---
+layout: cluedin
+title: Release 2025.01
+parent: Release overview
+nav_order: 2
+permalink: /release-notes/2025-01
+---
+## On this page
+{: .no_toc .text-delta }
+- TOC
+{:toc}
+
+This article outlines new features and improvements in CluedIn 2025.01.
+
+
+
+
+
+The following sections contain brief description of new features and links to related articles.
+
+## New Ingestion dashboard
+
+The new Ingestion dashboard is designed to simplify your work with data sources and make data management more efficient and user-friendly. You’ll find a quick and simple way to start uploading your data into CluedIn from files, ingestion endpoints, databases, manual data entry projects, and crawlers. Additionally, you'll be able to quickly identify which data sets or manual data entry projects require attention, enabling you to prioritize and address issues efficiently. For more information, see [Ingestion](/integration).
+
+## Sources page update
+
+The Sources page (previously, Data Sources) now displays the number of sources per type and allows filtering the sources by type. Now, you can quickly find the needed source without expanding the group.
+
+## Monitoring page update
+
+The Monitoring page for data sets created from ingestion endpoints now displays the ingestion progress over time in the form of hourly and daily ingestion reports. Additionally, we’ve improved the endpoint index to help you track each payload by receipt ID. This way, you can review all records sent to CluedIn in a specific request. You can also view the golden records produced from each payload and delete those golden records if you no longer need them. We've also added a list of potential errors that can occur with the data set, along with remediation steps and the status for each error. For more information, see [Monitoring for ingestion endpoints](/integration/additional-operations-on-records/monitoring#monitoring-for-ingestion-endpoints).
+
+## Source record approval
+
+Source record approval is a mechanism that ensures only verified records are sent for processing. This is particularly useful for data sets created via an ingestion endpoint. After completing the initial full data load, you may want to ingest only delta records on a daily basis. The approval mechanism helps ensure that only verified delta records are processed. Data source owners can review these delta records and decide whether they should be processed. Source record approval can also be beneficial for manual data entry projects, as it grants project owners full control over the records created. Project owners can review new records added by non-owner users and decide whether they should be processed and turned into golden records. For more information, see [Approval](/integration/additional-operations-on-records/approval).
+
+## Data set validations
+
+Data set validations allow you to check source records for errors, inconsistencies, and missing values, and to correct invalid values. You can use auto-validation, where CluedIn analyzes the fields and suggest appropriate validation methods, or configure your own validation methods. By using data set validations, you can enhance the quality of source records and prevent incorrect records from becoming golden records. For more information, see [Validations](/integration/additional-operations-on-records/validations).
+
+## Power Fx formulas
+
+You can now use Power Fx formulas in rules to set up filters, conditions, and actions. With the help of Excel-like formulas, you can perform querying, equality testing, decision making, type conversion, and string manipulation based on the supported properties of a data part or a golden record. For more information, see [Power Fx formulas in rules](/management/rules/power-fx-formulas).
+
+## New access control actions
+
+Previously, you could only use the Allow Access action in the policy rule to give access to all or specific vocabulary keys in golden records. Now, you have more granular control over the types of access to golden records and their properties:
+
+- View – to allow view-only access to all or specific vocabulary keys in golden records.
+- Mask – to restrict access to sensitive data, allowing certain users or roles to know that the value exists but remains hidden.
+- Add/edit – to grant full control over specific properties in golden records, allowing certain users or roles to add new properties to the golden record or edit existing properties.
+
+For more information, see [Access control](/management/access-control).
+
+## Search experience update
+
+You can quickly find your recent searches, private saved searches, and shared saved searches by clicking anywhere in the search box. We’ve also improved the selection of business domains for search—now, you can view the number of golden records per business domain. Additionally, to simplify the process of adding columns to the search results page, we've updated the vocabulary key selector. Now, the vocabulary keys are grouped by vocabularies, allowing you to conveniently add all or specific vocabulary keys. For more information, see [Search](/key-terms-and-features/search).
+
+## Audit log actions update
+
+We’ve expanded the list of audit log actions to help you track changes to [clean projects](/preparation/clean/clean-reference#clean-project-audit-log-actions), [deduplication projects](/management/deduplication/deduplication-reference#deduplication-project-audit-log-actions), [users](/administration/user-management#user-management-reference), and [vocabularies](/management/data-catalog/vocabulary#ocabulary-overview). Additionally, the audit log now displays the activation and deactivation of enrichers, crawlers, and export targets, as well as the addition or removal of permissions for these items. This enhancement provides greater visibility and control, ensuring you can effectively audit and manage all activities.
+
+## Stream logs
+
+We have added stream logs to help you verify the successful export of your golden records and identify issues if something goes wrong. On the golden record page, you can now find a list of streams that exported the golden record, along with the date it was sent to the export target. Additionally, each stream now includes a stream log, where you’ll find all golden records exported by that stream. Stream logs can help you effectively monitor and troubleshoot your streams to ensure everything runs smoothly. For more information, see [Stream logs](/consume/streams/stream-logs).
+
+## Terminology changes
+
+To simplify CluedIn interface and make it more intuitive and better aligned with common industry concepts, we have changed some terms used in the platform. There are three major changes:
+
+- **Entity type** is now referred to as **Business domain**.
+
+- **Entity origin code** is now referred to as **Primary identifier**.
+
+- **Entity codes** are now referred to as **Identifiers**.
+
+The functionality behind the terms remains the same; only the terms have been changed. Learn more in [Terminology changes](/release-notes/terminology-changes).
diff --git a/docs/160-release/003-terminology-changes.md b/docs/160-release/003-terminology-changes.md
new file mode 100644
index 00000000..754e3e14
--- /dev/null
+++ b/docs/160-release/003-terminology-changes.md
@@ -0,0 +1,22 @@
+---
+layout: cluedin
+title: Terminology changes
+parent: Release overview
+nav_order: 3
+permalink: /release-notes/terminology-changes
+last_modified: 2025-04-02
+---
+
+In the [2025.01 release](/release-notes/2025-01) of CluedIn, we have updated some of the terminology used in the platform. The terminology changes simplify CluedIn interface, making it more intuitive and better aligned with common industry concepts.
+
+
+
+
+
+The terminology changes only affect the terms, the functionality behind the terms remains the same. The following table provides a summary of terminology changes in CluedIn.
+
+| Old term | New term | Definition |
+|--|--|--|
+| Entity type | Business domain | A well-known business object that provides context for golden records. In CluedIn, all golden records must have a business domain to ensure systematic organization of data management processes. Learn more in [Business domain](/key-terms-and-features/entity-type). |
+| Entity origin code | Primary identifier | A mechanism used in CluedIn to define the uniqueness of a golden record. It is configured during the mapping process. The primary identifier consists of a business domain, an origin, and a key that uniquely identifies the record. This combination allows you to achieve absolute uniqueness across all the data sources you interact with. Learn more in [Identifiers](/key-terms-and-features/entity-codes). |
+| Entity codes | Identifiers | Additional mechanism to define the uniqueness of a golden record. If a data set contains additional columns that can uniquely represent a record, these columns can also be used to generate identifiers. Learn more in [Identifiers](/key-terms-and-features/entity-codes). |
\ No newline at end of file
diff --git a/docs/180-microsoft-integration/010-powerapps.md b/docs/180-microsoft-integration/010-powerapps.md
index 7a43fb75..91dc0704 100644
--- a/docs/180-microsoft-integration/010-powerapps.md
+++ b/docs/180-microsoft-integration/010-powerapps.md
@@ -16,7 +16,7 @@ Power Apps can be integrated with CluedIn to enable you to **manage your master
Power Apps integration offers the following benefits:
-- 2-way synchronization of Dataverse metadata to CluedIn entity types and vocabularies and vice versa:
+- 2-way synchronization of Dataverse metadata to CluedIn business domains and vocabularies and vice versa:
- CluedIn stream to export golden records from CluedIn to the Dataverse tables.
diff --git a/docs/180-microsoft-integration/050-event-hub.md b/docs/180-microsoft-integration/050-event-hub.md
index 4022226b..3fa86a3e 100644
--- a/docs/180-microsoft-integration/050-event-hub.md
+++ b/docs/180-microsoft-integration/050-event-hub.md
@@ -10,7 +10,7 @@ Azure Event Hub integration enables the transmission of workflow events from Clu
- Adding a data source, updating a data source
-- Adding an entity type
+- Adding a business domain
- Adding a role
diff --git a/docs/180-microsoft-integration/090-excel-add-in.md b/docs/180-microsoft-integration/090-excel-add-in.md
index 041aa89a..fff20d3a 100644
--- a/docs/180-microsoft-integration/090-excel-add-in.md
+++ b/docs/180-microsoft-integration/090-excel-add-in.md
@@ -94,7 +94,7 @@ When the CluedIn Excel Add-in is added, a new group called **CluedIn** appears o
- **Show Taskpane** – opens the CluedIn Excel Add-in task pane to the right side of the window.
-- **Create Entity Type** – opens the entity type creation pane in CluedIn in your default browser. For more information, see [Create entity type](/management/entity-type#create-an-entity-type).
+- **Create Entity Type** – opens the business domain (previously entity type) creation pane in CluedIn in your default browser. For more information, see [Create business domain](/management/entity-type#create-a-business-domaine).
- **Merge Entity** – initiates the merging process by opening the merging page in CluedIn in your default browser.
@@ -116,9 +116,9 @@ Once you connect to an instance of CluedIn, you can start working with the data
### Load data from CluedIn to Excel
-1. Select the **Entity Type** of golden records that you want to load. The dropdown list contains the entity types that are currently used in CluedIn.
+1. In **Entity Type**, select the business domain (previously entity type) of golden records that you want to load. The dropdown list contains the business domains that are currently used in CluedIn.
-1. Specify the **Vocabulary Keys** of golden records that you want to load. To add all vocabulary keys associated with the selected entity type, use the **Auto-select** option.
+1. Specify the **Vocabulary Keys** of golden records that you want to load. To add all vocabulary keys associated with the selected business domain, use the **Auto-select** option.
@@ -148,7 +148,7 @@ Once you connect to an instance of CluedIn, you can start working with the data
When the data is loaded, it becomes available in the spreadsheet, and you can start [modifying](#modify-loaded-data-in-excel) it as needed. By default, the rows are presented in alternating light blue and white colors.
- Note that the sheet name corresponds to the entity type of loaded golden records. If you want to load the data of another entity type, just add a new sheet, edit the configuration on the **Load Data** tab, and load the data. and You can have as many sheets as you like.
+ Note that the sheet name corresponds to the business domain of loaded golden records. If you want to load the data of another business domain, just add a new sheet, edit the configuration on the **Load Data** tab, and load the data. and You can have as many sheets as you like.
diff --git a/docs/180-microsoft-integration/copilot/020-work-with-copilot.md b/docs/180-microsoft-integration/copilot/020-work-with-copilot.md
index 7aabdfc5..78c2afd5 100644
--- a/docs/180-microsoft-integration/copilot/020-work-with-copilot.md
+++ b/docs/180-microsoft-integration/copilot/020-work-with-copilot.md
@@ -71,7 +71,7 @@ CluedIn Copilot can analyze a data set to provide general overview, suggest poss
|--|--|--|
| DescribeDataSet | Provides general information about a data set: column description, possible validation checks, data quality issues, and so on.If you are on the data set page, you can just tell the Copilot to describe _this_ data set. Otherwise, you can refer to the data set by its ID, which you can find in the URL of the page. | Tell me a bit about this data set.
Describe this data set.
Describe the data set with ID 443259BB-1D17-4078-A069-7ECAD418BA19. | | SuggestDatasetMapping | Provides suggestions on how to map a data set to an existing entity type and vocabulary. The suggested mapping can be used to define how the data set columns should be transformed and linked to the specified vocabulary.
If you are on the data set page, you can just tell the Copilot to suggest mapping for _this_ data set. Otherwise, you can refer to the data set by its ID, which you can find in the URL of the page. | Can you suggest a mapping from this data set to the Employee vocabulary?
Can you suggest how to map this data set to the Company vocabulary? | -| CreateDatasetMapping | Create a mapping from a data set to an existing entity type and vocabulary. Note that you'll need to set up the entity origin code to complete the mapping.
If you are on the data set page, you can just tell the Copilot to create mapping for _this_ data set. Otherwise, you can refer to the data set by its ID, which you can find in the URL of the page. | Can you create a mapping from this data set to the Employee vocabulary? | +| CreateDatasetMapping | Create a mapping from a data set to an existing business domain and vocabulary. Note that you'll need to set up the primary identifier to complete the mapping.
If you are on the data set page, you can just tell the Copilot to create mapping for _this_ data set. Otherwise, you can refer to the data set by its ID, which you can find in the URL of the page. | Can you create a mapping from this data set to the Employee vocabulary? | | ListDataSets | Provides a list of all available data sets. Note that it is not possible to list data sets by creation date or other properties, you can only get a list of all data sets. | Can you list all data sets? | | EntitySearchByDataSetColumnSample| Allows you to check if the values you have chosen as an entity code can already be found in the system. This can be helpful when you want to ensure that the chosen entity codes are unique and do not already exist in the system. | Can you check if values in the customerId column already have values in the system? | @@ -100,7 +100,7 @@ CluedIn Copilot can create vocabularies and vocabulary keys as well detect anoma | Copilot function | Description | Prompt example | |--|--|--| -| CreateVocabulary | Creates a new vocabulary with the specified name. Once a new vocabulary is created, you'll get a link to view and manage the vocabulary details.
If you are on the page of the entity type you want to associate the vocabulary with, you can just tell the Copilot to create the vocabulary for _this_ entity type. If you don't specify the entity type, it will be provided automatically, but you can change it later. | Can you create a new vocabulary called Company for the Company entity type?
Can you create a new vocabulary called Company for this entity type? | +| CreateVocabulary | Creates a new vocabulary with the specified name. Once a new vocabulary is created, you'll get a link to view and manage the vocabulary details.
If you are on the page of the business domain you want to associate the vocabulary with, you can just tell the Copilot to create the vocabulary for _this_ business domain. If you don't specify the business domain, it will be provided automatically, but you can change it later. | Can you create a new vocabulary called Company for the Company business domain?
Can you create a new vocabulary called Company for this business domain? | | CreateVocabularyKey | Creates a new vocabulary key with the specified name. If you previously created a vocabulary in the chat, the new vocabulary keys will be added to that vocabulary.
You can create individual vocabulary keys one at a time by entering a separate prompt for each vocabulary key. However, if you need to create multiple vocabulary keys, you can instruct Copilot to perform the task in a single prompt. | Can you create 10 vocabulary keys including Name, Age, Gender, JobTitle, ContactNumber, Email, ManagedBy, Salary, Tenure and NickName? | | ProfileVocabularyKey | Creates profiling for a vocabulary key. | Can you profile this vocabulary key? | | StandardizeData | Provides suggestions on how to standardize or normalize values within a vocabulary key. You can review the suggestions and then instruct Copilot to create rules or do it on your own. | Can you standardize values of this vocabulary key? | @@ -140,7 +140,7 @@ CluedIn Copilot can create clean projects according to your requirements and dis | Copilot function | Description | Prompt example | |--|--|--| -| CreateCleanProject | Creates a clean project. You'll get a brief project description, including top 10 records that match the project's filters. You can click the link to go to the clean project and validate if Copilot did the right thing. Then you'll be able to generate the project results on your own. | Can you create a clean project to fix contact.jobTitle values in records of the Contact entity type? | +| CreateCleanProject | Creates a clean project. You'll get a brief project description, including top 10 records that match the project's filters. You can click the link to go to the clean project and validate if Copilot did the right thing. Then you'll be able to generate the project results on your own. | Can you create a clean project to fix contact.jobTitle values in records of the Contact business domain? | | ListCleaningProjects | Provides a list of all available clean projects, including project ID and project name. | Can you list all clean projects?
What clean project are currently available in the platform? | ### Hierarchy skills @@ -149,7 +149,7 @@ CluedIn Copilot can create hierarchies to visualize relations between golden rec | Copilot function | Description | Prompt example | |--|--|--| -| CreateHierarchy | Creates a new hierarchy. Before creating the hierarchy, make sure that the records have the appropriate edge type defined. Once the hierarchy is created, you'll get a link to view the details. | Can you create a hierarchy called Org Chart for all records of the Contact entity type? | +| CreateHierarchy | Creates a new hierarchy. Before creating the hierarchy, make sure that the records have the appropriate edge type defined. Once the hierarchy is created, you'll get a link to view the details. | Can you create a hierarchy called Org Chart for all records of the Contact business domain? | | ListHierarchies | Provides a list of all available hierarchies, including status, number of nodes, creation and modification dates. | Can you list all hierarchies that are available in the system? | ### Glossary skills @@ -163,7 +163,7 @@ CluedIn Copilot can create glossary terms within specific category and display i ### Other skills -CluedIn Copilot can search for golden records according to your requirements as well as perform actions related to entity types (create, describe, list). +CluedIn Copilot can search for golden records according to your requirements as well as perform actions related to business domains (create, describe, list).  @@ -171,6 +171,6 @@ CluedIn Copilot can search for golden records according to your requirements as |--|--|--| | DataQualityMetrics | Provides current global data quality metrics. | Can you show me the global quality metrics? | | Search | Finds records according to your input.
CluedIn will return the top 10 results in a table and a link to launch into the full search query as well. | Can you find the Person records where the user.country is in the Nordics? | -| ListEntityTypes | Provides a list of all available entity types. Note that entity types that have no associated data will not appear in the list. | Can you list all entity types? | -| CreateEntityType| Creates a new entity type with the specified name. Once a new entity type is created, you'll get a link to view details. | Can you create a new entity type named Company? | -| DescribeEntity | Provides general information about a golden record: entity type, name, codes, properties, vocabularies, and so on.
If you are on the golden record page, you can just tell the Copilot to describe _this_ golden record. | Can you describe this golden record? | +| ListEntityTypes | Provides a list of all available business domains. Note that business domains that have no associated data will not appear in the list. | Can you list all entity types? | +| CreateEntityType| Creates a new business domain with the specified name. Once a new business domaine is created, you'll get a link to view details. | Can you create a new entity type named Company? | +| DescribeEntity | Provides general information about a golden record: business domain, name, codes, properties, vocabularies, and so on.
If you are on the golden record page, you can just tell the Copilot to describe _this_ golden record. | Can you describe this golden record? | diff --git a/docs/180-microsoft-integration/fabric/020-connect-fabric-to-cluedin.md b/docs/180-microsoft-integration/fabric/020-connect-fabric-to-cluedin.md index 619cb65a..97db6b98 100644 --- a/docs/180-microsoft-integration/fabric/020-connect-fabric-to-cluedin.md +++ b/docs/180-microsoft-integration/fabric/020-connect-fabric-to-cluedin.md @@ -159,7 +159,7 @@ After you set up Microsoft Fabric, send the data to CluedIn. This process involv 1. In CluedIn, create auto-mapping for the data set following the instructions [here](/integration/create-mapping). -1. In CluedIn, edit the mapping for the data set to select the property used as the entity name and the property used for the entity origin code. For more information about mapping details, see [Review mapping](/integration/review-mapping). +1. In CluedIn, edit the mapping for the data set to select the property used as the entity name and the property used for the primary identifier. For more information about mapping details, see [Review mapping](/integration/review-mapping). 1. In CluedIn, got to the **Process** tab of the data set, turn on the **Auto submission** toggle, and then select **Switch to Bridge Mode**. diff --git a/docs/180-microsoft-integration/power-automate/020-power-automate-configuration-guide.md b/docs/180-microsoft-integration/power-automate/020-power-automate-configuration-guide.md index ff0ea66d..451abba1 100644 --- a/docs/180-microsoft-integration/power-automate/020-power-automate-configuration-guide.md +++ b/docs/180-microsoft-integration/power-automate/020-power-automate-configuration-guide.md @@ -45,7 +45,7 @@ Make sure that you have completed all of the actions described in [Power Automa - **Enterprise Flow Cache Duration** – a time period for which data is stored in the cache for enterprise flows. This duration can impact the performance and efficiency of your workflows. In the context of Power Automate, the cache duration helps manage the flow’s performance by temporarily storing data to reduce the need for repeated data retrievals. - - **Entity Type Cache Duration** – a time period for which the records that belong to the entity types with the **Batch approval workflow** option enabled are stored in the cache. + - **Business Domain Cache Duration** – a time period for which the records that belong to the business domains with the **Batch approval workflow** option enabled are stored in the cache.  diff --git a/docs/180-microsoft-integration/powerapps/020-features/010-sync-entitytypes-to-dataverse.md b/docs/180-microsoft-integration/powerapps/020-features/010-sync-entitytypes-to-dataverse.md index 54f538c4..7ad1dd5c 100644 --- a/docs/180-microsoft-integration/powerapps/020-features/010-sync-entitytypes-to-dataverse.md +++ b/docs/180-microsoft-integration/powerapps/020-features/010-sync-entitytypes-to-dataverse.md @@ -4,22 +4,22 @@ nav_order: 10 parent: Features grand_parent: Power Apps Integration permalink: /microsoft-integration/powerapps/features/sync-entitytypes -title: Sync entity types to Dataverse tables +title: Sync business domains to Dataverse tables tags: ["integration", "microsoft", "powerapps", "dataverse"] last_modified: 2023-05-17 --- -This feature allows you to sync CluedIn entity types, vocabularies, and vocabulary keys with Dataverse table and columns. +This feature allows you to sync CluedIn business domains, vocabularies, and vocabulary keys with Dataverse table and columns. -**To sync CluedIn entity types with Dataverse table** +**To sync CluedIn business domains with Dataverse table** 1. On the navigation pane, go to **Administration** > **Settings**, and then find the **PowerApps** section. -1. In **Sync CluedIn Entity Types to Dataverse Table**, turn on the toggle, and then enter the entity type that you want to sync. If you want to sync multiple entity types, separate them with a comma (for example, _/_Type1,/Type2,/Type3_). +1. In **Sync CluedIn Business Domains to Dataverse Table**, turn on the toggle, and then enter the business domain that you want to sync. If you want to sync multiple business domains, separate them with a comma (for example, _/_Type1,/Type2,/Type3_).  - Another way to enable this feature is to navigate to **Management** > **Entity Types** and select the entity type you want to sync. Then, select **Edit** and turn on the toggle for **Sync CluedIn Entity Types to Dataverse Table**. Finally, save changes. + Another way to enable this feature is to navigate to **Management** > **Business Domains** and select the business domain you want to sync. Then, select **Edit** and turn on the toggle for **Sync CluedIn Business Domains to Dataverse Table**. Finally, save changes.  diff --git a/docs/180-microsoft-integration/powerapps/020-features/020-sync-dataverse-to-cluedin.md b/docs/180-microsoft-integration/powerapps/020-features/020-sync-dataverse-to-cluedin.md index 559f3158..f0ee5c13 100644 --- a/docs/180-microsoft-integration/powerapps/020-features/020-sync-dataverse-to-cluedin.md +++ b/docs/180-microsoft-integration/powerapps/020-features/020-sync-dataverse-to-cluedin.md @@ -4,12 +4,12 @@ nav_order: 20 parent: Features grand_parent: Power Apps Integration permalink: /microsoft-integration/powerapps/features/sync-dataverse -title: Sync Dataverse table to Cluedin entity types/vocabularies +title: Sync Dataverse table to Cluedin business domains/vocabularies tags: ["integration", "microsoft", "powerapps", "dataverse"] last_modified: 2023-05-17 --- -This feature allows you to sync Dataverse table and columns into CluedIn entity type, vocabulary, and vocabulary keys. +This feature allows you to sync Dataverse table and columns into CluedIn business domains, vocabulary, and vocabulary keys. **Prerequisites** @@ -23,18 +23,18 @@ You'll need to provide the logical name of the Dataverse table. There are the fo  -**To sync Dataverse table and columns into CluedIn entity types and vocabulary** +**To sync Dataverse table and columns into CluedIn business domains and vocabulary** 1. On the navigation pane, go to **Administration** > **Settings**, and then find the **PowerApps** section. -1. In **Sync Dataverse Table/Columns to CluedIn Entity Types and Vocabulary**, turn on the toggle, and then enter the Dataverse table name. The value should be the **logical name** of the table. If you want to sync multiple tables, separate them with a comma (for example, _logical_name1_,logical_name2,logical_name3_). +1. In **Sync Dataverse Table/Columns to CluedIn Business Domains and Vocabulary**, turn on the toggle, and then enter the Dataverse table name. The value should be the **logical name** of the table. If you want to sync multiple tables, separate them with a comma (for example, _logical_name1_,logical_name2,logical_name3_). -  +  Once the synchronization has been successfully completed, you'll receive three notifications: **Entity Type Created**, **Vocabulary Created**, and **Vocabulary Keys Created**.  -1. Verify the entity type, vocabulary, and vocabulary keys created in CluedIn. +1. Verify the business domain, vocabulary, and vocabulary keys created in CluedIn.  \ No newline at end of file diff --git a/docs/180-microsoft-integration/powerapps/020-features/030-create-ingestion-endpoint-workflow.md b/docs/180-microsoft-integration/powerapps/020-features/030-create-ingestion-endpoint-workflow.md index ba0cfe12..87a7a1fb 100644 --- a/docs/180-microsoft-integration/powerapps/020-features/030-create-ingestion-endpoint-workflow.md +++ b/docs/180-microsoft-integration/powerapps/020-features/030-create-ingestion-endpoint-workflow.md @@ -31,7 +31,7 @@ As part of workflow automation, the ingestion endpoint will be created as well. **Workflow** -The creation of workflow will depend on the values of **Sync Entity Types** and **Sync Dataverse Tables**. Once the execution of the job is done, from the sample values above, you can expect two workflows to be created, one for each of the **cluedin_dog** and **crc12_customer** tables. +The creation of workflow will depend on the values of **Sync Business Domains** and **Sync Dataverse Tables**. Once the execution of the job is done, from the sample values above, you can expect two workflows to be created, one for each of the **cluedin_dog** and **crc12_customer** tables.  @@ -49,7 +49,7 @@ As we already know the structure of the table/vocabulary that we are working on,  -On the **Map** tab, you can find the the full view of all columns mapped to our vocabulary, including edges (relationships) and origin entity code (keys), if there are any. +On the **Map** tab, you can find the the full view of all columns mapped to our vocabulary, including edges (relationships) and identifiers, if there are any.  diff --git a/docs/180-microsoft-integration/powerapps/020-features/040-create-batch-approval-worrkflow.md b/docs/180-microsoft-integration/powerapps/020-features/040-create-batch-approval-worrkflow.md index 5955fea4..18a5815c 100644 --- a/docs/180-microsoft-integration/powerapps/020-features/040-create-batch-approval-worrkflow.md +++ b/docs/180-microsoft-integration/powerapps/020-features/040-create-batch-approval-worrkflow.md @@ -9,7 +9,7 @@ tags: ["integration", "microsoft", "powerautomate", "approval", "workflow"] last_modified: 2023-05-17 --- -This feature enables you to automate the creation of the workflow for the batch approval process. If you process the data (regardless of the source) and the system identifies that the entity type used has been tagged for the approval process, the data will be halted, and the approval process will start and wait for the user's approval to continue the data processing. +This feature enables you to automate the creation of the workflow for the batch approval process. If you process the data (regardless of the source) and the system identifies that the business domain used has been tagged for the approval process, the data will be halted, and the approval process will start and wait for the user's approval to continue the data processing. **Prerequisites** @@ -20,7 +20,7 @@ For more information, refer to this [link](/microsoft-integration/powerapps/setu **To enable the batch approval workflow** -1. In CluedIn, on the navigation pane, go to **Management** > **Entity Types**, and then select the entity type that you want to sync. +1. In CluedIn, on the navigation pane, go to **Management** > **Business Domains**, and then select the business domain that you want to sync. 1. Select **Edit** and then turn on the toggle for **Enable for Batch Approval Workflow**. diff --git a/docs/180-microsoft-integration/powerapps/020-features/050-create-streams.md b/docs/180-microsoft-integration/powerapps/020-features/050-create-streams.md index 6475fe9b..a298e1a0 100644 --- a/docs/180-microsoft-integration/powerapps/020-features/050-create-streams.md +++ b/docs/180-microsoft-integration/powerapps/020-features/050-create-streams.md @@ -27,13 +27,13 @@ Export target will be created automatically using the same credentials from Orga **Streams** -The creation of a stream will depend on the values of **Sync Entity Types** and **Sync Dataverse Tables**. +The creation of a stream will depend on the values of **Sync Business Domains** and **Sync Dataverse Tables**. Once the execution of the job is done, from the sample values above, two streams should have been created, one for each of the **cluedin_dog** and **crc12_customer** tables.  -Each stream will have a certain configuration filtered by entity type. +Each stream will have a certain configuration filtered by business domain.  diff --git a/docs/180-microsoft-integration/powerapps/020-power-apps-configuration-guide.md b/docs/180-microsoft-integration/powerapps/020-power-apps-configuration-guide.md index 1c27e388..da21a09c 100644 --- a/docs/180-microsoft-integration/powerapps/020-power-apps-configuration-guide.md +++ b/docs/180-microsoft-integration/powerapps/020-power-apps-configuration-guide.md @@ -49,27 +49,27 @@ Power Apps integration offers a variety of features for syncing data between Clu **To configure specific features of Power Apps integration** -1. If you want to sync multiple CluedIn entity types to Dataverse tables, specify the **Parallel Execution Count**. This is the number of entity types that can be simultaneously synced with Dataverse. Be default, this number is 5. +1. If you want to sync multiple CluedIn business domains to Dataverse tables, specify the **Parallel Execution Count**. This is the number of business domains that can be simultaneously synced with Dataverse. Be default, this number is 5. -1. If you want to sync CluedIn entity types to Dataverse tables: +1. If you want to sync CluedIn business domains to Dataverse tables: - 1. Turn on the toggle next to **Sync CluedIn Entity Types Dataverse Table**. + 1. Turn on the toggle next to **Sync CluedIn Business Domains to Dataverse Table**. - 1. Enter the entity types that you want to sync. If you want to sync multiple entity types, separate them with a comma (for example, _/Type1,/Type2,/Type3_). + 1. Enter the business domains that you want to sync. If you want to sync multiple business domains, separate them with a comma (for example, _/Type1,/Type2,/Type3_).  - Each entity type will be synced into a separate Dataverse table. For more information, see [Sync entity types to Dataverse tables](/microsoft-integration/powerapps/features/sync-entitytypes). + Each business domain will be synced into a separate Dataverse table. For more information, see [Sync business domains to Dataverse tables](/microsoft-integration/powerapps/features/sync-entitytypes). -1. If you want to sync Dataverse tables and columns to CluedIn entity types and vocabulary keys: +1. If you want to sync Dataverse tables and columns to CluedIn business domains and vocabulary keys: - 1. Turn on the toggle next to **Sync Dataverse Table/Columns to CluedIn Entity Types and Vocabulary**. + 1. Turn on the toggle next to **Sync Dataverse Table/Columns to CluedIn Business Domains and Vocabulary**. 1. Enter the name of the Dataverse table that you want to sync. This should be the logical name of the Dataverse table. If you want to sync multiple tables, separate them with a comma (for example, _logical_name1,logical_name2,logical_name3_).  - Each table will be synced into a separate CluedIn entity type and vocabulary associated with that entity type. The columns from the table will be synced into the vocabulary keys of the vocabulary associated with the entity type. For more information, see [Sync Dataverse tables to CluedIn entity types and vocabularies](/microsoft-integration/powerapps/features/sync-dataverse). + Each table will be synced into a separate CluedIn business domain and vocabulary associated with that business domain. The columns from the table will be synced into the vocabulary keys of the vocabulary associated with the business domain. For more information, see [Sync Dataverse tables to CluedIn business domains and vocabularies](/microsoft-integration/powerapps/features/sync-dataverse). 1. If you want to automate the ingestion of data from Dataverse to CluedIn: @@ -87,7 +87,7 @@ Power Apps integration offers a variety of features for syncing data between Clu 1. Make sure you have the [Dataverse export target](/consume/export-targets/dataverse-connector) installed in your CluedIn instance. It should be available in the list of export targets (**Consume** > **Export Targets** > **Add Export Target**). You do not need to configure the Dataverse export target because it will be configured automatically. - 1. Make sure you have enabled **Sync CluedIn Entity Types to Dataverse Table** for entity types of golden records that you want to export to a Dataverse table. + 1. Make sure you have enabled **Sync CluedIn Business Domains to Dataverse Table** for business domains of golden records that you want to export to a Dataverse table. 1. Turn on the toggle next to **Create CluedIn Stream**. diff --git a/docs/180-microsoft-integration/powerapps/040-external-features.md b/docs/180-microsoft-integration/powerapps/040-external-features.md index e8463f7c..39f43aa7 100644 --- a/docs/180-microsoft-integration/powerapps/040-external-features.md +++ b/docs/180-microsoft-integration/powerapps/040-external-features.md @@ -13,7 +13,7 @@ last_modified: 2023-05-17 1. TOC {:toc} -This will enable the user to see the Power Apps and Power Automate features as an iFrame in CluedIn UI. The feature below will only appear on the entity type's main page if that entity type is part of the synchronization. +This will enable the user to see the Power Apps and Power Automate features as an iFrame in CluedIn UI. The feature below will only appear on the business domain's main page if that business domain is part of the synchronization. ### Dataverse data diff --git a/docs/180-microsoft-integration/powerapps/images/sync-cluedin-entitytypes-setting.png b/docs/180-microsoft-integration/powerapps/images/sync-cluedin-entitytypes-setting.png index b864b081..779197e1 100644 Binary files a/docs/180-microsoft-integration/powerapps/images/sync-cluedin-entitytypes-setting.png and b/docs/180-microsoft-integration/powerapps/images/sync-cluedin-entitytypes-setting.png differ diff --git a/docs/200-kb/how-to/010-fix-address-data.md b/docs/200-kb/how-to/010-fix-address-data.md index 6627c88c..27864f3c 100644 --- a/docs/200-kb/how-to/010-fix-address-data.md +++ b/docs/200-kb/how-to/010-fix-address-data.md @@ -45,11 +45,11 @@ Let's consider an example of a CluedIn golden record that contains the address p  -To configure the Libpostal enricher, specify the entity type of golden records that you want to enrich and the vocabulary key that contains the initial address. +To configure the Libpostal enricher, specify the business domain of golden records that you want to enrich and the vocabulary key that contains the initial address.  -When the enricher is configured, [trigger](/preparation/enricher/add-enricher#trigger-enrichment) the enrichment for golden records. You can trigger the enrichment for all golden records of the specific entity type using the [GraphQL tool](/consume/graphql/graphql-actions). Alternatively, you can trigger the enrichment manually for each golden record. To do this, on the golden record page, select **More** > **Trigger external enrichment**. +When the enricher is configured, [trigger](/preparation/enricher/add-enricher#trigger-enrichment) the enrichment for golden records. You can trigger the enrichment for all golden records of the specific business domain using the [GraphQL tool](/consume/graphql/graphql-actions). Alternatively, you can trigger the enrichment manually for each golden record. To do this, on the golden record page, select **More** > **Trigger external enrichment**.  @@ -84,7 +84,7 @@ To configure the Google Maps enricher, specify the following details: - **API Key** for retrieving information from the Google Maps Platform. -- **Accepted Entity Type** to define which golden records will be enriched. +- **Accepted Business Domain** (previously entity type) to define which golden records will be enriched. - **Vocabulary Key used to control whether it should be enriched** to indicate if the golden record should be enriched. If the value of the vocabulary key is _true_, then the golden record will be enriched. Otherwise, the golden record will not be enriched. @@ -94,7 +94,7 @@ To configure the Google Maps enricher, specify the following details:  -When the enricher is configured, [trigger](/preparation/enricher/add-enricher#trigger-enrichment) the enrichment for golden records. You can trigger the enrichment for all golden records of the specific entity type using the [GraphQL tool](/consume/graphql/graphql-actions), or you can trigger the enrichment manually for each golden record. Alternatively, you can trigger the enrichment manually for each golden record. To do this, on the golden record page, select **More** > **Trigger external enrichment**. +When the enricher is configured, [trigger](/preparation/enricher/add-enricher#trigger-enrichment) the enrichment for golden records. You can trigger the enrichment for all golden records of the specific business domain using the [GraphQL tool](/consume/graphql/graphql-actions), or you can trigger the enrichment manually for each golden record. Alternatively, you can trigger the enrichment manually for each golden record. To do this, on the golden record page, select **More** > **Trigger external enrichment**. As a result, the CluedIn golden record now contains a variety of company details from Google Maps, such as administrative area level 1 and 2, business status, country code, and more. diff --git a/docs/200-kb/kb0010-faq.md b/docs/200-kb/kb0010-faq.md index 48e3c134..cd6503a8 100644 --- a/docs/200-kb/kb0010-faq.md +++ b/docs/200-kb/kb0010-faq.md @@ -70,7 +70,7 @@ The good news is that the native CluedIn administration screen is built on top o ## I have made a change in CluedIn that requires me to re-process all the data. What do I do? -It will happen many times with your CluedIn account! It is highly typical and expected. CluedIn has been designed with the idea in mind that we will re-process the data all the time. Once you have made your change, you have quite a lot of control over the level of re-processing. You can re-process at a source level, globally, record level, or even something a little more custom, e.g., entity type level. +It will happen many times with your CluedIn account! It is highly typical and expected. CluedIn has been designed with the idea in mind that we will re-process the data all the time. Once you have made your change, you have quite a lot of control over the level of re-processing. You can re-process at a source level, globally, record level, or even something a little more custom, e.g., business domain level. ## Does CluedIn index everything? diff --git a/docs/210-playbooks/008-data-export-playbook.md b/docs/210-playbooks/008-data-export-playbook.md index 82ed13f0..da19a671 100644 --- a/docs/210-playbooks/008-data-export-playbook.md +++ b/docs/210-playbooks/008-data-export-playbook.md @@ -28,7 +28,7 @@ title: Data export playbook Now that you have completed the [data transformation](/playbooks/data-transformation-playbook) process and reached the desired quality of your [golden records](/key-terms-and-features/golden-records), it is time to **push golden records to the target systems** in your organization. {:.important} -To establish correlations between exported golden records in your target systems, use the [entity origin code (primary identifier)](/key-terms-and-features/entity-codes#entity-origin-code-primary-identifier) and [codes (identifiers)](/key-terms-and-features/entity-codes#entity-codes-identifiers) instead of the entity ID. This is because the entity ID does not guarantee uniqueness, as records with different IDs could be merged. +To establish correlations between exported golden records in your target systems, use the [primary identifier](/key-terms-and-features/entity-codes#primary-identifier) and [additional identifiers](/key-terms-and-features/entity-codes#identifiers) instead of the entity ID. This is because the entity ID does not guarantee uniqueness, as records with different IDs could be merged. ## Data export models diff --git a/docs/210-playbooks/data-engineering/002-extending-cluedin-with-ms-integrations.md b/docs/210-playbooks/data-engineering/002-extending-cluedin-with-ms-integrations.md index 5845bd19..b7d2f22f 100644 --- a/docs/210-playbooks/data-engineering/002-extending-cluedin-with-ms-integrations.md +++ b/docs/210-playbooks/data-engineering/002-extending-cluedin-with-ms-integrations.md @@ -59,7 +59,7 @@ If you use Fabric, Databricks, Snowflake, Synapse, or any other Python-based dat ## Event Hubs integration -[Azure Event Hubs](https://learn.microsoft.com/en-us/azure/event-hubs/) is a native data-streaming service in the cloud that can stream millions of events per second, with low latency, from any source to any destination. By integrating Azure Event Hubs and CluedIn, you can enable the transmission of important events from CluedIn to your event hub. For example, adding or updating a data source, adding an entity type, creating a deduplication project, and more. You can then connect your event hub to Fabric and **build reports or alerts for different events**. This way you can get valuable insights about the activities in CluedIn, such as the number of deduplication or clean projects that were created last week. For more information, see [Event Hub integration](/microsoft-integration/event-hub-integration). +[Azure Event Hubs](https://learn.microsoft.com/en-us/azure/event-hubs/) is a native data-streaming service in the cloud that can stream millions of events per second, with low latency, from any source to any destination. By integrating Azure Event Hubs and CluedIn, you can enable the transmission of important events from CluedIn to your event hub. For example, adding or updating a data source, adding a business domain, creating a deduplication project, and more. You can then connect your event hub to Fabric and **build reports or alerts for different events**. This way you can get valuable insights about the activities in CluedIn, such as the number of deduplication or clean projects that were created last week. For more information, see [Event Hub integration](/microsoft-integration/event-hub-integration). In addition to this, CluedIn offers the [Azure Event Hub connector](/consume/export-targets/azure-event-hub-connector). You can configure it and use it in a stream to **export golden records** to a specific event hub. diff --git a/docs/210-playbooks/data-engineering/020-search.md b/docs/210-playbooks/data-engineering/020-search.md index 2234aa56..c86d1059 100644 --- a/docs/210-playbooks/data-engineering/020-search.md +++ b/docs/210-playbooks/data-engineering/020-search.md @@ -45,7 +45,7 @@ To find them, I can run a query like this: ``` The query will return me the top 20 of the `/Duck` entities. -The `query` parameter tells the API to filter the response by a given Entity Type. +The `query` parameter tells the API to filter the response by a given business domain (previously entity type). You can also specify the entity properties you want to get in the payload: `id`, `name`, and `entityType`. ### GraphQL search query with variables and cursor diff --git a/docs/210-playbooks/data-engineering/040-ingestion.md b/docs/210-playbooks/data-engineering/040-ingestion.md index 0dc94dd8..f8bd431e 100644 --- a/docs/210-playbooks/data-engineering/040-ingestion.md +++ b/docs/210-playbooks/data-engineering/040-ingestion.md @@ -28,7 +28,7 @@ We want to load this data to CluedIn. To do that, we need to create an API token
-Next, create an endpoint in CluedIn. From CluedIn's main page, click "Import From Ingestion Endpoint" and create a new endpoint. You will need to enter the endpoint's name, group name, and select entity type:
+Next, create an endpoint in CluedIn. From CluedIn's main page, click "Import From Ingestion Endpoint" and create a new endpoint. You will need to enter the endpoint's name, group name, and select business domain (previouisly entity type):
@@ -163,7 +163,7 @@ Then, in the Map tab, we create an automatic mapping:
1. Click "Add Mapping".
2. Select "Auto Mapping" and "Next".
-3. Ensure the entity type is selected or type a new entity type name and click "Create".
+3. Ensure the business domain (previously entity type) is selected or type a new business domain name and click "Create".
4. Type the new vocabulary name, like `imdb.title` and click "Create".
5. Click "Create Mapping".
diff --git a/docs/210-playbooks/data-ingestion/004-concept-of-mapping.md b/docs/210-playbooks/data-ingestion/004-concept-of-mapping.md
index 9b6e4e76..d1482e89 100644
--- a/docs/210-playbooks/data-ingestion/004-concept-of-mapping.md
+++ b/docs/210-playbooks/data-ingestion/004-concept-of-mapping.md
@@ -39,10 +39,10 @@ The mapping uses multiple CluedIn terms that you will need to learn. While it ma
| Name | Purpose | Link to documentation |
|--|--|--|
-| Entity type | The entity type represents a specific business domain of your data. Read the documentation to understand how to choose a good entity type. | [Link](/key-terms-and-features/entity-type) |
+| Business domain | The business domain represents a specific business object that describes the semantic meaning of your data. Read the documentation to understand how to choose a good business domain. | [Link](/key-terms-and-features/entity-type) |
| Vocabulary and vocabulary keys | The vocabulary is used to define the semantic layer (metadata) for your data. The vocabulary contains vocabulary keys that describe the properties coming in from the data source. Read the documentation to learn about vocabulary usage. | [Link](/key-terms-and-features/vocabularies) |
-| Codes (identifiers) | This is a mechanism that CluedIn uses to define the uniqueness of a golden record. Read the documentation to understand the concept of origin code (primary identifier) and codes (identifiers). | [Link](/key-terms-and-features/entity-codes) |
-| Origin | The origin generally determines the source of golden records, and it is used in codes (identifiers). Read the documentation to understand the importance of the origin. | [Link](/key-terms-and-features/origin) |
+| Identifiers | This is a mechanism that CluedIn uses to define the uniqueness of a golden record. Read the documentation to understand the concept of primary identifier and identifiers. | [Link](/key-terms-and-features/entity-codes) |
+| Origin | The origin generally determines the source of golden records, and it is used in identifiers. Read the documentation to understand the importance of the origin. | [Link](/key-terms-and-features/origin) |
## Mapping process overview
@@ -52,19 +52,19 @@ To get a good default mapping configuration, use the **auto-mapping** option.
-It is a great way to start and define the most important mapping attributes—**entity type** and **vocabulary**. You can learn more about the process of creating mapping and find step-by-step instructions in a dedicated [article](/integration/create-mapping).
+It is a great way to start and define the most important mapping attributes—**business domain** and **vocabulary**. You can learn more about the process of creating mapping and find step-by-step instructions in a dedicated [article](/integration/create-mapping).
For lineage purposes, we recommend **keeping a vocabulary close to the source**. Later, you can map the vocabulary keys to generic, shared vocabulary keys. When you have multiple sources with vocabulary keys mapped directly to the generic, shared vocabulary keys, it can become overwhelming to have more than 10 sources mapping directly to your golden records. In order to avoid confusion for those consuming the records, it is a good practice to map to the source vocabulary first.
-## Setting up the right codes (identifiers)
+## Setting up the right identifiers
-After you selected the right entity type and vocabulary, it's time to choose the right key to produce the codes for your records.
+After you selected the right business domain and vocabulary, it's time to choose the right key to produce the identifiers for your records.
-Poorly defined codes can have a truly unexpected impact. The most common pitfall of poorly defined codes is what we call _over-merging_. It happens when you set up a code that is not actually unique. Suppose you choose the country code as a key, then all records with the same country code will merge together into one record. For example, if you have 100,000 records with the country code of "DK", then all those 100,000 records will end up as 1 record.
+Poorly defined identifiers can have a truly unexpected impact. The most common pitfall of poorly defined identifiers is what we call _over-merging_. It happens when you set up an identifier that is not actually unique. Suppose you choose the country code as a key, then all records with the same country code will merge together into one record. For example, if you have 100,000 records with the country code of "DK", then all those 100,000 records will end up as 1 record.
-Poorly defined codes can cause system slowdowns. While **reverting is possible, it will take time** as now CluedIn will need to _split_ those records. At that point, the fastest solution is to remove those records from CluedIn and restart the mapping. With the country code example, it is easy to understand that using non-unique properties as identifiers is not a good choice.
+Poorly defined identifiers can cause system slowdowns. While **reverting is possible, it will take time** as now CluedIn will need to _split_ those records. At that point, the fastest solution is to remove those records from CluedIn and restart the mapping. With the country code example, it is easy to understand that using non-unique properties as identifiers is not a good choice.
Sometimes, the key you consider unique is not in fact unique. For example, a SKU code—unique internal product code—can have the following issues:
@@ -86,11 +86,11 @@ Of course, CluedIn has ways to fix such data quality issues. However, if you bli
This is an introductory article on the topic of mapping. We'll add more detailed articles soon, as mapping is a significant part of the processes in CluedIn. As an outcome of this article, you know about 2 important decisions you have to make while creating mapping:
-- Choose the **right entity type** (business domain).
+- Choose the **right business domain**.
- Choose the **right vocabulary** that is close to the source.
-Additionally, you now know about the importance of choosing the **unique key** for producing the codes (identifiers). If you are unsure whether the selected key is unique, you can use a deduplication project to detect and merge duplicates.
+Additionally, you now know about the importance of choosing the **unique key** for producing the identifiers. If you are unsure whether the selected key is unique, you can use a deduplication project to detect and merge duplicates.
## Next step