You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/purview/how-to-create-import-export-glossary.md
+10-8Lines changed: 10 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@ ms.date: 03/09/2022
11
11
12
12
# Create, import, export, and delete glossary terms
13
13
14
-
This article describes how to work with the business glossary in Microsoft Purview. It provides steps to create a business glossary term in the Microsoft Purview data catalog. It also shows you how to import and export glossary terms by using .csv files, and how to delete terms that you no longer need.
14
+
This article describes how to work with the business glossary in Microsoft Purview. It provides steps to create a business glossary term in the Microsoft Purview data catalog. It also shows you how to import and export glossary terms by using .CSV files, and how to delete terms that you no longer need.
15
15
16
16
## Create a term
17
17
@@ -102,11 +102,13 @@ To create a glossary term, follow these steps:
102
102
103
103
## Import terms into the glossary
104
104
105
-
The Microsoft Purview data catalog provides a template .csv file for you to import terms from the catalog into your glossary. Duplicate terms include both spelling and capitalization, because term names are case-sensitive.
105
+
The Microsoft Purview data catalog provides a template .CSV file for you to import terms from the catalog into your glossary. Duplicate terms include both spelling and capitalization, because term names are case-sensitive.
106
106
107
107
1. On the **Glossary terms** page, select **Import terms**.
108
108
109
-
2. The term template page opens. Match the term template to the kind of .csv file that you want to import, and then select **Continue**.
109
+
The term template page opens.
110
+
111
+
2. Match the term template to the kind of .CSV file that you want to import, and then select **Continue**.
110
112
111
113
:::image type="content" source="media/how-to-create-import-export-glossary/select-term-template-for-import.png" alt-text="Screenshot of the template list for importing a term, with the system default template highlighted.":::
112
114
@@ -117,13 +119,13 @@ The Microsoft Purview data catalog provides a template .csv file for you to impo
117
119
> [!Important]
118
120
> The system supports only importing columns that are available in the template. The **System default** template will have all the default attributes.
119
121
>
120
-
> Custom term templates define out-of-the box attributes and additional custom attributes. Therefore, the .csv file differs in the total number of columns and the column names, depending on the term template that you select. You can also review the file for problems after upload.
122
+
> Custom term templates define out-of-the box attributes and additional custom attributes. Therefore, the .CSV file differs in the total number of columns and the column names, depending on the term template that you select. You can also review the file for problems after upload.
121
123
>
122
-
> If you want to upload a file with a rich text definition, be sure to enter the definition with markup tags and populate the column `IsDefinitionRichText` to `true` in the .csv file.
124
+
> If you want to upload a file with a rich text definition, be sure to enter the definition with markup tags and populate the column `IsDefinitionRichText` to `true` in the .CSV file.
123
125
124
126
:::image type="content" source="media/how-to-create-import-export-glossary/select-file-for-import.png" alt-text="Screenshot of the button for downloading a sample template file.":::
125
127
126
-
4. After you finish filling out your .csv file, select your file to import and then select **OK**.
128
+
4. After you finish filling out your .CSV file, select your file to import, and then select **OK**.
127
129
128
130
The system will upload the file and add all the terms to your glossary.
129
131
@@ -141,7 +143,7 @@ Select **Export terms** to download the selected terms.
141
143
:::image type="content" source="media/how-to-create-import-export-glossary/select-term-template-for-export.png" lightbox="media/how-to-create-import-export-glossary/select-term-template-for-export.png" alt-text="Screenshot of the button to export terms on the glossary terms page.":::
142
144
143
145
> [!Important]
144
-
> If the terms in a hierarchy belong to different term templates, you need to split them into different .csv files for import. Also, the import process currently doesn't support updating the parent of a term.
146
+
> If the terms in a hierarchy belong to different term templates, you need to split them into different .CSV files for import. Also, the import process currently doesn't support updating the parent of a term.
145
147
146
148
## Delete terms
147
149
@@ -191,7 +193,7 @@ If [workflows](concept-workflow.md) are enabled on a term, then any create, upda
191
193
192
194
- **Deletion**: When a delete approval workflow is enabled on the parent term, you see **Submit for approval** instead of **Delete** when you're deleting the term. Selecting **Submit for approval** triggers the workflow. However, the term won't be deleted from the catalog until all the approvals are met.
193
195
194
-
- **Importing terms**: When an import approval workflow is enabled for the Microsoft Purview glossary, you see **Submit for approval** instead of **OK** in the **Import** window when you're importing terms via .csv file. Selecting **Submit for approval** triggers the workflow. However, the terms in the file won't be updated in the catalog until all the approvals are met.
196
+
- **Importing terms**: When an import approval workflow is enabled for the Microsoft Purview glossary, you see **Submit for approval** instead of **OK** in the **Import** window when you're importing terms via .CSV file. Selecting **Submit for approval** triggers the workflow. However, the terms in the file won't be updated in the catalog until all the approvals are met.
195
197
196
198
:::image type="content" source="media/how-to-create-import-export-glossary/create-submit-for-approval.png" alt-text="Screenshot of the window for creating a new term and the button for submitting the term for approval." border="true":::
0 commit comments