Semantic types classify the meaning and role of data fields. You can view built-in semantic types, assign them to fields, create custom semantic types from profile data, and update or remove assignments.
A semantic type is a category that classifies the meaning or role of a concept, entity, or data field within a specific context. Rather than focusing on structure or syntax, semantic types group items based on what they represent or signify. Semantic types are determined by their associated semantic type qualifiers, which are standardized codes or identifiers that classify data fields according to their semantic meaning and purpose.
Common semantic types: The following table lists commonly recognized semantic types with their qualifiers and examples:
| Semantic type name | Semantic type qualifier | Description | Example |
|---|---|---|---|
| Email Address | Identifies a string as an email address. Represents valid, commonly used real-world email values. | user@example.com | |
| Telephone Number (Generic) | TELEPHONE | Identifies a string as a phone number. Represents valid, commonly used real-world phone values. | +1 415 555 9823 |
| Country As A String (English) | COUNTRY.TEXT_EN | Identifies a string as a country code in English. Represents valid, commonly used real-world country codes. | US |
| Social Security Number (US) | SSN | Identifies a string as a US Social Security Number. Represents valid, commonly used real-world SSN values. | 123-45-6789 |
| Postal Code (US) | POSTAL_CODE.ZIP5_US | Identifies a string as a US postal code. Represents valid, commonly used real-world postal code values. | 94105 |
| Street Address | STREET_ADDRESS2_EN | Identifies a string as a postal address in English. Represents valid, commonly used real-world address values. | 221B Baker Street, London |
| First Name | NAME.FIRST | Identifies a string as a first name. Represents valid, commonly used real-world first name values. | Michael |
| Last Name | NAME.LAST | Identifies a string as a last name. Represents valid, commonly used real-world last name values. | Thompson |
| Merged Name (Last, First) | NAME.LAST_FIRST | Identifies a string as a name combining both first and last names. Represents valid, commonly used real-world name values. | Michael Thompson |
| City or Town | CITY | Identifies a string as the name of a city. Represents valid, commonly used real-world city values. | San Francisco |
| US State Code | STATE_PROVINCE.STATE_US | Identifies a string as the name of a US state. Represents valid, commonly used real-world state values. | California |
Semantic type states: A field can have one of the following semantic type states:
- Not detected: No semantic type has been assigned to the field. This is the initial state before automatic detection runs or before you manually assign a type.
- Detected type: A semantic type has been automatically detected and assigned to the field.
- Manually assigned type with Overridden badge: A semantic type has been manually assigned, overriding any automatic detection. The system displays an 'Overridden' badge to indicate manual assignment.
Entry points: You can manage semantic types for a field from multiple locations:
- Details tab: In the field details page, go to the Details tab and locate the Semantic Type field in the Summary section.
- Profile tab: In the field details page, go to the Profile tab and locate the Semantic Type field in the Summary section.
- Side panel: In the Fields tab of the Catalog, select a field to open the side panel and locate the Semantic Type field.
Assign a semantic type to a field
Manually assign a semantic type to a field when automatic semantic type detection has not run or when you want to assign a specific semantic type that differs from the detected value.
Manual assignment allows you to override the default semantic type and ensures the assigned type is used for rule detection and data quality analysis.
The semantic type is now manually assigned to the field. The system displays a confirmation message indicating that the assignment is complete. The field details page shows the assigned semantic type with an Overridden badge. The manually assigned semantic type will be used for rule detection and data quality scoring, and automatic semantic type detection will not override this manual assignment.
You can track all changes to the semantic type assignment by going to the Change History tab on the field details page. This shows who made the change, what was changed, and when the change occurred.
Create a custom semantic type from profile
Create a custom semantic type directly from an asset's profile data when advanced profiling has detected a regex pattern.
To use the Create New Semantic Type from Profile action, the asset must meet the following conditions:
- The asset must be advanced-profiled.
- The profile data must include a generated regex pattern derived from profiling.
If these conditions are not met, the option to create a new semantic type from the profile will not be available.
This action creates a new semantic type using values derived from the asset's profile. The system automatically populates the creation form with key attributes, including name, qualifier, data regex, header regex, base type, priority, and threshold.
Before saving, you can review and modify any of these fields to refine the semantic type definition as needed.
The semantic type is now created and available in your workspace. It receives higher detection priority in subsequent profiling runs. You can view, edit, or delete the semantic type from the Configuration menu under .
You can now assign this semantic type to other fields or use it during data profiling. Follow the steps in the "Assign a semantic type to a field" task above to assign this newly created semantic type to other fields.
Update or remove an existing semantic type
Change or clear the semantic type assignment for a field.
You can update an existing semantic type assignment when you need to change the semantic type that was previously assigned to a field, either automatically or manually. Updating the semantic type allows you to correct misidentified types or assign a more appropriate type.
The semantic type assignment is now removed. The field returns to the "Not detected" state, and automatic semantic type detection can run again on the next cataloging operation.