Data marketplace: Legacy elements to migrate

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 what's in the pipeline to be released.

Many domains can jump straight to activation, but if your catalog contains any of the items listed below, you’ll need to make some choices before the data marketplace is activated on your domain:

• Those who have been with us for a while know that custom views are nothing new, but over time they became a kind of Swiss-army knife, used for many different functions.

  In the data marketplace, we’ve streamlined their role: Custom views now sit squarely in the asset-conversion funnel. They're fully measurable and give admins the insight they need to run an effective marketplace, all while making information easier for end-users to find.

  • You will know the click-through rate for each custom view

  • You can have up to 7 different custom views per dataset, in the order you define, with one set as the default

  • For clean metrics, there is one block per view

  • Views are built in our no-code Studio, each with its own title and icon

  For more details, see the article in our Community.

  ⚠️ However, note that if you take no action, your legacy custom views will simply disappear from your portal when the data marketplace is activated.

  Instead, choose one of the two paths below before going live:

  1. Opendatasoft runs the auto-migration script to transform your custom views into code editor assets

     What we’ll do	Recommended?	Your effort
     We copy every legacy view into a new asset. The created asset's type is "code editor page", its default category is "Visualization" and it is tagged as a Showcase. The content and metadata stay intact; we add a “Visualization – <Dataset Title>” prefix and back-links in the dataset’s description so users land in the right place. The linked dataset or visualization is displayed in the "Similar assets" section.	- If your legacy views are true custom views (ie. they highlight the dataset itself). - If you have many views or no time to review them one by one - If they are too complex to be rebuild with our new tool (see 2.)	Just give us the green light.

  2. Rebuild your custom views with the new feature

     What we’ll do	Recommended?	Your effort
     You recreate each relevant view using the new feature (Dataset > Edit content > Custom views), taking advantage of the new metrics, titles, and icons.	- If you want to clean house and curate your data marketplace. - You prefer to redesign or drop views that no longer add value.	A few minutes per view, depending on complexity.

  Let your CSM know which path you prefer so we can schedule the migration and keep your former custom views visible from day one.

Reuses were our first way to spotlight what people built with open data. With the data marketplace, we’re broadening that idea and introducing showcases:

• Showcases = assets
  Each showcase is now a catalog asset (flag is_showcase), with the same permissions, metadata, and visibility controls as datasets.

• Works for any data
  Everything fits: Open-data projects, private dashboards, internal Power BI reports.

• Can link to several datasets
  A single submitted showcase can reference multiple datasets in the data marketplace.

• Better catalog integration
  Showcases appear in search, lineage, and usage metrics, just like any other asset.

Need the full story? See the relevant post in our Community.

If you activate the data marketplace without migrating, the reuses won’t be available anymore, and the ods-reuses widget won’t display any objects, because it will list only showcases.

Instead, choose one of these two options before going live:

1. Let us run the auto-migration script

   What we’ll do	Recommended?	Your effort
   Every Reuse becomes an asset with the propriety Showcase.	You have many Reuses or little time.	Just give us the green light.

2. Handle your reuses manually

   What we’ll do	Recommended?	Your effort
   You rebuild each project as a showcase (or decide to drop it), using the new asset form.	You want to clean up or reorganize your data marketplace, or some reuses are outdated.	A few minutes per showcase, depending on their complexity.

Let your CSM know which option you prefer so we can schedule the migration and keep your former reuses visible from day one.

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:

In the data marketplace experience, you can no longer hide columns directly in the table view of the dataset.

Previously, there were two settings:

1. The dataset security configuration, which makes the data available or not in the API (and thus in the front end), under Security.

2. The column visibility configuration in the Table view, which only affected the display in the front end, via Visualizations > Table.

This improves both data security and transparency, because previously there was the potential for confusion and potential data leaks if columns were hidden in the front end but still available through the API.

Now, visibility is controlled only via the dataset’s security settings.

What to do with your hidden columns?

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.