Creating a catalog

You create a catalog to organize your assets and collaborators.

Requirements

The default catalog is created during installation.

Required permission

Required role:

You must have this user permission to create a catalog:

Manage catalogs

Storage requirement

The file storage that you associate with the catalog will contain files for assets that are copied into the catalog. For example, if you add local files or a notebook to the catalog, the information about those files are stored as assets in the catalog and the associated files are stored in the file storage.

Procedure

To create a catalog:

Click Catalogs > All catalogs to get to the Your Catalogs page, and then click New Catalog.
Specify these properties:
- A name and optional description for the catalog.
  The name can be 1–256 printable Unicode characters. ISO control characters and Unicode special characters are not allowed.
  The name must be unique. If, for any reason, you want to allow duplicate names, use the API to create or update catalogs. See the API documentation in the Data and AI Common Core API under Create a catalog.
- Whether to enable governance for the catalog. You can decide whether you want to enforce data protection rules on your catalog or not only while you are creating the catalog. After you create it, you cannot change this setting.
- Whether to enable shared properties across workspaces for governed catalogs. You can't change this setting after you create the catalog.
- Whether to allow reporting on this catalog assets metadata.
- Duplicate asset handling. By default, duplicate handling is set to allow duplicates.
- How you want to configure asset removal. You can either select to purge the assets automatically after the removal or 30 days after it.
Click Create. You can now add assets and collaborators to your catalog.

Enforcing data protection rules

Base Premium

Data protection rules apply to all governed catalogs and all assets within these catalogs. Data protection rules are automatically enforced when a catalog member attempts to view or act on a data asset in a governed catalog to prevent unauthorized users from accessing sensitive data.

However, if the user who is trying to access the asset is the owner of the asset (by default, the user who created the asset), then access is always granted. See Data Protection Rules.

You can decide whether you want to enforce data protection rules on your catalog or not only while you are creating the catalog. After you create it, you cannot change this setting.

The default catalog, is automatically governed, so that data protection rules are enforced.

Reporting on asset metadata

If you allow reporting, the reporting administrator can enable reporting on this catalog's asset metadata and store such metadata in an external database. By default, this setting is off. To set up and enable reporting, go to Administration > Governance and catalogs > Reporting setup.

Duplicate asset handling

When assets are added to a catalog, it can happen that an asset with a duplicate already exists in the catalog. You can specify what action should be taken in such a case. The choices you have are determined by the catalog default setting. Find out how you can specify duplicate asset handling in Handling duplicate assets in catalogs.

Asset removal

When you create a new catalog, you can decide how you want to configure removing assets. You can either select to purge the assets automatically from the trash and get them permanently deleted immediately after the removal or 30 days after the removal, in which case the assets remain in the trash for the next 30 days and you can restore them if needed.

All previously created catalogs have Never purge assets option selected by default. You can change this setting to any other of the purge options on the catalog Settings page.

You can also create a catalog by using the Data and AI Common Core API. See Create a catalog with the Data and AI Common Core API.

Learn more

Parent topic: Administering a catalog