Overview of the Feature Request
It's possible to export metadata (Dublin Core, Croissant, DDI, etc.) for draft datasets via API as of IQSS/dataverse#11398 and it would be nice to have a button for this.
Here's a screenshot of the current UI. Note that for the never published draft, there is no "Export Metadata" button
What kind of user is the feature intended for?
Curator, Depositor, Guest
What inspired the request?
We added the ability to export metadata from drafts for the NeurIPS community (Slack thread). They have an annual conference and have been recommending Harvard Dataverse since 2025 to host datasets associated with that conference. They are required to upload a Croissant file with their conference submission and many would prefer to keep the dataset in draft state. As a workaround, I wrote a Python script at gdcc/dataverse-recipes#19 they can use to download Croissant from their draft dataset. However, it would be much more convenient for them have a button to click.
What existing behavior do you want changed?
Currently, the "Export Metadata" button does not appear on datasets that have never been published, that are still in draft. Adding a button would be great.
Any brand-new behavior do you want to add to Dataverse?
A new button, as explained above.
How to call the API
As described at https://guides.dataverse.org/en/6.10.1/api/native-api.html#export-metadata-of-a-dataset-in-various-formats the query parameter version=:draft should be passed. Authentication is required, of course.
export SERVER_URL=https://demo.dataverse.org
export PERSISTENT_IDENTIFIER=doi:10.5072/FK2/J8SJZB
export METADATA_FORMAT=ddi
export VERSION=:draft
export API_TOKEN=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
curl -H "X-Dataverse-key: $API_TOKEN" "$SERVER_URL/api/datasets/export?exporter=$METADATA_FORMAT&persistentId=$PERSISTENT_IDENTIFIER&version=$VERSION"
Design and scope considerations
At the frontend meeting on 2026-06-25, we decided that if we work on this issue in isolation, we can simply make the "Export Dataset" dropdown appear for drafts.
Note that drafts can be seen by someone with a Preview URL, but there is an open issue about how a Preview URL token can't be use to export drafts:
This behavior should be tested. If someone with a Preview URL can't export a draft, the "Export Metadata" button should not be shown.
We also said work on this issue could be combined with the following issue:
This would increase the scope, of course.
Therefore, the
Any open or closed issues related to this feature request?
Overview of the Feature Request
It's possible to export metadata (Dublin Core, Croissant, DDI, etc.) for draft datasets via API as of IQSS/dataverse#11398 and it would be nice to have a button for this.
Here's a screenshot of the current UI. Note that for the never published draft, there is no "Export Metadata" button
What kind of user is the feature intended for?
Curator, Depositor, Guest
What inspired the request?
We added the ability to export metadata from drafts for the NeurIPS community (Slack thread). They have an annual conference and have been recommending Harvard Dataverse since 2025 to host datasets associated with that conference. They are required to upload a Croissant file with their conference submission and many would prefer to keep the dataset in draft state. As a workaround, I wrote a Python script at gdcc/dataverse-recipes#19 they can use to download Croissant from their draft dataset. However, it would be much more convenient for them have a button to click.
What existing behavior do you want changed?
Currently, the "Export Metadata" button does not appear on datasets that have never been published, that are still in draft. Adding a button would be great.
Any brand-new behavior do you want to add to Dataverse?
A new button, as explained above.
How to call the API
As described at https://guides.dataverse.org/en/6.10.1/api/native-api.html#export-metadata-of-a-dataset-in-various-formats the query parameter
version=:draftshould be passed. Authentication is required, of course.Design and scope considerations
At the frontend meeting on 2026-06-25, we decided that if we work on this issue in isolation, we can simply make the "Export Dataset" dropdown appear for drafts.
Note that drafts can be seen by someone with a Preview URL, but there is an open issue about how a Preview URL token can't be use to export drafts:
This behavior should be tested. If someone with a Preview URL can't export a draft, the "Export Metadata" button should not be shown.
We also said work on this issue could be combined with the following issue:
This would increase the scope, of course.
Therefore, the
Any open or closed issues related to this feature request?