What steps does it take to reproduce the issue?
Find a dataset with many versions, like this:
Navigate to an older version, such as 1.3 and click "Export Metadata":
Download metadata in any format, such JSON.
Observe that the JSON does not match version 1.3. Rather, it matches the latest published version, which is 3.1. This is confusing to users, as reported in the following issues:
Always.
- Which page(s) does it occur on?
The dataset page.
There's a mismatch between the expected metadata (version 1.3) and the actual metadata (3.1).
- To whom does it occur (all users, curators, superusers)?
All users.
- What did you expect to happen?
Given the presence of the button, I expect the correct metadata to be downloaded.
Which version of Dataverse Frontend are you using?
d8d1344
Proposed solution
As discussed in the frontend meeting on 2026-06-24, we think we should simply hide the "Export Metadata" button when metadata for the version in question is not available. I checked with @thisisbillie and she said this sounds reasonable.
Design and scope considerations
As discussed in the frontend meeting on 2026-06-24, a fix for this issue could be done in the same pull request that fixes the following issue:
Any related open or closed issues to this bug report?
What steps does it take to reproduce the issue?
Find a dataset with many versions, like this:
Navigate to an older version, such as 1.3 and click "Export Metadata":
Download metadata in any format, such JSON.
Observe that the JSON does not match version 1.3. Rather, it matches the latest published version, which is 3.1. This is confusing to users, as reported in the following issues:
Suggestion: Clarify Export Metadata behaviour when viewing older dataset versions dataverse#12461
As a researcher, I want the metadata export to be available only if it matches the dataset version that's available for download so that I don't get a mismatch dataverse#4372
When does this issue occur?
Always.
The dataset page.
There's a mismatch between the expected metadata (version 1.3) and the actual metadata (3.1).
All users.
Given the presence of the button, I expect the correct metadata to be downloaded.
Which version of Dataverse Frontend are you using?
d8d1344
Proposed solution
As discussed in the frontend meeting on 2026-06-24, we think we should simply hide the "Export Metadata" button when metadata for the version in question is not available. I checked with @thisisbillie and she said this sounds reasonable.
Design and scope considerations
As discussed in the frontend meeting on 2026-06-24, a fix for this issue could be done in the same pull request that fixes the following issue:
Any related open or closed issues to this bug report?