# Resource properties Pentaho Data Catalog modifies discovered resource properties to add user-defined metadata to the resource. This metadata holds business value or communicates the data quality of the resource. ## Properties Pentaho Data Catalog discovers metadata properties of resources during the **Data Profiling** (for structured data) and **Data Discovery** (for unstructured data) processes. Data Catalog provides a set of built-in properties that are system-defined metadata attributes available for selected asset types. Built-in properties are predefined metadata fields that appear in the **Properties** section of supported assets, such as glossaries and policies. Unlike custom properties, built-in properties are created and managed by the system and follow a standardized structure. These properties are available by default and are intended to capture commonly required governance and descriptive information. To access built-in properties in Data Catalog, log in as an administrator and click **Management** in the left navigation menu. On the Management page, click **View Built-in Properties** to view the list of system-defined properties and their descriptions.
Built-in properties are grouped into two categories based on their purpose and level of control. ### **Mandatory properties** Mandatory properties are core metadata attributes that are always visible in the **Properties** panel and cannot be hidden, as they are meant for the governance processes or actions. Mandatory properties are applied consistently across supported asset hierarchies to ensure that essential metadata is always available to users. ### **Non-mandatory properties** Non-mandatory properties are optional built-in metadata attributes whose visibility in the **Properties** panel can be controlled by administrators by enabling or disabling them from the **Management** section. Non-mandatory properties allow organizations to simplify the user interface and remove properties that are not relevant to their business needs. {% hint style="info" %} Built-in property visibility management is currently supported for the Glossary and Policies asset types. When a non-mandatory property is disabled, it is hidden from the user interface, but any existing metadata values are retained. Re-enabling the property restores its visibility and retains its existing values. For more information, see [Manage properties](/pdc-admin/manage-properties.md#enable-or-disable-built-in-properties). {% endhint %} > ▶️ **Watch a walkthrough** > > You can watch a guided walkthrough that demonstrates how to [customize the visibility of built-in properties](https://assets.demos.hitachivantara.com/psl/54h0b23) in Data Catalog. > > {% embed url="" %} ## Custom properties Custom properties let organizations extend the metadata model in Data Catalog by defining additional attributes that are specific to their business, governance, or operational needs. You can use custom properties to: * Capture organization-specific metadata that is not provided out of the box. * Standardize how additional information is recorded across assets. * Improve data understanding and governance by adding structured, validated attributes. * Reduce reliance on free-text descriptions for structured information. Custom properties complement other metadata features such as descriptions, business terms, tags, and data labels, and are designed to work consistently across supported hierarchies. The following hierarchies support custom properties: * **Data resources** (datasets, files, tables, and data collections) * **Business glossaries** (glossaries, categories, and terms) * **Applications** * **Policies and standards** * **Business Intelligence assets** * **Physical Assets** * **Machine Learning (ML) Models** Custom properties are user-defined metadata that let organizations extend the metadata model in Data Catalog by defining additional attributes that are specific to their business, governance, or operational needs. You can use custom properties to: * Capture organization-specific metadata that is not provided out of the box. * Standardize how additional information is recorded across assets. * Improve data understanding and governance by adding structured, validated attributes. * Reduce reliance on free-text descriptions for structured information. Custom properties complement other metadata features such as descriptions, business terms, tags, and data labels, and are designed to work consistently across supported hierarchies. The following hierarchies support custom properties: * **Data resources** (datasets, files, tables, and data collections) * **Business glossaries** (glossaries, categories, and terms) * **Applications** * **Policies and standards** * **Business Intelligence assets** * **Physical Assets** * **Machine Learning (ML) Models** Custom properties appear in the **Custom Properties** pane on the **Summary** or **Custom** **Properties** tab when you select a resource. The description below each field typically explains how the property is used or what values it can take. For example:
CategoryExample custom propertyExample values
Business contextBusiness UnitRetail, Finance, HR
Data managementData OwnerJohn Smith, Jane Doe
ComplianceRegulatory ZoneGDPR, HIPAA, CCPA
OperationsCriticality LevelHigh, Medium, Low
TechnicalSource SystemSAP, Salesforce, Snowflake
### Role-based responsibilities In Data Catalog, custom properties follow a clear separation of responsibilities based on user roles, ensuring that metadata definitions remain controlled while allowing domain experts to populate accurate values.: * **Administrators** manage the lifecycle of custom properties. They create, edit, and delete properties and define where those properties apply. * **Stewards** (such as Data Stewards and Business Stewards) assign values to custom properties on individual assets within their area of responsibility. * **Other users** can view custom properties and their assigned values, but cannot modify them. To know more about user roles, see [User roles and permissions in Data Catalog](https://docs.pentaho.com/pdc-use/pdc-user-roles-and-permissions). #### Centralized management model Custom properties are managed from a centralized **Custom Properties** area in the **Management** section in Data Catalog. From the management area, administrators can create new custom properties, define where each property applies, and edit or delete existing custom properties. For more information, see [Manage custom properties](/pdc-admin/manage-custom-properties.md). #### Supported field types Custom properties support multiple field types to ensure accurate data capture and validation. The field type determines how values are entered, validated, and displayed when stewards assign values to assets. The following table describes the field types available when creating a custom property, including their purpose, expected values, and behavior during value assignment.
Field typeDescriptionTypical use cases
Free TextStores free-form text without format restrictions. It accepts alphanumeric and special characters. No format validation is applied.Notes, comments, descriptive qualifiers
URLStores a web address that links to an external resource. It accepts only valid URL formats and displays as a clickable link.Policy documents, external systems, reference links
NumberStores numeric values only. It accepts numeric input only.Scores, thresholds, numeric identifiers
BooleanStores a true or false (binary) value.Compliance flags, approval indicators, and status attributes
DateStores a calendar date. It uses a date picker to prevent invalid date formats.Review dates, expiration dates, and certification dates
UsersStores multiple Data Catalog users. It allows selecting multiple valid users.Shared ownership, review groups, escalation contacts
Select StringStores a text value selected from a predefined list. It allows selection from predefined string options and doesn’t accept arbitrary values.Status values, categories, standardized labels
Select NumberStores a numeric value selected from a predefined list. It allows selection from predefined numeric options and doesn’t accept arbitrary values.Priority levels, rating scales, and standardized numeric classifications
{% hint style="warning" %} Once a custom property is created, its field type cannot be changed. If you need a different type, you must delete the property and create a new one. {% endhint %} ### Applicability and scope control When creating a custom property, an administrator defines its scope to prevent unnecessary properties from appearing on unrelated assets, reducing visual and semantic clutter. Scope determines where the property is available for use. Scope definition includes: * **Hierarchy selection**: Specifies which catalog hierarchies the property applies to, such as Data Canvas, Business Glossary, Applications, Policies and Standards, BI assets, Physical Assets, or ML Models. Additionally, custom properties can be restricted to specific roots within a selected hierarchy. For example, a property can apply only to terms under a particular glossary domain and not to the entire glossary. * **Asset type selection**: Limits the property to specific asset types within a hierarchy, such as tables, columns, schemas, or glossary terms. * **Root-level restriction** (optional): Further narrows applicability to specific roots within a hierarchy, allowing fine-grained control. However, fine-grained root selection is available when a single hierarchy is selected. When creating a custom property, administrators can specify whether the property appears on the **Summary** tab by default. This option helps to highlight important properties for quick visibility and hide less frequently used properties. {% hint style="info" %} These display settings affect only visibility, not assignment availability. {% endhint %} ### Assign values to custom properties You can assign values to custom properties on assets to enrich assets with structured, business-specific metadata. These values provide additional context that supports governance, ownership, compliance, and data discovery. Custom property values are assigned at the asset level and are governed by role-based permissions and field-type validation rules. Perform the following procedure to assign a value to a custom property of an asset in Data Catalog: Only users with appropriate steward roles can assign values to custom properties. **Before you begin** Ensure that the following conditions are met: * A custom property is already created and assigned to the relevant hierarchy and asset type. * You are signed in as a **Data Steward** or **Business Steward**, and have access to the asset on which you want to assign the custom property value. **Procedure** 1. In the left navigation menu, select a hierarchy depending on the asset type. 2. Browse the hierarchy and select the asset to which you want to assign a custom property value.\ For example, select a folder, schema, table, or column. 3. In the asset content pane, click the **Custom Properties** tab. 4. In the **Custom Properties** table, locate the custom property for which you want to assign a value. 5. In the **Value** column, enter or select a value based on the field type of the custom property: * **Free Text**: Type the required text. * **URL**: Enter a valid URL. * **Number**: Enter a numeric value. * **Boolean**: Select true or false. * **Date**: Select a date from the date picker. * **Users**: Select one or more users from the list. * **Select String / Select Number**: Select a value from the predefined list. 6. Press **Enter** or click outside the field to save the value.\ The value is saved automatically. **Result** The custom property value is assigned to the selected asset and is displayed in the **Custom Properties** tab. If the property is configured to appear in the **Summary** view, the value is also visible in the **Custom Properties** panel on the **Summary** tab. #### Role-based responsibilities In Data Catalog, custom properties follow a clear separation of responsibilities based on user roles, ensuring that metadata definitions remain controlled while allowing domain experts to populate accurate values.: * **Administrators** manage the lifecycle of custom properties. They create, edit, and delete properties and define where those properties apply. * **Stewards** (such as Data Stewards and Business Stewards) assign values to custom properties on individual assets within their area of responsibility. * **Other users** can view custom properties and their assigned values, but cannot modify them. To know more about user roles, see [User roles and permissions in Data Catalog](https://docs.pentaho.com/pdc-use/pdc-user-roles-and-permissions). #### Centralized management model Custom properties are managed from a centralized **Custom Properties** area in the **Management** section in Data Catalog. From the management area, administrators can create new custom properties, define where each property applies, and edit or delete existing custom properties. For more information, see [Manage custom properties](https://docs.pentaho.com/pdc-admin/manage-custom-properties). #### Supported field types Custom properties support multiple field types to ensure accurate data capture and validation. The field type determines how values are entered, validated, and displayed when stewards assign values to assets. The following table describes the field types available when creating a custom property, including their purpose, expected values, and behavior during value assignment.
Field typeDescriptionTypical use cases
Free TextStores free-form text without format restrictions. It accepts alphanumeric and special characters. No format validation is applied.Notes, comments, descriptive qualifiers
URLStores a web address that links to an external resource. It accepts only valid URL formats and displays as a clickable link.Policy documents, external systems, reference links
NumberStores numeric values only. It accepts numeric input only.Scores, thresholds, numeric identifiers
BooleanStores a true or false (binary) value.Compliance flags, approval indicators, and status attributes
DateStores a calendar date. It uses a date picker to prevent invalid date formats.Review dates, expiration dates, and certification dates
UsersStores multiple Data Catalog users. It allows selecting multiple valid users.Shared ownership, review groups, escalation contacts
Select StringStores a text value selected from a predefined list. It allows selection from predefined string options and doesn’t accept arbitrary values.Status values, categories, standardized labels
Select NumberStores a numeric value selected from a predefined list. It allows selection from predefined numeric options and doesn’t accept arbitrary values.Priority levels, rating scales, and standardized numeric classifications
Once a custom property is created, its field type cannot be changed. If you need a different type, you must delete the property and create a new one. #### Applicability and scope control When creating a custom property, an administrator defines its scope to prevent unnecessary properties from appearing on unrelated assets, reducing visual and semantic clutter. Scope determines where the property is available for use. Scope definition includes: * **Hierarchy selection**: Specifies which catalog hierarchies the property applies to, such as Data Canvas, Business Glossary, Applications, Policies and Standards, BI assets, Physical Assets, or ML Models. Additionally, custom properties can be restricted to specific roots within a selected hierarchy. For example, a property can apply only to terms under a particular glossary domain and not to the entire glossary. * **Asset type selection**: Limits the property to specific asset types within a hierarchy, such as tables, columns, schemas, or glossary terms. * **Root-level restriction** (optional): Further narrows applicability to specific roots within a hierarchy, allowing fine-grained control. However, fine-grained root selection is available when a single hierarchy is selected. When creating a custom property, administrators can specify whether the property appears on the **Summary** tab by default. This option helps to highlight important properties for quick visibility and hide less frequently used properties. These display settings affect only visibility, not assignment availability. ### Assign values to custom properties You can assign values to custom properties on assets to enrich assets with structured, business-specific metadata. These values provide additional context that supports governance, ownership, compliance, and data discovery. Custom property values are assigned at the asset level and are governed by role-based permissions and field-type validation rules. Perform the following procedure to assign a value to a custom property of an asset in Data Catalog: Only users with appropriate steward roles can assign values to custom properties. **Before you begin** Ensure that the following conditions are met: * A custom property is already created and assigned to the relevant hierarchy and asset type. * You are signed in as a **Data Steward** or **Business Steward**, and have access to the asset on which you want to assign the custom property value. **Procedure** 1. In the left navigation menu, select a hierarchy depending on the asset type. 2. Browse the hierarchy and select the asset to which you want to assign a custom property value.\ For example, select a folder, schema, table, or column. 3. In the asset content pane, click the **Custom Properties** tab. 4. In the **Custom Properties** table, locate the custom property for which you want to assign a value. 5. In the **Value** column, enter or select a value based on the field type of the custom property: * **Free Text**: Type the required text. * **URL**: Enter a valid URL. * **Number**: Enter a numeric value. * **Boolean**: Select true or false. * **Date**: Select a date from the date picker. * **Users**: Select one or more users from the list. * **Select String / Select Number**: Select a value from the predefined list. 6. Press **Enter** or click outside the field to save the value.\ The value is saved automatically. **Result** The custom property value is assigned to the selected asset and is displayed in the **Custom Properties** tab. If the property is configured to appear in the **Summary** view, the value is also visible in the **Custom Properties** panel on the **Summary** tab. ## Data labels Data labels in Data Catalog are structured metadata elements defined as key-value pairs, designed to provide standardized, informative machine-readable labels derived from data content to data assets such as tables, columns, datasets, and files. Data Labels are intended for use by consumers of data, such as ML Models. While similar in format to [#custom-properties](#custom-properties "mention"), which also use key-value pairs, Data labels are meant for a specific purpose of data labeling, a concept required for supervised machine learning. This structured approach helps you to manage metadata more effectively, particularly for use cases involving AI, machine learning, and data governance. With data labels, you can classify data using consistent terminology, such as '*Sensitivity*: *Confidential*' or '*Data Quality*: *High*', which improves model training, search accuracy, and compliance. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.pentaho.com/pdc-use/ldc-resource-properties-user-guide-cp.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.