v0.3.2

Updated banner message link to use the /modern url

v0.3.1

Patch release - Added pagination to the Versions tabs on Dataset and File page.

v.0.3.0

[v0.3.0] -- 2026-04-24

This is the third preview of the new Dataverse frontend. This early version is still missing several features from the original Dataverse (JSF) UI and is intended primarily for testing and early review purposes. It’s not yet recommended for production installations.

This early release focuses on features used by Data Depositors, Data Seekers, and Data Downloaders.

Development will continue to fully replicate the current JSF UI functionalities and introduce new features.

This version has been tested with Dataverse 6.10.1🚀 and is using Dataverse Client Javascript 2.2.0.

Added

• Added the value entered by the user in the error messages for metadata field validation errors in EMAIL and URL type fields. For example, instead of showing “Point of Contact E-mail is not a valid email address.“, we now show “Point of Contact E-mail foo is not a valid email address.”
• Contact Owner button in File Page.
• Share button in File Page.
• Link Collection and Link Dataset features.
• Edit Terms Integration.
• File upload now shows the remaining storage quota when upload limits are available.
• With the addition of the new runtime configuration approach, we now support dynamic configuration for languages. If more than one language is configured, the Language Switcher will be shown in the header to allow users to change the language.
• Added Notifications tab in Account Page
• Added runtime configuration options for homepage branding and support link.
• Added an environment variable to docker-compose-dev.yml to hide the OIDC client used in the SPA from the JSF frontend: DATAVERSE_AUTH_OIDC_HIDDEN_JSF: 1
• Added a message note to the login page
• Download with terms of use and guestbook.
• Show terms modal before download when dataset has custom terms, a non-default license (not CC0 1.0), or a guestbook. Draft datasets and dataset editors bypass the modal.
• Layout: added a configurable homepage banner for announcements and important messages. (#787)

Changed

• Add pagination support to the Dataset Version Summaries and File Version Summaries use cases by introducing optional pagination object. #885
• Refactored pagination to use consistent CollectionItemsPaginationInfo object in getMyDataCollectionItems, instead of individual limit/selectedPage parameters.
• Use of the new sourceLastUpdateTime query parameter from update dataset and file metadata endpoints to support optimistic concurrency control during editing operations. See Edit Dataset Metadata and Updating File Metadata guides for more details.
• Changed the way we were handling DATE type metadata field validation to better match the backend validation and give users better error messages. For example, for an input like “foo AD”, we now show “Production Date is not a valid date. The AD year must be numeric.“. For an input like “99999 AD”, we now show “Production Date is not a valid date. The AD year cant be higher than 9999.“. For an input like “[-9999?], we now show “Production Date is not a valid date. The year in brackets cannot be negative.“, etc.
• The SPA now fetches the runtime configuration from config.js on each load, allowing configurations without rebuilding the app. We don't use .env variables at build time anymore.
• Renamed dataset template fetch/create use cases and DTOs to getTemplatesByCollectionId and CreateTemplateDTO for API alignment, and added new getTemplate and deleteTemplate use cases for retrieving a single template by ID and deleting templates.
• Added disclaimer text and custom popup text to Publish Dataset modal for better communication of the implications of publishing a dataset. The text can be configured through the runtime configuration.
• Dataset page Terms tab title now depends on permissions: users with dataset update permission see Terms and Guestbook, and read-only users see Terms.
• Avoided prop-drilling for collection repository, so used context to share epository instances.
• Added frontend version to the footer of the application, which is retrieved from the version field in package.json at build time.

Fixed

• Add word-break to items text to prevent layout issues when long descriptions without spaces are entered. (#839)
• Show toast notification when API token is copied to clipboard.
• Dataset versions: (1) file changes should be Access: Restricted instead of isResticted: true/false; (2) logic of View Detail button. (#879)
• File versions: (1) logic of linking to a file version; (2)If file not included, show text information "File not included in this version.". (#879)
• Dataset page publish flow now avoids rendering duplicate tab sets by making tabs skeleton and tabs content mutually exclusive.

v0.2.0

Dataverse Frontend 0.2.0

This is the second release of the new Dataverse frontend. This early version is still missing several key features from the original Dataverse (JSF) UI and is intended primarily for internal testing and early review purposes. It’s not yet recommended for production installations.

Development will continue to fully replicate the current JSF UI functionalities and introduce new features.

This version has been tested with Dataverse 6.8🚀 and is using Dataverse Client Javascript 2.1.0

Added

• Dataset Templates integration in the Create Dataset form (#820)
• Advanced Search UI replicating legacy JSF, with persistence of queries and facet filters (#770, #9993)
• External Search integration with selectable search service and first-load fetch behavior (#787)
• File Edit Tags with populated categories dropdown (#768, #785)
• DEMO environment option in deploy actions (#808)
• Metadata Export Dropdown in the metadata tab of Dataset and File pages (#823)
• External Tools integration — all tool types supported (Explore, Configure, Preview, and Query) in Dataset and File pages. Auxiliary Files support pending additional development (#815)
• Dataset page: citation downloads available in multiple formats with copy-to-clipboard (#795)
• Truncate long collection and dataset descriptions with expandable content (#790)

Changed

• Standardized Node.js to v22 across environments (Docker dev, CI, production)
• Upgrade Keycloak to 26.3.2; updated SPI and test realm JSON (#782, #826)
• UI polish: Files Table always shows action buttons (#817)

Fixed

• Guest user access: file info retrieval works on deaccessioned datasets (#766, #776)
• Collection filter queries with values containing “:” now parsed correctly (#813)
• File upload: corrected “You can only drop one file to replace” warning (#811)
• Create Collection form: prevent numeric-only aliases (#805)
• Improved URL handling and wrapping across the UI (#788)

Documentation

• Introduced CHANGELOG and updated related documents (#832)
• Added Environments section to README (#829)
• Expanded Keycloak deployment documentation with realm setup and SPI guidance (#759)
• Added “Featured Items” section to README (#844)

Security

• Fixed dependency vulnerabilities and updated versions — reduced npm audit issues from 100+ (12 critical, 33 high) to only 2 moderate (#840)

v0.1.0

Dataverse Frontend 0.1.0

This is the first release of the new Dataverse frontend. This early version is missing several key features from the original Dataverse (JSF) UI. It's intended for testing purposes and is not recommended for all installations.

Development will continue to fully replicate the current JSF UI functionalities and introduce new features.

This version has been tested with Dataverse 6.7🚀 and is using Dataverse Client Javascript 2.0.0