Data marketplace: required actions during the activation of the new experience

Edited

This page is part of our guide to the new data marketplace experience. You can also see our other pages about what's new or different, as well as how to preview the new experience on your portal.

Many domains can jump straight to activation, but if your catalog contains any of the items listed below, you’ll need to perform some actions to ensure service continuity before the data marketplace is activated on your domain.

1. Custom views

In the new experience, custom views are integrated into the conversion funnel. They become fully measurable (click-through rate tracking) and are limited to 7 views per asset.

2. Reuses

The former “Reuse” concept is evolving into Showcases. They become full-fledged catalog assets, benefiting from the same visibility controls and metadata as datasets.

Impacts:

  • The ods-reuses widget will no longer work.

  • As soon as the new experience is activated in the back office, the Reuses management area disappears.

  • Your reuses will appear in your "requests" tab. Validate them if you want to make them visible and searchable by your users.

3. Calendar and images views

In the new experience, calendar and image views tabs will no longer be available due to low usage and limited value.

For images, we launched asset thumbnails: add a cover image to any asset and choose whether it appears on its catalogue card.

What can you do? It’s up to you to decide and apply the changes before activation:

Situation

Action to take

Low usage or value

Delete calendar or image views if they haven’t served a clear purpose or haven't seen much engagement.

Still valuable

If you still need a gallery or calendar-style view, turn them into a page asset in the data marketplace, possibly combining multiple views into a single asset for a better user experience.

4. Custom HTML tooltips

The Explorer standardizes display for greater clarity. Custom HTML tooltips no longer appear on the default map view. They are replaced by a data exploration side panel.

  • Solution: if your tooltips contain calculations or specific code, turn this map into a Page asset (Code editor).

  • Benefit: your map becomes a searchable object with its own usage statistics.

To identify datasets using custom tooltips, use this API query:

https://<your domain name>/api/explore/v2.1/catalog/exports/csv?select=datasetid,visualization.map_tooltip_html&where=visualization.map_tooltip_html is not null&apikey=<your api key>

The API key must have the permission Browse all datasets to get the list of public and restricted datasets.

Copy the tooltip HTML snippet from the export. In your map creations, paste the snippet inside the relevant ods-map widget, within the <ods-map-layer> tag.

To find where to update : in the dataset back office, open Data lineage and locate pages/creations with a linked Geographic field—those are likely the ones with the map/tooltips to update.

5. Page management

Your existing pages are enhanced: they become searchable assets.

  • Discoverability: they now appear in search results.

  • Metadata: you can assign tags, descriptions, and owners.

  • Action required: review your technical or administrative pages. If they are not intended to be public, consider excluding them from the catalog so they do not clutter user search.