Adding catalog assets to a project

You can add a catalog asset to a project from within the project or from within the catalog.

Required permissions

You must have the following roles and permissions to copy a catalog asset to a project:

  • The Admin, Editor, or Viewer catalog collaborator role.
  • The Add assets to projects user permission.
Restrictions

You can't add an asset in these situations:

  • If the asset is blocked by data protection rules.
  • If the asset requires a private connection asset that you're not a member of.
  • If you're using the default Git integration, you can add only data assets and connections from a catalog to a project.

For relational data assets, if any of the columns are masked when you view the asset in the catalog, those columns are also masked when you add the asset to a project. All project collaborators see the asset the way it looks to the person who adds it from the catalog.

Asset profile information is copied to the catalog. Data quality information is not copied.

Add assets from within a project

To add catalog assets from within a project:

  1. From your project, click Assets > Import assets > Catalog asset.

  2. Choose a catalog, then select the assets that you want to import.

  3. Click Import. If the assets require connections, the connection assets are also listed to be added to the project.

The assets are added to the project.

Add assets from within the catalog

To add assets to a project from the catalog:

  1. From the catalog Browse page, search for the assets you want to add and select them.

  2. Click Add to project. If any of the assets require a connection, those connections are listed and get added to the project as connection assets. If you don't want to add a connection, you can remove it. All assets that require the removed connection are removed from the list of assets to add.

    When you're inside of a governed catalog and click Add to project, information about new data protection rule enforcement protocol appears. You must acknowledge it to continue. The data protection rules apply only to deeply enforced assets (data sources that are integrated with deep enforcement solutions, such IBM Data Virtualization, IBM Security Guardium Data Protection, or IBM watsonx.data). These rules don't apply to local assets. As a result, local assets, such as CSV files are unmasked in the catalog view.

    If you don't have the Add assets to projects permission, the Add to project button is disabled.

  3. Choose the project name.

  4. Click Add.

    The assets are added to the project.

    • If you added an identical data asset from a catalog to a project, you don't become the asset owner of the newly added data asset. You're the asset creator and have the asset viewer role.
    • The newly created data asset references the shared properties of the existing data asset.
    • If you're not the asset owner or asset editor of the data asset, you can't edit the shared properties.
    • If shared properties for the catalog assets are made, they're automatically reflected in the project version of the asset.

    For more information, see Identical data assets.

Next steps

Parent topic: Adding data to a project