Exporting Custom Property Values

After associating custom properties to object types, you can set values for the properties by exporting the objects and the associated custom properties into a file, add values to the custom properties, and import it to Data Catalog. This method helps you to enrich technical metadata in bulk.

Exporting the values of custom properties are available for data assets that are created using a relational database or Oracle Object Storage. Examples of relational database include Microsoft SQL Server, MySQL, and Oracle Database. For data assets created using a relational database, you can export custom property values at the schema and data entity levels. For Oracle Object Storage, at the bucket and data entity levels.

    1. On the Home tab, click Data Assets.
    2. On the Data Assets page, from the list of data assets, select the data asset for which you want to enrich the metadata.
    3. In the data asset detail page, depending on the data asset, click the appropriate tab as follows:
      • Schemas for relational database
      • Buckets for Oracle Object Storage
    4. Select the schema or the bucket for which you want to export the custom property values.
    5. In the details page, click Export custom properties.
      Note

      To export at the data entity level, click the Data Entities tab of the schema or bucket and select the data entity for which you want to export the values. In the data entity details page, click Export custom properties.
    6. In the Export custom properties panel, select the object types for which you want to export the custom property values.
      The object types are displayed depending on the object level at which you're exporting. For example, for a relational database, if you're exporting at the schema level, you can select from the schema, data entities, or attributes object types. For Oracle Object Storage, if you're exporting at the bucket level, you can select from the bucket, data entities, or attributes object types
      After you select the object types, provide the following details to specify the location where the file is exported:
      • Compartment: Select the compartment of the Object Storage bucket.
      • Bucket: Select the bucket in which the exported file needs to be stored.
      • Filename: Enter the filename without an extension. If the specified file already exists in the bucket, it gets overwritten with the latest content.
    7. Click Export.

      An Excel file gets downloaded to the specified bucket. The name of the Excel file indicates the name of the object at which you clicked Export custom properties.

      The Excel file contains a ReadMe sheet and as many sheets as the types of objects that you selected to be exported. The ReadMe sheet includes details of the selected object types, the root object, the date and time of export, and so on. The subsequent sheets are named based on the object types. They contain the objects of that type with the custom properties associated with the objects, and their existing values, if any.

      In each of the object type sheet, enter values for the custom properties. While adding details to the Excel file, remember the following:
      • Don't change the Type, Object path, and Name columns—they're intended to provide you additional information.
      • Don't change the values in the Internal Key column, as the column is used to uniquely identify an object during import.
  • This task isn't available in the CLI.

  • This task isn't available in the API.