Configuring a shared catalog

The Shared Catalog option is available with the Ultimate Plan.Contact your sales representative for more information about our plans.

A Shared Catalog is a combination of the public datasets from two or more different ODS workspaces. The resulting combined catalog can then be configured to be visible at each of the individual workspaces, or else be its own separate, shared workspace.

A Shared Catalog is a good idea if you want to group all of your datasets as part of a larger organization or initiative.

For example, a region can find it useful to bring together the data from all of its different administrative levels—the region, its states or departments, metropolitan areas, cities and towns, etc. This allows users to find all the relevant data for that region in one easy location.

To enable the Shared Catalog, your portal must be public and must be part of the ODS Data Hub. Also note that some actions must be performed by your CSM.

• To make your portal public, in your back office, go to Configuration → Security, and toggle the Portal access option to Public portal. (see configuring your portal's general security policy).

• Make sure your portal is part of the ODS Data Hub (check with your CSM if you’re not sure).

• Define the unique identifier for your shared catalog. To perform this step you will need to contact your CSM. The identifier is the same for all the portals part of your shared catalog, so if a shared catalog was already started by another workspace you must ask about the existing identifier and use it.

Once the shared catalog is activated on your workspace, you have two different catalogs:

1. Your local catalog containing your own public and restricted datasets

2. Your shared catalog containing your public datasets and all the public datasets of the portals using this shared catalog

By default, your local catalog is visible at your workspace’s URL ending with /explore/, but you can change this to show the shared catalog instead.

Changing the default catalog needs to be performed by ODS. To make the shared catalog as your default catalog, please contact your CSM.

Remember that whatever your default catalog, you can always access the local and shared catalogs using their specific URLs:

• Your local catalog is always available at your workspace’s URL ending with /explore/?source=workspace

• The shared catalog is always visible at your workspace’s URL ending with /explore/?source=shared

Remember, only your public datasets are part of a shared catalog. Therefore, when you're browsing the shared catalog on your own workspace, you will not see your own private datasets, no matter what permissions you have for your private datasets.

Example: The diagram below shows an example with four workspaces. All four have the same shared catalog identifier, and thus are part of the same shared catalog.

So, if you visit the shared catalog via Workspace A's URL, the four restricted datasets of this workspace are not displayed. For the Workspace C, since this workspace has no restricted dataset, the local and the shared catalog display the same datasets of this workspace (plus the public datasets of the other workspace, of course). On the contrary the Workspace D has no public datasets, so the shared catalog does not contain datasets from Workspace D.

• Your portal’s appearance: Using the shared catalog option does not change the appearance of your datasets, nor change what information is visible in them.

• The order your datasets are displayed: Your local public datasets are always displayed first. This is to ensure that your own datasets are promoted and remain visible. No matter how your portal’s datasets are filtered (alphabetically, by last modified, etc.), your local public datasets are displayed first, before the shared datasets that might otherwise come first.

• Metadata: The metadata shared_catalog (visible while using the ODS Management APIs) is populated with the value of the unique identifier of the shared catalog.

• API Explore V2: With the API Explore V2, /api/v2/catalog/dataset allows you to see the local catalog, and /api/v2/shared/datasets allows you to see the shared catalog.