Dataset catalog exports in the new experience

hi for our Dataportal, this export was important, please bring it back as a customizable element for the left side of the catalog

Hi ​@Christian Trachsel , thanks for the feedback !

A couple of things that would help us understand your need better:

• Why was it important for your team specifically? Is it a compliance/reporting need, a way to feed the catalog into another system, or something users ask for ad hoc?
• How do your users actually use the exported catalog? Do they open it in Excel to browse offline, pull it into a BI tool, share it with people who don't have portal access, or something else?
• What do you mean by "customizable"? A few different things could fit that word — happy to build the right guidance once I know which:
  • Choosing which format appears (CSV only vs. CSV/Excel/JSON)?
  • Choosing where it sits in the left panel (above/below facets, sticky vs. scroll)?
  • Exporting the full catalog vs. only the currently filtered/refined view (e.g. after applying facets)?
  • Letting an admin toggle the button on/off per portal, without a dev deploying code each time?

In the meantime — since the export is now API-driven rather than a built-in UI button, you can absolutely recreate it yourself as a small custom HTML/CSS block on the left side of the catalog page. Here's the pattern:

html

<div class="catalog-export-buttons">
  <a href="/api/explore/v2.1/catalog/exports/csv" class="export-btn export-btn--csv" target="_blank">
    Export CSV
  </a>
  <a href="/api/explore/v2.1/catalog/exports/xlsx" class="export-btn export-btn--xlsx" target="_blank">
    Export Excel
  </a>
  <a href="/api/explore/v2.1/catalog/exports/json" class="export-btn export-btn--json" target="_blank">
    Export JSON
  </a>
</div>

css

.catalog-export-buttons {
  display: flex;
  flex-direction: column;
  gap: 8px;
  margin: 16px 0;
}
.export-btn {
  display: inline-block;
  padding: 8px 14px;
  border-radius: 6px;
  border: 1px solid #3355FF;
  color: #3355FF;
  text-decoration: none;
  font-size: 14px;
  text-align: center;
  transition: background 0.15s ease;
}
.export-btn:hover {
  background: #3355FF;
  color: #FFFFFF;
}

A few notes on making this robust:

• These endpoints are relative to your domain, so on a live portal they resolve to https://yourdomain.opendatasoft.com/api/explore/v2.1/catalog/exports/{format} , swap in your actual domain if you're hardcoding the block outside the portal's own templating.
• If what you actually want is to export the filtered catalog (only datasets matching whatever facets/search the visitor currently has applied), you can append ODSQL query parameters to the endpoint, e.g. ?where=... or ?refine=..., mirroring whatever refinement is active on the page. That's the more complex "customizable" case, let me know if that's the one you mean and I can put together a fuller how-to (likely needs a bit of JS to read the current facet state and build the URL dynamically, rather than a static link).
• No authentication is needed for exporting open datasets this way; if your Dataportal also has private/restricted datasets in the mix, exports will only include what the visitor is authorized to see, so the button will behave correctly for both anonymous and logged-in users.

Let us know how you'd like this to behave and we can help refine it !