Setting up your default Watson Studio catalog

When you install Watson Studio, a default catalog is created. Catalogs are normally provided by the IBM Knowledge Catalog service, but you can also access the one default catalog in deployments that include Watson Studio but not IBM Knowledge Catalog. By default, only the default administrator has access to the catalog. If you don't plan to install IBM Knowledge Catalog, you can set up the default catalog if you want to enable watsonx Watson Studio users to share data and assets.

You can use your catalog to easily find and share your data and other assets. A catalog is like a private community for your organization. It’s a way to organize resources for many data science projects: data assets, models, other types of assets, and the users who need to use the assets.

The default catalog provided by Watson Studio has the following restrictions:

  • Limited to 50 assets
  • Limited to 50 collaborators

In addition to these restrictions, if the IBM Knowledge Catalog service is not installed, then your catalog assets do not have access to many powerful capabilities from IBM Knowledge Catalog, including features that manage data quality, data governance, lineage, relationships, and more. For more information about the capabilities that IBM Knowledge Catalog provides, see Data governance in the Cloud Pak for Data documentation.

The name of the default catalog is Default Catalog. Initially, the only member of the default catalog is the Cloud Pak for Data default Admin user.

If the default Admin user is suppressed when Watson Studio is installed, the default catalog is not created automatically and a user with the Administrator role must create the default catalog. If you plan to suppress the default Admin user after the default catalog is created, make sure the catalog has a collaborator with the Admin role other than the Admin user.

Setting up the default catalog

The Admin user must set up the default catalog.

To set up the automatically-created default catalog:

  1. Open the catalog. Choose Catalogs > All catalogs from the navigation menu and then click Default Catalog.
  2. Add collaborators to the catalog with the appropriate catalog roles. All Cloud Pak for Data user roles have permission to access the catalog. For more information, see Add collaborators and catalog roles in the Cloud Pak for Data documentation. Catalog roles determine user permissions within a specific catalog:
    • Admin: Control collaborators and assets. If you don't want to be the only user who can add collaborators to the catalog, give this role to one or more collaborators.
    • Editor: Control assets within the catalog and use them in projects.
    • Viewer: Find assets in the catalog and use them in projects.

If you later delete the default catalog, you can create a new default catalog manually.

You can also add collaborators by using an API instead of the user interface. See IBM Knowledge Catalog API: Adding members to a catalog.

Creating the default catalog manually

If the default catalog is not created automatically, a user with the Cloud Pak for Data Administrator role or the Manage catalogs permission must create the default catalog.

To manually create the default catalog:

  1. Go to Administration > Catalogs and then click the Catalog Setup tab.

  2. Enter the catalog name and description and click Create.

  3. Open the catalog. Choose Catalogs > All catalogs from the navigation menu and then click the catalog name.

  4. Add collaborators to the catalog with the appropriate catalog roles. For more information, see Add collaborators and catalog roles in the Cloud Pak for Data documentation.

  5. Load and publish the predefined data classes:

    1. Create a Cloud Pak for Data bearer access token. See Creating a Cloud Pak for Data bearer token.

    2. Run this curl command:

      curl -k -X POST \
'https://{cpd_cluster_host}/v3/glossary_terms/admin/initialize_content' \
    -H "accept: application/json" \
    -H "Authorization: Bearer {token} " \
    -H "Content-Type: application/json" \
    -d "{}"

      Replace these variables:

      • {cpd_cluster_host} → Your Cloud Pak for Data cluster host name
      • {token} → Your bearer access token

You can also create the default catalog by using an API instead of the user interface. See Data and AI Common Core API: Creating the default catalog.

Learn more