Synchronize outbound metadata via the Google Knowledge Catalog integration

Click Updated: <timestamp> next to Metadata outbound, where timestamp indicates the last time when the data was loaded from Knowledge Catalog.
The aspect fields are loaded to the dropdown list of Aspect field. This can take some time.

After you add at least one mapping, you can run a full synchronization. It sends all mapped asset attributes to Knowledge Catalog, not just recent changes. While it runs, you can't change outbound configurations, and the integration doesn't start other synchronizations. This feature is in preview.

1. On the Metadata outbound tab, click Synchronize.
2. In the confirmation dialog, click Continue.

Limit outbound synchronization to specific projects, datasets, or tables. This applies to every outbound mapping and full synchronization (in preview). Assets outside the scope aren't changed in Knowledge Catalog or BigQuery (for description mapping only). If you leave Include scope empty, everything that isn't excluded is synchronized.

1. In Include scope, click Add Included path.
2. In Included path, specify a project (project), dataset (project>dataset), or table (project>dataset>table) to include, using the names as they appear in Collibra Platform. For example, my-project>sales_*.
   • Use * for any sequence of characters and ? for exactly one character.
   • Don't add any spaces around > or include the location or entry group.
   • Matching is case-sensitive and spaces aren't removed.
   • If a path doesn't match any asset, nothing is synchronized for it and no warning appears.

Changes take effect on the next synchronization run, which can take up to 5 minutes. Widening the scope doesn't backfill assets that already exist. Run a full synchronization (in preview) to backfill them. Narrowing the scope doesn't remove values already written to Knowledge Catalog or BigQuery (for description mapping only).

Exclude specific projects, datasets, or tables from outbound synchronization. The exclude scope has priority over the include scope. For example, if you include my-project>* and exclude my-project>sales_tmp, outbound metadata is synchronized for the my-project project, except the sales_tmp dataset.

1. In Exclude scope, click Add Excluded path.
2. In Excluded path, enter a path in the same format and with the same rules as Include scope.

Configure an aspect field mapping to send a Collibra attribute value to a Knowledge Catalog aspect field.

To add an outbound aspect field mapping:

1. In the Collibra attribute to Knowledge Catalog aspect field mappings section, click Add aspect field mapping.
2. In Asset, select the asset type the mapping applies to. If you do not specify an asset type, the mapping applies to all applicable asset types by default.
3. In the Attribute field, select the attribute whose value you want to send to Knowledge Catalog.
4. In Aspect field, select the aspect and field path, in the format projectid.location.aspectId>fieldPath. For aspectId, ensure that you provide the Aspect type ID from Knowledge Catalog and not the Display name. For example, 460474087160.us.outbound-table-aspect>field.

Configure a Collibra property to a native property on the matching BigQuery object, for example, an asset's Description to a BigQuery description. This is available only for BigQuery-backed entries. Note that removing a value in Collibra does not remove the native property in BigQuery.

To add an outbound property mapping:

1. In the Collibra property to BigQuery property mappings section, click Add Collibra property to BigQuery property mapping.
2. In Asset, select the asset type the mapping applies to. If you do not specify an asset type, the mapping applies to all applicable asset types by default.
3. In the Collibra property field, select the property whose value you want to send. Currently, only Description is available.
4. In the BigQuery property field, select the native BigQuery property to receive the value. Currently, only Description is available. Note that rich-text values are written as plain text.

Configure a status mapping to send an asset's current status name to a Knowledge Catalog aspect field. On each status change, the new status name is written. When you remove the status, the integration removes the aspect field value.

1. In the Collibra asset status to Knowledge Catalog aspect field mappings section, click Add status mapping.
2. In Asset, select the asset type the mapping applies to. If you do not specify an asset type, the mapping applies to all applicable asset types by default.
3. In Aspect field, select the aspect and field path, in the format projectid.location.aspectId>fieldPath. For aspectId, ensure that you provide the Aspect type ID from Knowledge Catalog and not the Display name. For example, 460474087160.us.outbound-table-aspect>field.

Configure an articulation score mapping to send an asset's articulation score, a decimal from 0.0 to 100.0 (for example, 87.5), to a Knowledge Catalog aspect field. The integration removes the aspect field value when the score is removed.

1. In the Collibra asset articulation score to Knowledge Catalog aspect field mappings section, click Add articulation score mapping.
2. In Asset, select the asset type the mapping applies to. If you do not specify an asset type, the mapping applies to all applicable asset types by default.
3. In Aspect field, select the aspect and field path, in the format projectid.location.aspectId>fieldPath. For aspectId, ensure that you provide the Aspect type ID from Knowledge Catalog and not the Display name. For example, 460474087160.us.outbound-table-aspect>field.

Configure an average rating mapping to send an asset's average rating to a Knowledge Catalog aspect field. The average rating can be one of the following values: 0, 0.2, 0.4, 0.6, 0.8, or 1. If you remove the average rating in Collibra, the integration writes 0 to the aspect field. It does not remove the aspect field value because 0 is a valid average rating.

1. In the Collibra asset average rating to Knowledge Catalog aspect field mappings section, click Add average rating mapping.
2. In Asset, select the asset type the mapping applies to. If you do not specify an asset type, the mapping applies to all applicable asset types by default.
3. In Aspect field, select the aspect and field path, in the format projectid.location.aspectId>fieldPath. For aspectId, ensure that you provide the Aspect type ID from Knowledge Catalog and not the Display name. For example, 460474087160.us.outbound-table-aspect>field.

Configure a tag mapping to send all Collibra tags on an asset to a Knowledge Catalog aspect field as a single value, joined with semicolons (for example, PII;Sensitive). The value is replaced on each update. The integration removes the aspect field value when the asset no longer has any Collibra tags left.

1. In the Collibra tag to Knowledge Catalog aspect field mappings section, click Add tag mapping.
2. In Asset, select the asset type the mapping applies to. If you do not specify an asset type, the mapping applies to all applicable asset types by default.
3. In Aspect field, select the aspect and field path, in the format projectid.location.aspectId>fieldPath. For aspectId, ensure that you provide the Aspect type ID from Knowledge Catalog and not the Display name. For example, 460474087160.us.outbound-table-aspect>field.

Configure a responsibility mapping to send the owner of a responsibility to a Knowledge Catalog aspect field as owner name:role name (for example, Jane Doe:Data Steward). The integration removes the aspect field value when the responsibility is removed. If more than one owner holds the same role on the same asset, the aspect field shows the owner synced most recently.

1. In the Collibra responsibility to Knowledge Catalog aspect field mappings section, click Add responsibility mapping.
2. In Asset, select the asset type the mapping applies to. If you do not specify an asset type, the mapping applies to all applicable asset types by default.
3. In Role, select the resource role.
4. In Aspect field, select the aspect and field path, in the format projectid.location.aspectId>fieldPath. For aspectId, ensure that you provide the Aspect type ID from Knowledge Catalog and not the Display name. For example, 460474087160.us.outbound-table-aspect>field.