Data marketplace: required actions during the activation of the new experience
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.
Your migration options :
Custom views | Actions | Action owner |
You have many views or complex code. | Run an automatic migration script that will turn your custom views into Page-type assets. | CSM |
You want to clean up and optimize the experience. | Recreate the views via the Custom views tab. | Portal administrator |
⚠️ Without action on your side, your old custom views will no longer be visible after activation.
For more details, see the article in our Community.
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.
Actions are therefore required before and during the activation phase:
Identify duplicates (multiple “identical” reuses).
Identify reuses that point to assets already in the catalog (internal pages or datasets).
Your migration options:
Reuses | Actions | Action owner |
You have no duplicates and no internal links. | Run an automatic migration script that will turn your reuses into use cases. | CSM |
You have duplicates and/or internal links. | Recreate the use cases manually. | Portal administrator |
Need the full story? See the relevant post in our Community.
3. Calendar and images views
In the data marketplace 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. Column visibility and security
t is no longer possible to “hide” columns for display purposes only (via the Visualizations tab). Visibility is now strictly aligned with data security.
Situation | Action to take |
|---|---|
Sensitive fields | If you hid columns for security reasons, manage these through the dataset's security settings, not visibility. |
Non-relevant fields | Remove the column from the schema if it doesn't need to be visible or is just intermediate data. |
Less important columns | Move the column to the far right of the table for less prominence if it's useful but not essential for front end display. |
Editorialized tables | Create a custom view if you need a specific view with filtered, sorted, or limited columns. The full Explorer will remain available, but you can control the first view with full flexibility. |
If you’re unsure, we can directly provide you with the list of datasets that have columns hidden via the Visualizations > Table setting. You’ll then be able to handle the adjustments yourself.
5. 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://<yourdomain>.opendatasoft.com/api/explore/v2.1/catalog/datasets/?where=visualization.map_tooltip_html_enabled=true&apikey=<your_api_key>The API key must have the permission Browse all datasets to get the list of public and restricted datasets.
6. 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.