From c66a2b41581f7a4408ad34d0eae97b6484400124 Mon Sep 17 00:00:00 2001 From: Philip Durbin Date: Tue, 16 Jun 2026 14:13:44 -0400 Subject: [PATCH 01/56] start 6.11 release notes #12283 --- doc/release-notes/6.11-release-notes.md | 84 +++++++++++++++++++++++++ 1 file changed, 84 insertions(+) create mode 100644 doc/release-notes/6.11-release-notes.md diff --git a/doc/release-notes/6.11-release-notes.md b/doc/release-notes/6.11-release-notes.md new file mode 100644 index 00000000000..fa9d8e6bc3c --- /dev/null +++ b/doc/release-notes/6.11-release-notes.md @@ -0,0 +1,84 @@ +# Dataverse 6.11 + +Please note: To read these instructions in full, please go to https://github.com/IQSS/dataverse/releases/tag/v6.11 rather than the [list of releases](https://github.com/IQSS/dataverse/releases), which will cut them off. + +This release brings new features, enhancements, and bug fixes to Dataverse. Thank you to all of the community members who contributed code, suggestions, bug reports, and other assistance across the project! + +## Release Highlights + +Highlights for Dataverse 6.11 include: + +- New and improved APIs +- Bug fixes + +## Features Added + +These are features that weren't already mentioned under "highlights" above. + +## API Updates + +## Security Updates + +This release contains important security updates. If you are not receiving security notices, please sign up by following [the steps](https://guides.dataverse.org/en/latest/installation/config.html#ongoing-security-of-your-installation) in the guides. + +## Backward Incompatible Changes + +Generally speaking, see the [API Changelog](https://guides.dataverse.org/en/latest/api/changelog.html) for a list of backward-incompatible API changes. + +## End-Of-Life (EOL) Announcements + +### PostgreSQL 13 Reached EOL on 13 November 2025 + +We mentioned this in the Dataverse [6.6](https://github.com/IQSS/dataverse/releases/tag/v6.6), [6.8](https://github.com/IQSS/dataverse/releases/tag/v6.8), [6.9](https://github.com/IQSS/dataverse/releases/tag/v6.9), and [6.10](https://github.com/IQSS/dataverse/releases/tag/v6.10) release notes, but as a reminder, according to https://www.postgresql.org/support/versioning/ PostgreSQL 13 reached EOL on 13 November 2025. As stated in the [Installation Guide](https://guides.dataverse.org/en/6.11/installation/prerequisites.html#postgresql), we recommend running PostgreSQL 16 since it is the version we test with in our continuous integration ([since](https://github.com/gdcc/dataverse-ansible/commit/8ebbd84ad2cf3903b8f995f0d34578250f4223ff) February 2025). The [Dataverse 5.4 release notes](https://github.com/IQSS/dataverse/releases/tag/v5.4) explained the upgrade process from 9 to 13 (e.g. pg_dumpall, etc.) and the steps will be similar. If you have any problems, please feel free to reach out (see "getting help" in these release notes). + +## Notes for Dataverse Installation Administrators + +## New Settings + +### New JVM Options (MicroProfile Config Settings) + +### New Database Settings + +## Complete List of Changes + +For the complete list of code changes in this release, see the [6.11 milestone](https://github.com/IQSS/dataverse/issues?q=milestone%3A6.11+is%3Aclosed) in GitHub. + +## Getting Help + +For help with upgrading, installing, or general questions please see [getting help](https://guides.dataverse.org/en/latest/installation/intro.html#getting-help) in the Installation Guide. + +## Installation + +If this is a new installation, please follow our [Installation Guide](https://guides.dataverse.org/en/latest/installation/). Please don't be shy about [asking for help](https://guides.dataverse.org/en/latest/installation/intro.html#getting-help) if you need it! + +Once you are in production, we would be delighted to update our [map of Dataverse installations around the world](https://dataverse.org/installations) to include yours! Please [create an issue](https://github.com/IQSS/dataverse-installations/issues) or email us at support@dataverse.org to join the club! + +You are also very welcome to join the [Global Dataverse Community Consortium](https://www.gdcc.io) (GDCC). + +## Upgrade Instructions + +Upgrading requires a maintenance window and downtime. Please plan accordingly, create backups of your database, etc. + +Note: These instructions assume that you are upgrading from the immediate previous version. That is to say, you've already upgraded through all the 6.x releases and are now running Dataverse 6.10. See [tags on GitHub](https://github.com/IQSS/dataverse/tags) for a list of versions. If you are running an earlier version, the only supported way to upgrade is to progress through the upgrades to all the releases in between before attempting the upgrade to this version. + +If you are running Payara as a non-root user (and you should be!), **remember not to execute the commands below as root**. By default, Payara runs as the `dataverse` user. In the commands below, we use sudo to run the commands as a non-root user. + +Also, we assume that Payara 6 is installed in `/usr/local/payara6`. If not, adjust as needed. + +1. Deploy the Dataverse 6.10 war file. + + `wget https://github.com/IQSS/dataverse/releases/download/v6.10/dataverse-6.11.war` + + `sudo -u dataverse /usr/local/payara7/bin/asadmin deploy dataverse-6.11.war` + +1. Check that you get a version number from Dataverse. + + This is just a sanity check that Dataverse has been deployed properly. + + `curl http://localhost:8080/api/info/version` + +1. For installations with internationalization or text customizations: + + Please remember to update translations via [Dataverse language packs](https://github.com/GlobalDataverseCommunityConsortium/dataverse-language-packs). + + If you have text customizations you can get the latest English files from . From 4c6cb597db0f9a574d8af160066ca94a7e20e49d Mon Sep 17 00:00:00 2001 From: Philip Durbin Date: Tue, 16 Jun 2026 14:22:49 -0400 Subject: [PATCH 02/56] CORS filter fix --- doc/release-notes/6.11-release-notes.md | 12 ++++++++++++ doc/release-notes/cors-filter-fix.md | 9 --------- 2 files changed, 12 insertions(+), 9 deletions(-) delete mode 100644 doc/release-notes/cors-filter-fix.md diff --git a/doc/release-notes/6.11-release-notes.md b/doc/release-notes/6.11-release-notes.md index fa9d8e6bc3c..864c5d2a0be 100644 --- a/doc/release-notes/6.11-release-notes.md +++ b/doc/release-notes/6.11-release-notes.md @@ -31,14 +31,26 @@ Generally speaking, see the [API Changelog](https://guides.dataverse.org/en/late We mentioned this in the Dataverse [6.6](https://github.com/IQSS/dataverse/releases/tag/v6.6), [6.8](https://github.com/IQSS/dataverse/releases/tag/v6.8), [6.9](https://github.com/IQSS/dataverse/releases/tag/v6.9), and [6.10](https://github.com/IQSS/dataverse/releases/tag/v6.10) release notes, but as a reminder, according to https://www.postgresql.org/support/versioning/ PostgreSQL 13 reached EOL on 13 November 2025. As stated in the [Installation Guide](https://guides.dataverse.org/en/6.11/installation/prerequisites.html#postgresql), we recommend running PostgreSQL 16 since it is the version we test with in our continuous integration ([since](https://github.com/gdcc/dataverse-ansible/commit/8ebbd84ad2cf3903b8f995f0d34578250f4223ff) February 2025). The [Dataverse 5.4 release notes](https://github.com/IQSS/dataverse/releases/tag/v5.4) explained the upgrade process from 9 to 13 (e.g. pg_dumpall, etc.) and the steps will be similar. If you have any problems, please feel free to reach out (see "getting help" in these release notes). +## Documentation Changes + +- [The Big Data Support](https://guides.dataverse.org/en/6.11/installation/big-data-support.html) page has been moved from the Developer Guide to the Installation Guide. See #12151. + ## Notes for Dataverse Installation Administrators +### CORS Filter Fix and Docs + +We fixed an inconsistency where the `CorsFilter` was not always being invoked when accessing `/api/...` endpoints, preventing these endpoints from being used from webapps even when CORS was properly configured. In addition, the [documentation](https://guides.dataverse.org/en/6.11/installation/config.html#cross-origin-resource-sharing-cors) related to how certain Dataverse features depend on proper CORS configuration has been extended and improved. See #12151 and #12161. + ## New Settings ### New JVM Options (MicroProfile Config Settings) ### New Database Settings +## Updates for Documentation Writers + +A new dependency called "sphinx-reredirects" has been added. Please re-run the `pip install -r requirements.txt` setup [step](https://guides.dataverse.org/en/6.11/contributor/documentation.html#building-the-guides-with-sphinx) to update your environment. Otherwise you might see an error like `Could not import extension sphinx_reredirects`. + ## Complete List of Changes For the complete list of code changes in this release, see the [6.11 milestone](https://github.com/IQSS/dataverse/issues?q=milestone%3A6.11+is%3Aclosed) in GitHub. diff --git a/doc/release-notes/cors-filter-fix.md b/doc/release-notes/cors-filter-fix.md deleted file mode 100644 index 6acb665fe26..00000000000 --- a/doc/release-notes/cors-filter-fix.md +++ /dev/null @@ -1,9 +0,0 @@ -## CORS Filter Fix - -Fixed an inconsistency where the `CorsFilter` was not always being invoked when accessing `/api/...` endpoints, preventing these endpoints from being used from webapps even when CORS was properly configured. See #12151. - -In addition, the documentation around the Dataverse features regarding CORS has been extended and improved. The "Big Data" page has been moved from the development section to the installation section of the guides. See #12161. - -## Updates for Documentation Writers - -A new dependency called "sphinx-reredirects" has been added. Please re-run the `pip install -r requirements.txt` setup [step](https://dataverse-guide--12151.org.readthedocs.build/en/12151/contributor/documentation.html#building-the-guides-with-sphinx) to update your environment. Otherwise you might see an error like `Could not import extension sphinx_reredirects`. From 10f18afc1a62febfce788027436435605f815a68 Mon Sep 17 00:00:00 2001 From: Philip Durbin Date: Tue, 16 Jun 2026 14:39:33 -0400 Subject: [PATCH 03/56] Show Historical File Access Requests --- doc/release-notes/6.11-release-notes.md | 7 +++++++ .../8013-history-of-access-request-available-via-api.md | 8 -------- 2 files changed, 7 insertions(+), 8 deletions(-) delete mode 100644 doc/release-notes/8013-history-of-access-request-available-via-api.md diff --git a/doc/release-notes/6.11-release-notes.md b/doc/release-notes/6.11-release-notes.md index 864c5d2a0be..39c9ebbeec2 100644 --- a/doc/release-notes/6.11-release-notes.md +++ b/doc/release-notes/6.11-release-notes.md @@ -15,8 +15,15 @@ Highlights for Dataverse 6.11 include: These are features that weren't already mentioned under "highlights" above. +### Show Historical File Access Requests + +A new button called "Show Historical Requests" checkbox has been added to the permissions page for a data file. Checking the box will show the number of times access has been granted or denied by user. See #8013 and #12012. + + ## API Updates +- The `/datafile/{id}/listRequests` API has been extended to show request history. See [the guides](https://guides.dataverse.org/en/6.11/api/dataaccess.html#list-file-access-requests), #8013 and #12012. + ## Security Updates This release contains important security updates. If you are not receiving security notices, please sign up by following [the steps](https://guides.dataverse.org/en/latest/installation/config.html#ongoing-security-of-your-installation) in the guides. diff --git a/doc/release-notes/8013-history-of-access-request-available-via-api.md b/doc/release-notes/8013-history-of-access-request-available-via-api.md deleted file mode 100644 index 14ebe52f9f7..00000000000 --- a/doc/release-notes/8013-history-of-access-request-available-via-api.md +++ /dev/null @@ -1,8 +0,0 @@ -### Feature: Extend List File Access Requests API ### - -Added ability to get access request history via the `/datafile/{id}/listRequests` API. The API returns a list of users/groups where the request for access is waiting for an accept or reject. Already accepted or rejected requests are not returned. - -By adding the flag 'includeHistory=true' all of the requests will be returned. Pagination is also implemented in this feature. Adding a start page parameter and max list size (`&start=0` and `&per_page=20`) can limit the amount of data being returned. - -See https://guides.dataverse.org/en/latest/api/dataaccess.html#list-file-access-requests - From 210d89c3f1e0842c883ce33b3dd8395220243bd0 Mon Sep 17 00:00:00 2001 From: Philip Durbin Date: Tue, 16 Jun 2026 14:58:28 -0400 Subject: [PATCH 04/56] show orig file format for ingested files --- doc/release-notes/6.11-release-notes.md | 5 ++++- doc/release-notes/7956-show_original_file_format.md | 2 -- 2 files changed, 4 insertions(+), 3 deletions(-) delete mode 100644 doc/release-notes/7956-show_original_file_format.md diff --git a/doc/release-notes/6.11-release-notes.md b/doc/release-notes/6.11-release-notes.md index 39c9ebbeec2..9026645e037 100644 --- a/doc/release-notes/6.11-release-notes.md +++ b/doc/release-notes/6.11-release-notes.md @@ -15,11 +15,14 @@ Highlights for Dataverse 6.11 include: These are features that weren't already mentioned under "highlights" above. +### Original Tabular File Format Shown (Rather Than .tab) + +In previous releases of Dataverse, the file, dataset, and collection pages showed the .tab version of tabular files (a plain text preservation-friendly copy). This has been changed to show the original format instead (e.g. Excel, Stata, etc.). The .tab version is still available from the download menu. See #7956 and #12145. + ### Show Historical File Access Requests A new button called "Show Historical Requests" checkbox has been added to the permissions page for a data file. Checking the box will show the number of times access has been granted or denied by user. See #8013 and #12012. - ## API Updates - The `/datafile/{id}/listRequests` API has been extended to show request history. See [the guides](https://guides.dataverse.org/en/6.11/api/dataaccess.html#list-file-access-requests), #8013 and #12012. diff --git a/doc/release-notes/7956-show_original_file_format.md b/doc/release-notes/7956-show_original_file_format.md deleted file mode 100644 index eea80f58fc4..00000000000 --- a/doc/release-notes/7956-show_original_file_format.md +++ /dev/null @@ -1,2 +0,0 @@ -This release changes the display behavior of the file, dataset and collection ("dataverse") pages for tabular files. They will show the original file name and information, and will allow editing of the original file name. The ingested *.tab version is still available from the download menu. - From 114a2eec9799b9a0338f79f8963c7d0f4a3fd291 Mon Sep 17 00:00:00 2001 From: Philip Durbin Date: Tue, 16 Jun 2026 16:26:22 -0400 Subject: [PATCH 05/56] not valid, does not comply --- .../360-modify-notvalid-deaccession-reason.md | 16 ---------------- doc/release-notes/6.11-release-notes.md | 16 ++++++++++++++-- 2 files changed, 14 insertions(+), 18 deletions(-) delete mode 100644 doc/release-notes/360-modify-notvalid-deaccession-reason.md diff --git a/doc/release-notes/360-modify-notvalid-deaccession-reason.md b/doc/release-notes/360-modify-notvalid-deaccession-reason.md deleted file mode 100644 index fcfba4dfcd0..00000000000 --- a/doc/release-notes/360-modify-notvalid-deaccession-reason.md +++ /dev/null @@ -1,16 +0,0 @@ -# Language change for file.deaccessionDialog.reason.selectItem.notValid - -"Not a valid dataset." is being changed to "Not valid. This dataset does not comply with repository policies." -This is the default English language version. For installations using customized languages, replacing the Bundle.properties file, please follow these manual instructions to make this modification, if desired. - -Make the change to the Bundle_##.properties file with the new verbiage. Either locally or as an update to [dataverse-language-packs Repo](https://github.com/GlobalDataverseCommunityConsortium/dataverse-language-packs/tree/develop) - -The SQL statements to modify the datasets is: - -- `UPDATE dvobject SET indextime=null WHERE id in (SELECT dataset_id FROM datasetversion WHERE deaccessionnote='Not a valid dataset.');` - -- `UPDATE datasetversion SET deaccessionnote='Not valid. This dataset does not comply with repository policies.' WHERE deaccessionnote='Not a valid dataset.';` - -Once the database is updated the Solr indexes need to be rebuilt using the following Admin API: - -- `curl http://localhost:8080/api/admin/index` diff --git a/doc/release-notes/6.11-release-notes.md b/doc/release-notes/6.11-release-notes.md index 9026645e037..8c007af04c6 100644 --- a/doc/release-notes/6.11-release-notes.md +++ b/doc/release-notes/6.11-release-notes.md @@ -23,6 +23,10 @@ In previous releases of Dataverse, the file, dataset, and collection pages showe A new button called "Show Historical Requests" checkbox has been added to the permissions page for a data file. Checking the box will show the number of times access has been granted or denied by user. See #8013 and #12012. +## Other Changes + +- The deaccession reason "Not a valid dataset." has been changed to "Not valid. This dataset does not comply with repository policies." See the Bundle.properties key file.deaccessionDialog.reason.selectItem.notValid and #11985. + ## API Updates - The `/datafile/{id}/listRequests` API has been extended to show request history. See [the guides](https://guides.dataverse.org/en/6.11/api/dataaccess.html#list-file-access-requests), #8013 and #12012. @@ -87,9 +91,9 @@ If you are running Payara as a non-root user (and you should be!), **remember no Also, we assume that Payara 6 is installed in `/usr/local/payara6`. If not, adjust as needed. -1. Deploy the Dataverse 6.10 war file. +1. Deploy the Dataverse 6.11 war file. - `wget https://github.com/IQSS/dataverse/releases/download/v6.10/dataverse-6.11.war` + `wget https://github.com/IQSS/dataverse/releases/download/v6.11/dataverse-6.11.war` `sudo -u dataverse /usr/local/payara7/bin/asadmin deploy dataverse-6.11.war` @@ -104,3 +108,11 @@ Also, we assume that Payara 6 is installed in `/usr/local/payara6`. If not, adju Please remember to update translations via [Dataverse language packs](https://github.com/GlobalDataverseCommunityConsortium/dataverse-language-packs). If you have text customizations you can get the latest English files from . + + Note that deaccessionDialog.reason.selectItem.notValid was updated. See #11985. + +1. Reindex Solr + + Solr needs to be reindexed because of the change to deaccessionDialog.reason.selectItem.notValid in Bundle.properties (#11985). + + `curl http://localhost:8080/api/admin/index` \ No newline at end of file From 5ec62b9a2da2ef52faecd1da0b7c9c21372e6ed2 Mon Sep 17 00:00:00 2001 From: Philip Durbin Date: Tue, 16 Jun 2026 16:34:05 -0400 Subject: [PATCH 06/56] fast redeploy --- .../10156-fast-redeploy-scripts.md | 42 ------------------- doc/release-notes/6.11-release-notes.md | 4 ++ 2 files changed, 4 insertions(+), 42 deletions(-) delete mode 100644 doc/release-notes/10156-fast-redeploy-scripts.md diff --git a/doc/release-notes/10156-fast-redeploy-scripts.md b/doc/release-notes/10156-fast-redeploy-scripts.md deleted file mode 100644 index 2d53ba13ab8..00000000000 --- a/doc/release-notes/10156-fast-redeploy-scripts.md +++ /dev/null @@ -1,42 +0,0 @@ -## Fast Redeploy Scripts for Container-Based Development - -Three new shell scripts in `scripts/dev/` enable fast iterative development for Dataverse contributors working with the container-based development environment: - -- **`dev-start-frd.sh`**: One-time setup (full build → exploded WAR → start containers) -- **`dev-frd.sh`**: Incremental recompile + redeploy (~12s vs. ~54s for traditional full rebuild workflow, 4.5x faster) -- **`dev-down-frd.sh`**: Clean shutdown of dev environment - -This command-line workflow provides a fast feedback loop for developers who prefer CLI-based development or use lightweight editors like VS Code or Vim, complementing the existing IDE-based hot reload options (IntelliJ Ultimate, NetBeans). - -### New Files - -- **`docker-compose.override.yml`**: Increases memory limits to 8GB (from the 2GB limit set for GitHub Actions CI) for local development. Automatically used by the fast-redeploy scripts. - -### Key Features - -- No infrastructure changes (works with existing docker-compose-dev.yml) -- Optional workflow (doesn't affect other development approaches) -- Completes in ~12 seconds instead of ~54 seconds after code changes (4.5x faster) - -**Note:** Performance timings may vary depending on your hardware configuration. - -### Typical Workflow - -```bash -# One-time setup -./scripts/dev/dev-start-frd.sh - -# Make code changes... - -# Fast redeploy -./scripts/dev/dev-frd.sh - -# Repeat as needed - -# When finished -./scripts/dev/dev-down-frd.sh -``` - -### Documentation - -See the [Fast Redeploy (Command-Line)](https://guides.dataverse.org/en/latest/container/dev-usage.html#dev-fast-redeploy) section in the Container Guide for complete usage instructions and limitations. diff --git a/doc/release-notes/6.11-release-notes.md b/doc/release-notes/6.11-release-notes.md index 8c007af04c6..e7a2353e3ea 100644 --- a/doc/release-notes/6.11-release-notes.md +++ b/doc/release-notes/6.11-release-notes.md @@ -65,6 +65,10 @@ We fixed an inconsistency where the `CorsFilter` was not always being invoked wh A new dependency called "sphinx-reredirects" has been added. Please re-run the `pip install -r requirements.txt` setup [step](https://guides.dataverse.org/en/6.11/contributor/documentation.html#building-the-guides-with-sphinx) to update your environment. Otherwise you might see an error like `Could not import extension sphinx_reredirects`. +## Updates for Developers + +- New "fast redeploy" scripts have been added for the backend. See [the guides](https://guides.dataverse.org/en/6.11/container/dev-usage.html#fast-redeploy-command-line), #10156, and [Zulip](https://dataverse.zulipchat.com/#narrow/channel/379673-dev/topic/fast.20redeploy.20with.20docker.20compose/near/553715282). Please note that this solution is being further improved in #12467. + ## Complete List of Changes For the complete list of code changes in this release, see the [6.11 milestone](https://github.com/IQSS/dataverse/issues?q=milestone%3A6.11+is%3Aclosed) in GitHub. From 86a1e4b84e4bbe581bc627bf75eb202ef57a4387 Mon Sep 17 00:00:00 2001 From: Philip Durbin Date: Tue, 16 Jun 2026 16:53:54 -0400 Subject: [PATCH 07/56] new geo fields --- doc/release-notes/10398-geospatial-block.md | 22 --------- doc/release-notes/6.11-release-notes.md | 51 ++++++++++++++++++--- 2 files changed, 45 insertions(+), 28 deletions(-) delete mode 100644 doc/release-notes/10398-geospatial-block.md diff --git a/doc/release-notes/10398-geospatial-block.md b/doc/release-notes/10398-geospatial-block.md deleted file mode 100644 index 50eea141883..00000000000 --- a/doc/release-notes/10398-geospatial-block.md +++ /dev/null @@ -1,22 +0,0 @@ -## New Expanded Geospatial Metadata Block - -This release introduces a major enhancement to geospatial data support with the addition of an expanded Geospatial Metadata Block, designed to improve how researchers describe, share, and discover geospatial datasets. - -This new expanded metadata block aligns with the international ISO 19115 standard for describing geographic data. - -- Includes 22 new metadata fields to provide more detailed and standardized descriptions of geospatial data (e.g. vector, raster, mixed or multi-format geospatial collections) -- Incorporates and extends current metadata elements (Geographic Coverage and Geographic Bounding Box) -- Ensures backward compatibility while significantly improving metadata description capabilities. - -See [the guides](https://dataverse-guide--11507.org.readthedocs.build/en/11507/user/appendix.html#supported-metadata), #10398, and #11507. - -## Upgrade Instructions - -### Update geospatial metadata block in existing installation (PR #11507) - -.. code-block:: javascript - - curl http://localhost:8080/api/admin/datasetfield/load -H "Content-type: text/tab-separated-values" -X POST --upload-file geospatial.tsv - curl "http://localhost:8080/api/admin/index/solr/schema" > new.xml - ./dataverse/conf/solr/update-fields.sh /usr/local/solr/solr-9.8.0/server/solr/collection1/conf/schema.xml new.xml - curl "http://localhost:8983/solr/admin/cores?action=RELOAD&core=collection1" diff --git a/doc/release-notes/6.11-release-notes.md b/doc/release-notes/6.11-release-notes.md index e7a2353e3ea..4ce628fb60b 100644 --- a/doc/release-notes/6.11-release-notes.md +++ b/doc/release-notes/6.11-release-notes.md @@ -8,9 +8,22 @@ This release brings new features, enhancements, and bug fixes to Dataverse. Than Highlights for Dataverse 6.11 include: +- New expanded geospatial metadata block - New and improved APIs - Bug fixes +### New Expanded Geospatial Metadata Block + +This release introduces a major enhancement to geospatial data support with the addition of an expanded Geospatial Metadata Block, designed to improve how researchers describe, share, and discover geospatial datasets. + +This new expanded metadata block aligns with the international ISO 19115 standard for describing geographic data. + +- Includes 22 new metadata fields to provide more detailed and standardized descriptions of geospatial data (e.g. vector, raster, mixed or multi-format geospatial collections) +- Incorporates and extends current metadata elements (Geographic Coverage and Geographic Bounding Box) +- Ensures backward compatibility while significantly improving metadata description capabilities. + +See [the guides](https://guides.dataverse.org/en/6.11/user/appendix.html#supported-metadata), #10398, and #11507. + ## Features Added These are features that weren't already mentioned under "highlights" above. @@ -93,7 +106,7 @@ Note: These instructions assume that you are upgrading from the immediate previo If you are running Payara as a non-root user (and you should be!), **remember not to execute the commands below as root**. By default, Payara runs as the `dataverse` user. In the commands below, we use sudo to run the commands as a non-root user. -Also, we assume that Payara 6 is installed in `/usr/local/payara6`. If not, adjust as needed. +Also, we assume that Payara is installed in `/usr/local/payara7`. If not, adjust as needed. 1. Deploy the Dataverse 6.11 war file. @@ -107,16 +120,42 @@ Also, we assume that Payara 6 is installed in `/usr/local/payara6`. If not, adju `curl http://localhost:8080/api/info/version` -1. For installations with internationalization or text customizations: +1. Update the geospatial metadata block. - Please remember to update translations via [Dataverse language packs](https://github.com/GlobalDataverseCommunityConsortium/dataverse-language-packs). + `wget https://raw.githubusercontent.com/IQSS/dataverse/refs/tags/v6.11/scripts/api/data/metadatablocks/geospatial.tsv` - If you have text customizations you can get the latest English files from . + `curl http://localhost:8080/api/admin/datasetfield/load -H "Content-type: text/tab-separated-values" -X POST --upload-file geospatial.tsv` + +1. Update Solr schema + + Due to changes in the Solr schema (the addition of geospatial fields), updating the Solr schema and reindexing is required. + + Back up your current Solr schema. + + `cp /usr/local/solr/solr-9.8.0/server/solr/collection1/conf/schema.xml /usr/local/solr/solr-9.8.0/server/solr/collection1/conf/schema.xml.orig` - Note that deaccessionDialog.reason.selectItem.notValid was updated. See #11985. + Run the `update-fields.sh` script that we supply. The example below shows the default path for a non-Docker installation, but adjust the path as necessary. Docker-based installations use this directory: `solr/data/data/collection1/conf/schema.xml`. + + `wget https://raw.githubusercontent.com/IQSS/dataverse/v6.11/conf/solr/update-fields.sh` + + `chmod +x update-fields.sh` + + `curl "http://localhost:8080/api/admin/index/solr/schema" | ./update-fields.sh /usr/local/solr/solr-9.8.0/server/solr/collection1/conf/schema.xml` + + Reload the Solr core + + `curl "http://localhost:8983/solr/admin/cores?action=RELOAD&core=collection1"` 1. Reindex Solr Solr needs to be reindexed because of the change to deaccessionDialog.reason.selectItem.notValid in Bundle.properties (#11985). - `curl http://localhost:8080/api/admin/index` \ No newline at end of file + `curl http://localhost:8080/api/admin/index` + +1. For installations with internationalization or text customizations: + + Please remember to update translations via [Dataverse language packs](https://github.com/GlobalDataverseCommunityConsortium/dataverse-language-packs). + + If you have text customizations you can get the latest English files from . + + Note that deaccessionDialog.reason.selectItem.notValid was updated. See #11985. \ No newline at end of file From 97170b3ca38b8e6aee10e6bd18d4ebc216eb79d2 Mon Sep 17 00:00:00 2001 From: Philip Durbin Date: Wed, 17 Jun 2026 09:17:46 -0400 Subject: [PATCH 08/56] mydata empty --- doc/release-notes/11447-mydata-retrieve-empty-result-set.md | 3 --- doc/release-notes/6.11-release-notes.md | 2 ++ 2 files changed, 2 insertions(+), 3 deletions(-) delete mode 100644 doc/release-notes/11447-mydata-retrieve-empty-result-set.md diff --git a/doc/release-notes/11447-mydata-retrieve-empty-result-set.md b/doc/release-notes/11447-mydata-retrieve-empty-result-set.md deleted file mode 100644 index 949da5780c7..00000000000 --- a/doc/release-notes/11447-mydata-retrieve-empty-result-set.md +++ /dev/null @@ -1,3 +0,0 @@ -## Feature MyData API Endpoint - don't return error for empty result set - -**GET /api/mydata/retrieve** will now return "data" block with 0 results if the result set is empty, Also, the "success" status will be returned as 'true' and the message giving context as to the 0 results will be returned in "message" instead of "error_message". All true errors will still return "success":false and "error_message":"Some error" with no "data" block. diff --git a/doc/release-notes/6.11-release-notes.md b/doc/release-notes/6.11-release-notes.md index 4ce628fb60b..1f847dfa24e 100644 --- a/doc/release-notes/6.11-release-notes.md +++ b/doc/release-notes/6.11-release-notes.md @@ -52,6 +52,8 @@ This release contains important security updates. If you are not receiving secur Generally speaking, see the [API Changelog](https://guides.dataverse.org/en/latest/api/changelog.html) for a list of backward-incompatible API changes. +- The GET /api/mydata/retrieve, if the search returns no data, now includes the "data" block with 0 results. The message that was returned in "error_message" will be returned in "message" and the "success" will be `true`. All other errors will continue to reply with "success":false and the error message in "error_message". See #11447 and #12256. + ## End-Of-Life (EOL) Announcements ### PostgreSQL 13 Reached EOL on 13 November 2025 From 964a950c965fda1b7da2d20437c03fd6730adcff Mon Sep 17 00:00:00 2001 From: Philip Durbin Date: Wed, 17 Jun 2026 09:21:08 -0400 Subject: [PATCH 09/56] thumbnail search bug --- doc/release-notes/11588-search-api-doesnt-return-image-url.md | 4 ---- doc/release-notes/6.11-release-notes.md | 4 ++++ 2 files changed, 4 insertions(+), 4 deletions(-) delete mode 100644 doc/release-notes/11588-search-api-doesnt-return-image-url.md diff --git a/doc/release-notes/11588-search-api-doesnt-return-image-url.md b/doc/release-notes/11588-search-api-doesnt-return-image-url.md deleted file mode 100644 index 6d0a474281c..00000000000 --- a/doc/release-notes/11588-search-api-doesnt-return-image-url.md +++ /dev/null @@ -1,4 +0,0 @@ -## BUG ## -Search API doesn't return image_url after newly created dataset is published. - -The Dataset thumbnail will be created automatically when a Dataset is published under the following conditions: The Dataset has no existing thumbnail; The Dataset has image files that can be converted to a thumbnail; The Feature Flag "disable-dataset-thumbnail-autoselect" is not enabled; diff --git a/doc/release-notes/6.11-release-notes.md b/doc/release-notes/6.11-release-notes.md index 1f847dfa24e..4625eb7a71d 100644 --- a/doc/release-notes/6.11-release-notes.md +++ b/doc/release-notes/6.11-release-notes.md @@ -36,6 +36,10 @@ In previous releases of Dataverse, the file, dataset, and collection pages showe A new button called "Show Historical Requests" checkbox has been added to the permissions page for a data file. Checking the box will show the number of times access has been granted or denied by user. See #8013 and #12012. +## Bug Fixes + +- The bug "Search API doesn't return image_url after newly created dataset is published" was fixed in the following manner. The dataset thumbnail will be created automatically when a dataset is published under the following conditions: the dataset has no existing thumbnail; the dataset has image files that can be converted to a thumbnailt the Feature Flag "disable-dataset-thumbnail-autoselect" is not enabled. See #11588 and #12403. + ## Other Changes - The deaccession reason "Not a valid dataset." has been changed to "Not valid. This dataset does not comply with repository policies." See the Bundle.properties key file.deaccessionDialog.reason.selectItem.notValid and #11985. From 0cb7712d9ff03eafc81c9a2a49e24f1ce21e4f8b Mon Sep 17 00:00:00 2001 From: Philip Durbin Date: Wed, 17 Jun 2026 09:26:32 -0400 Subject: [PATCH 10/56] citation format API --- doc/release-notes/11733-api-get-file-citation-format.md | 4 ---- doc/release-notes/6.11-release-notes.md | 2 ++ 2 files changed, 2 insertions(+), 4 deletions(-) delete mode 100644 doc/release-notes/11733-api-get-file-citation-format.md diff --git a/doc/release-notes/11733-api-get-file-citation-format.md b/doc/release-notes/11733-api-get-file-citation-format.md deleted file mode 100644 index b315e8176b8..00000000000 --- a/doc/release-notes/11733-api-get-file-citation-format.md +++ /dev/null @@ -1,4 +0,0 @@ -### Feature New API ### -New API added to retrieve the DataFile Citation in a requested format. This is similar output to the API to get the Dataset Citation. - -SERVER_URL/api/access/datafile/{fileId}/citation/{format} diff --git a/doc/release-notes/6.11-release-notes.md b/doc/release-notes/6.11-release-notes.md index 4625eb7a71d..c0fbdcee778 100644 --- a/doc/release-notes/6.11-release-notes.md +++ b/doc/release-notes/6.11-release-notes.md @@ -46,6 +46,8 @@ A new button called "Show Historical Requests" checkbox has been added to the pe ## API Updates +- A new API has been added to get citations in various formats such as EndNote, RIS, BibTeX, and CSL. Previously this functionality was only available via the UI. See [the guides](https://guides.dataverse.org/en/6.11/api/dataaccess.html#citation-get-citation-in-other-formats), #11733 and #12238. + - The `/datafile/{id}/listRequests` API has been extended to show request history. See [the guides](https://guides.dataverse.org/en/6.11/api/dataaccess.html#list-file-access-requests), #8013 and #12012. ## Security Updates From 5f26de065fc539636cbe3c299616b40d5dd76248 Mon Sep 17 00:00:00 2001 From: Philip Durbin Date: Wed, 17 Jun 2026 09:56:53 -0400 Subject: [PATCH 11/56] template APIs --- doc/release-notes/11912-edit-template-apis | 23 ---------------------- doc/release-notes/6.11-release-notes.md | 1 + 2 files changed, 1 insertion(+), 23 deletions(-) delete mode 100644 doc/release-notes/11912-edit-template-apis diff --git a/doc/release-notes/11912-edit-template-apis b/doc/release-notes/11912-edit-template-apis deleted file mode 100644 index 91324f38330..00000000000 --- a/doc/release-notes/11912-edit-template-apis +++ /dev/null @@ -1,23 +0,0 @@ -## New Endpoint: PUT `/dataverses/{templateId}/metadata` - -A new endpoint has been implemented to edit the metadata and field instructions for a given template. - -### Functionality -- Updates the metadata and field instructions for a template based on a json file provided. -- You must have edit dataverse permission in the collection in order to use this endpoint. - -## New Endpoint: PUT `/dataverses/{templateId}/licenseTerms` - -A new endpoint has been implemented to edit the license or custom terms of use for a given template. - -### Functionality -- Updates the license or custom terms of use for a template based on a json file provided. -- You must have edit dataverse permission in the collection in order to use this endpoint. - -## New Endpoint: PUT `/dataverses/{templateId}/access` - -A new endpoint has been implemented to edit the terms of access for a given template. - -### Functionality -- Updates the terms of access for a template based on a json file provided. -- You must have edit dataverse permission in the collection in order to use this endpoint. diff --git a/doc/release-notes/6.11-release-notes.md b/doc/release-notes/6.11-release-notes.md index c0fbdcee778..813aeac81c9 100644 --- a/doc/release-notes/6.11-release-notes.md +++ b/doc/release-notes/6.11-release-notes.md @@ -46,6 +46,7 @@ A new button called "Show Historical Requests" checkbox has been added to the pe ## API Updates +- New APIs have been added called [Update the Metadata and Instructions of a Template](https://guides.dataverse.org/en/6.11/api/native-api.html#update-the-metadata-and-instructions-of-a-template), [Update the License or Terms Of Use of a Template](https://guides.dataverse.org/en/6.11/api/native-api.html#update-the-license-or-terms-of-use-of-a-template), and [Update the Terms Of Access of a Template](https://guides.dataverse.org/en/6.11/api/native-api.html#update-the-terms-of-access-of-a-template). See #11912 and #12159. - A new API has been added to get citations in various formats such as EndNote, RIS, BibTeX, and CSL. Previously this functionality was only available via the UI. See [the guides](https://guides.dataverse.org/en/6.11/api/dataaccess.html#citation-get-citation-in-other-formats), #11733 and #12238. - The `/datafile/{id}/listRequests` API has been extended to show request history. See [the guides](https://guides.dataverse.org/en/6.11/api/dataaccess.html#list-file-access-requests), #8013 and #12012. From 4caf17b3990eefc14a51364237e7525ec6038899 Mon Sep 17 00:00:00 2001 From: Philip Durbin Date: Wed, 17 Jun 2026 11:50:29 -0400 Subject: [PATCH 12/56] more ra info --- doc/release-notes/11920-more-ra-info.md | 1 - doc/release-notes/6.11-release-notes.md | 2 +- 2 files changed, 1 insertion(+), 2 deletions(-) delete mode 100644 doc/release-notes/11920-more-ra-info.md diff --git a/doc/release-notes/11920-more-ra-info.md b/doc/release-notes/11920-more-ra-info.md deleted file mode 100644 index 7ef12e06fea..00000000000 --- a/doc/release-notes/11920-more-ra-info.md +++ /dev/null @@ -1 +0,0 @@ -All API endpoints that return information about role assignments (such as `/api/dataverses/$ID/assignments`) now include additional fields in their JSON responses: `assigneeName`, `roleDescription`, `definitionPointName`, `definitionPointType`, and `definitionPointGlobalId` (if available). \ No newline at end of file diff --git a/doc/release-notes/6.11-release-notes.md b/doc/release-notes/6.11-release-notes.md index 813aeac81c9..0350e71c26f 100644 --- a/doc/release-notes/6.11-release-notes.md +++ b/doc/release-notes/6.11-release-notes.md @@ -48,7 +48,7 @@ A new button called "Show Historical Requests" checkbox has been added to the pe - New APIs have been added called [Update the Metadata and Instructions of a Template](https://guides.dataverse.org/en/6.11/api/native-api.html#update-the-metadata-and-instructions-of-a-template), [Update the License or Terms Of Use of a Template](https://guides.dataverse.org/en/6.11/api/native-api.html#update-the-license-or-terms-of-use-of-a-template), and [Update the Terms Of Access of a Template](https://guides.dataverse.org/en/6.11/api/native-api.html#update-the-terms-of-access-of-a-template). See #11912 and #12159. - A new API has been added to get citations in various formats such as EndNote, RIS, BibTeX, and CSL. Previously this functionality was only available via the UI. See [the guides](https://guides.dataverse.org/en/6.11/api/dataaccess.html#citation-get-citation-in-other-formats), #11733 and #12238. - +- All API endpoints that return information about role assignments (such as `/api/dataverses/$ID/assignments`) now include additional fields in their JSON responses: `assigneeName`, `roleDescription`, `definitionPointName`, `definitionPointType`, and `definitionPointGlobalId` (if available). See #11920. - The `/datafile/{id}/listRequests` API has been extended to show request history. See [the guides](https://guides.dataverse.org/en/6.11/api/dataaccess.html#list-file-access-requests), #8013 and #12012. ## Security Updates From d40ae709fba0556f51b40a889db67ea6223a516d Mon Sep 17 00:00:00 2001 From: Philip Durbin Date: Wed, 17 Jun 2026 11:52:29 -0400 Subject: [PATCH 13/56] list of features --- doc/release-notes/11998-features-in-guides.md | 1 - doc/release-notes/6.11-release-notes.md | 1 + 2 files changed, 1 insertion(+), 1 deletion(-) delete mode 100644 doc/release-notes/11998-features-in-guides.md diff --git a/doc/release-notes/11998-features-in-guides.md b/doc/release-notes/11998-features-in-guides.md deleted file mode 100644 index 1f96b99463f..00000000000 --- a/doc/release-notes/11998-features-in-guides.md +++ /dev/null @@ -1 +0,0 @@ -A [list of Dataverse features](https://dataverse-guide--12000.org.readthedocs.build/en/12000/admin/features.html) has been added to the guides. See #11998 and #12000. diff --git a/doc/release-notes/6.11-release-notes.md b/doc/release-notes/6.11-release-notes.md index 0350e71c26f..2dd76e2247e 100644 --- a/doc/release-notes/6.11-release-notes.md +++ b/doc/release-notes/6.11-release-notes.md @@ -42,6 +42,7 @@ A new button called "Show Historical Requests" checkbox has been added to the pe ## Other Changes +- A [list of Dataverse features](https://guides.dataverse.org/en/6.11/admin/features.html) has been added to the guides. See #11998 and #12000. - The deaccession reason "Not a valid dataset." has been changed to "Not valid. This dataset does not comply with repository policies." See the Bundle.properties key file.deaccessionDialog.reason.selectItem.notValid and #11985. ## API Updates From 0343fa5f6300e4846c23c45280f9347859d72d44 Mon Sep 17 00:00:00 2001 From: Philip Durbin Date: Wed, 17 Jun 2026 12:03:57 -0400 Subject: [PATCH 14/56] croissant 1.1 --- doc/release-notes/12014-croissant-1.1.md | 25 ------------------------ doc/release-notes/6.11-release-notes.md | 21 ++++++++++++++++++-- 2 files changed, 19 insertions(+), 27 deletions(-) delete mode 100644 doc/release-notes/12014-croissant-1.1.md diff --git a/doc/release-notes/12014-croissant-1.1.md b/doc/release-notes/12014-croissant-1.1.md deleted file mode 100644 index 44c796c593d..00000000000 --- a/doc/release-notes/12014-croissant-1.1.md +++ /dev/null @@ -1,25 +0,0 @@ -### Croissant 1.1 (Summary Statistics) - -The Croissant metadata export format has been updated from version 1.0 to 1.1. - -Summary statistics (mean, min, max, etc.) are now included for tabular files that were successfully ingested. - -You can download an example Croissant file from the [Supported Metadata Export Formats](https://dataverse-guide--12214.org.readthedocs.build/en/12214/user/dataset-management.html#supported-metadata-export-formats) section of the guides. - -Minor backward-incompatible changes were made, which are noted below. - -See #12014 and #12214 - -## Backward Incompatible Changes - -Generally speaking, see the [API Changelog](https://guides.dataverse.org/en/latest/api/changelog.html) for a list of backward-incompatible API changes. - -Minor changes in the `croissant` format are noted in the [API changelog](https://dataverse-guide--12214.org.readthedocs.build/en/12214/api/changelog.html). - -## Upgrade Instructions - -1. Re-export metadata export formats - - We re-export because the Croissant format was updated. - - `curl http://localhost:8080/api/admin/metadata/reExportAll` diff --git a/doc/release-notes/6.11-release-notes.md b/doc/release-notes/6.11-release-notes.md index 2dd76e2247e..d86adf4d93c 100644 --- a/doc/release-notes/6.11-release-notes.md +++ b/doc/release-notes/6.11-release-notes.md @@ -24,6 +24,16 @@ This new expanded metadata block aligns with the international ISO 19115 standar See [the guides](https://guides.dataverse.org/en/6.11/user/appendix.html#supported-metadata), #10398, and #11507. +### Croissant 1.1 (Summary Statistics) + +The Croissant metadata export format has been updated from version 1.0 to 1.1. + +Summary statistics (mean, min, max, etc.) are now included for tabular files that were successfully ingested. + +You can download an example Croissant file from the [Supported Metadata Export Formats](https://guides.dataverse.org/en/6.11/user/dataset-management.html#supported-metadata-export-formats) section of the guides. + +Minor backward-incompatible changes were made, which are noted below. See #12014 and #12214. + ## Features Added These are features that weren't already mentioned under "highlights" above. @@ -61,6 +71,7 @@ This release contains important security updates. If you are not receiving secur Generally speaking, see the [API Changelog](https://guides.dataverse.org/en/latest/api/changelog.html) for a list of backward-incompatible API changes. - The GET /api/mydata/retrieve, if the search returns no data, now includes the "data" block with 0 results. The message that was returned in "error_message" will be returned in "message" and the "success" will be `true`. All other errors will continue to reply with "success":false and the error message in "error_message". See #11447 and #12256. +- The Croissant metadata export format has been updated from version 1.0 to 1.1, which is reflected in the "conformsTo" property. The unused "wd" property has been dropped. ## End-Of-Life (EOL) Announcements @@ -136,7 +147,7 @@ Also, we assume that Payara is installed in `/usr/local/payara7`. If not, adjust `curl http://localhost:8080/api/admin/datasetfield/load -H "Content-type: text/tab-separated-values" -X POST --upload-file geospatial.tsv` -1. Update Solr schema +1. Update Solr schema. Due to changes in the Solr schema (the addition of geospatial fields), updating the Solr schema and reindexing is required. @@ -156,12 +167,18 @@ Also, we assume that Payara is installed in `/usr/local/payara7`. If not, adjust `curl "http://localhost:8983/solr/admin/cores?action=RELOAD&core=collection1"` -1. Reindex Solr +1. Reindex Solr. Solr needs to be reindexed because of the change to deaccessionDialog.reason.selectItem.notValid in Bundle.properties (#11985). `curl http://localhost:8080/api/admin/index` +1. Re-export metadata export formats. + + We re-export because the Croissant format was updated. + + `curl http://localhost:8080/api/admin/metadata/reExportAll` + 1. For installations with internationalization or text customizations: Please remember to update translations via [Dataverse language packs](https://github.com/GlobalDataverseCommunityConsortium/dataverse-language-packs). From f1a6e2c3bfe98d20477c134a5d0dfcd122ffc5e8 Mon Sep 17 00:00:00 2001 From: Philip Durbin Date: Wed, 17 Jun 2026 15:11:05 -0400 Subject: [PATCH 15/56] datacite utf bug --- .../12070-datacite-getmetadata.md | 11 ----------- doc/release-notes/6.11-release-notes.md | 19 ++++++++++++++++++- 2 files changed, 18 insertions(+), 12 deletions(-) delete mode 100644 doc/release-notes/12070-datacite-getmetadata.md diff --git a/doc/release-notes/12070-datacite-getmetadata.md b/doc/release-notes/12070-datacite-getmetadata.md deleted file mode 100644 index dcef698e3e5..00000000000 --- a/doc/release-notes/12070-datacite-getmetadata.md +++ /dev/null @@ -1,11 +0,0 @@ -Incremental improvements have been made to the process of registering dataset metadata with DataCite. If your instance is using DataCite, please make sure you have a valid DataCite REST API url configured, since it is now required. - -The JVM option(s) in question are `dataverse.pid.*.datacite.rest-api-url` if the recommended, new-style pid configuration is used, or `doi.dataciterestapiurlstring` if the legacy settings are in place. In the latter case however, this may be a good occasion to switch to the new configuration setup. - -For instances using registered DataCite authorities in production the url should be: - -```-Ddataverse.pid..datacite.rest-api-url=https://api.datacite.org``` - -Or, for test and development instances: - -```-Ddataverse.pid..datacite.rest-api-url=https://api.test.datacite.org``` \ No newline at end of file diff --git a/doc/release-notes/6.11-release-notes.md b/doc/release-notes/6.11-release-notes.md index d86adf4d93c..479906a46bd 100644 --- a/doc/release-notes/6.11-release-notes.md +++ b/doc/release-notes/6.11-release-notes.md @@ -48,6 +48,7 @@ A new button called "Show Historical Requests" checkbox has been added to the pe ## Bug Fixes +- When the "modifyRegistrationMetadata" API was used, some datasets with UTF-8 characters were beeing unnecessarily updated in DataCite. This has been resolved by switching from the DataCite MDS API to its JSON API. See the upgrade instructions below, #12070, and #12270. - The bug "Search API doesn't return image_url after newly created dataset is published" was fixed in the following manner. The dataset thumbnail will be created automatically when a dataset is published under the following conditions: the dataset has no existing thumbnail; the dataset has image files that can be converted to a thumbnailt the Feature Flag "disable-dataset-thumbnail-autoselect" is not enabled. See #11588 and #12403. ## Other Changes @@ -185,4 +186,20 @@ Also, we assume that Payara is installed in `/usr/local/payara7`. If not, adjust If you have text customizations you can get the latest English files from . - Note that deaccessionDialog.reason.selectItem.notValid was updated. See #11985. \ No newline at end of file + Note that deaccessionDialog.reason.selectItem.notValid was updated. See #11985. + +1. For installations using DataCite, ensure the DataCite REST API URL (now required) is configured: + + Incremental improvements have been made to the process of registering dataset metadata with DataCite. If your instance is using DataCite, please make sure you have a valid DataCite REST API URL configured, since it is now required. + + The JVM options in question are `dataverse.pid.*.datacite.rest-api-url` if the recommended, new-style PID configuration is used, or `doi.dataciterestapiurlstring` if the legacy settings are in place. In the latter case however, this is a good occasion to switch to the new configuration setup. + + For installations using registered DataCite authorities in production the URL should be: + + `-Ddataverse.pid..datacite.rest-api-url=https://api.datacite.org` + + Or, for test and development instances: + + `-Ddataverse.pid..datacite.rest-api-url=https://api.test.datacite.org` + + See [the guides](https://guides.dataverse.org/en/6.11/installation/config.html#datacite-specific-settings), #12070 and #12270. \ No newline at end of file From d4bc81169a1bd65a4a5b52c502b168a82c15c1d7 Mon Sep 17 00:00:00 2001 From: Philip Durbin Date: Wed, 17 Jun 2026 15:15:31 -0400 Subject: [PATCH 16/56] mention other sphinx dep --- doc/release-notes/6.11-release-notes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/release-notes/6.11-release-notes.md b/doc/release-notes/6.11-release-notes.md index 479906a46bd..22362a9c41e 100644 --- a/doc/release-notes/6.11-release-notes.md +++ b/doc/release-notes/6.11-release-notes.md @@ -98,7 +98,7 @@ We fixed an inconsistency where the `CorsFilter` was not always being invoked wh ## Updates for Documentation Writers -A new dependency called "sphinx-reredirects" has been added. Please re-run the `pip install -r requirements.txt` setup [step](https://guides.dataverse.org/en/6.11/contributor/documentation.html#building-the-guides-with-sphinx) to update your environment. Otherwise you might see an error like `Could not import extension sphinx_reredirects`. +The dependencies "sphinx-reredirects" and "sphinx-design" have been added. Please re-run the `pip install -r requirements.txt` setup [step](https://guides.dataverse.org/en/6.11/contributor/documentation.html#building-the-guides-with-sphinx) to update your environment. Otherwise you will see a "could not import extension" error. ## Updates for Developers From 4db534125d6c10df8444ff1aafd8d646593caa3b Mon Sep 17 00:00:00 2001 From: Philip Durbin Date: Wed, 17 Jun 2026 15:25:30 -0400 Subject: [PATCH 17/56] userperm needs auth --- doc/release-notes/6.11-release-notes.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/doc/release-notes/6.11-release-notes.md b/doc/release-notes/6.11-release-notes.md index 22362a9c41e..932dc390eff 100644 --- a/doc/release-notes/6.11-release-notes.md +++ b/doc/release-notes/6.11-release-notes.md @@ -71,7 +71,8 @@ This release contains important security updates. If you are not receiving secur Generally speaking, see the [API Changelog](https://guides.dataverse.org/en/latest/api/changelog.html) for a list of backward-incompatible API changes. -- The GET /api/mydata/retrieve, if the search returns no data, now includes the "data" block with 0 results. The message that was returned in "error_message" will be returned in "message" and the "success" will be `true`. All other errors will continue to reply with "success":false and the error message in "error_message". See #11447 and #12256. +- The `GET /api/access/datafile/{id}/userPermissions` endpoint now requires authentication. +- The `GET /api/mydata/retrieve` endpoint, if the search returns no data, now includes the "data" block with 0 results. The message that was returned in "error_message" will be returned in "message" and the "success" will be `true`. All other errors will continue to reply with "success":false and the error message in "error_message". See #11447 and #12256. - The Croissant metadata export format has been updated from version 1.0 to 1.1, which is reflected in the "conformsTo" property. The unused "wd" property has been dropped. ## End-Of-Life (EOL) Announcements From 65c9e0ad367e97e1c7083f0a1267c56911f19a46 Mon Sep 17 00:00:00 2001 From: Philip Durbin Date: Wed, 17 Jun 2026 15:28:06 -0400 Subject: [PATCH 18/56] default contributor role API --- doc/release-notes/12112-get-default-contributor-role.md | 1 - doc/release-notes/6.11-release-notes.md | 1 + 2 files changed, 1 insertion(+), 1 deletion(-) delete mode 100644 doc/release-notes/12112-get-default-contributor-role.md diff --git a/doc/release-notes/12112-get-default-contributor-role.md b/doc/release-notes/12112-get-default-contributor-role.md deleted file mode 100644 index 0ed0072bd6e..00000000000 --- a/doc/release-notes/12112-get-default-contributor-role.md +++ /dev/null @@ -1 +0,0 @@ -A new API endpoint for getting the default contributor role of a collection (`GET /api/dataverses/$ID/defaultContributorRole`) was added. \ No newline at end of file diff --git a/doc/release-notes/6.11-release-notes.md b/doc/release-notes/6.11-release-notes.md index 932dc390eff..a671efdcea2 100644 --- a/doc/release-notes/6.11-release-notes.md +++ b/doc/release-notes/6.11-release-notes.md @@ -59,6 +59,7 @@ A new button called "Show Historical Requests" checkbox has been added to the pe ## API Updates - New APIs have been added called [Update the Metadata and Instructions of a Template](https://guides.dataverse.org/en/6.11/api/native-api.html#update-the-metadata-and-instructions-of-a-template), [Update the License or Terms Of Use of a Template](https://guides.dataverse.org/en/6.11/api/native-api.html#update-the-license-or-terms-of-use-of-a-template), and [Update the Terms Of Access of a Template](https://guides.dataverse.org/en/6.11/api/native-api.html#update-the-terms-of-access-of-a-template). See #11912 and #12159. +- A new API endpoint for getting the default contributor role of a collection was added. See [the guides](https://guides.dataverse.org/en/6.11/api/native-api.html#get-default-role-assigned-to-user-creating-a-dataset-in-a-dataverse-collection) and #12112. - A new API has been added to get citations in various formats such as EndNote, RIS, BibTeX, and CSL. Previously this functionality was only available via the UI. See [the guides](https://guides.dataverse.org/en/6.11/api/dataaccess.html#citation-get-citation-in-other-formats), #11733 and #12238. - All API endpoints that return information about role assignments (such as `/api/dataverses/$ID/assignments`) now include additional fields in their JSON responses: `assigneeName`, `roleDescription`, `definitionPointName`, `definitionPointType`, and `definitionPointGlobalId` (if available). See #11920. - The `/datafile/{id}/listRequests` API has been extended to show request history. See [the guides](https://guides.dataverse.org/en/6.11/api/dataaccess.html#list-file-access-requests), #8013 and #12012. From d50859285cacabeca8cf86e97e10405f09880712 Mon Sep 17 00:00:00 2001 From: Philip Durbin Date: Wed, 17 Jun 2026 15:32:15 -0400 Subject: [PATCH 19/56] storage driver API changes --- doc/release-notes/12141-storage-driver-endpoints.md | 6 ------ doc/release-notes/6.11-release-notes.md | 3 +++ 2 files changed, 3 insertions(+), 6 deletions(-) delete mode 100644 doc/release-notes/12141-storage-driver-endpoints.md diff --git a/doc/release-notes/12141-storage-driver-endpoints.md b/doc/release-notes/12141-storage-driver-endpoints.md deleted file mode 100644 index 2d57da3f04d..00000000000 --- a/doc/release-notes/12141-storage-driver-endpoints.md +++ /dev/null @@ -1,6 +0,0 @@ -### Breaking Changes - -All endpoints related to storage drivers have been moved out of the Admin API. - -- The GET, PUT, and DELETE endpoints for `/api/admin/dataverse/{alias}/storageDriver` have been moved to `/api/dataverses/{alias}/storageDriver`. Write operations continue to be accessible only to superusers, while GET methods are public. -- The endpoint `/api/admin/dataverse/storageDrivers` has been made public, moved, and renamed to `/api/dataverses/{alias}/allowedStorageDrivers`. Regarding the name change, this endpoint will in the future only display the storage drivers that are allowed on the specified collection. For now, it will display the entire list of available drivers on the installation. diff --git a/doc/release-notes/6.11-release-notes.md b/doc/release-notes/6.11-release-notes.md index a671efdcea2..2565f6dd9af 100644 --- a/doc/release-notes/6.11-release-notes.md +++ b/doc/release-notes/6.11-release-notes.md @@ -75,6 +75,9 @@ Generally speaking, see the [API Changelog](https://guides.dataverse.org/en/late - The `GET /api/access/datafile/{id}/userPermissions` endpoint now requires authentication. - The `GET /api/mydata/retrieve` endpoint, if the search returns no data, now includes the "data" block with 0 results. The message that was returned in "error_message" will be returned in "message" and the "success" will be `true`. All other errors will continue to reply with "success":false and the error message in "error_message". See #11447 and #12256. - The Croissant metadata export format has been updated from version 1.0 to 1.1, which is reflected in the "conformsTo" property. The unused "wd" property has been dropped. +- All endpoints related to storage drivers have been moved out of the Admin API. See #12141 and #12182. + - The GET, PUT, and DELETE endpoints for `/api/admin/dataverse/{alias}/storageDriver` have been moved to `/api/dataverses/{alias}/storageDriver`. Write operations continue to be accessible only to superusers, while GET methods are public. + - The endpoint `/api/admin/dataverse/storageDrivers` has been made public, moved, and renamed to `/api/dataverses/{alias}/allowedStorageDrivers`. Regarding the name change, this endpoint will in the future only display the storage drivers that are allowed on the specified collection. For now, it will display the entire list of available drivers on the installation. ## End-Of-Life (EOL) Announcements From 78f75cb1e91ca860e69314e422f16eecaaf82bff Mon Sep 17 00:00:00 2001 From: Philip Durbin Date: Wed, 17 Jun 2026 15:36:14 -0400 Subject: [PATCH 20/56] handles --- doc/release-notes/12174-handle-improvements.md | 5 ----- doc/release-notes/6.11-release-notes.md | 7 +++++++ 2 files changed, 7 insertions(+), 5 deletions(-) delete mode 100644 doc/release-notes/12174-handle-improvements.md diff --git a/doc/release-notes/12174-handle-improvements.md b/doc/release-notes/12174-handle-improvements.md deleted file mode 100644 index 09315f352f6..00000000000 --- a/doc/release-notes/12174-handle-improvements.md +++ /dev/null @@ -1,5 +0,0 @@ -This release offers improved support for Handles as persistent ids. - -The following issues are fixed: -- When pid registration of persistent ids for files is enabled, Dataverse will create the handle as soon as the file is created (similary to other persistent id providers) (issue #12174); -- When a new handle is created, for a dataset or file that is still a draft, it will be reserved and registered, but not visible publicly. The handle will become visible and the redirects will start working once it is published. This is also in line with how DOI providers work (issue #8881). \ No newline at end of file diff --git a/doc/release-notes/6.11-release-notes.md b/doc/release-notes/6.11-release-notes.md index 2565f6dd9af..ce99c7a0db9 100644 --- a/doc/release-notes/6.11-release-notes.md +++ b/doc/release-notes/6.11-release-notes.md @@ -46,6 +46,13 @@ In previous releases of Dataverse, the file, dataset, and collection pages showe A new button called "Show Historical Requests" checkbox has been added to the permissions page for a data file. Checking the box will show the number of times access has been granted or denied by user. See #8013 and #12012. +### Improved Support for Handles as Persistent IDs + +The following issues were addressed in #12366: + +- When PID registration of persistent ids for files is enabled, Dataverse will create the handle as soon as the file is created (similarly to other persistent id providers) (issue #12174); +- When a new handle is created for a dataset or file that is still a draft, it will be reserved and registered, but not visible publicly. The handle will become visible and the redirects will start working once it is published. This is also in line with how DOI providers work (issue #8881). + ## Bug Fixes - When the "modifyRegistrationMetadata" API was used, some datasets with UTF-8 characters were beeing unnecessarily updated in DataCite. This has been resolved by switching from the DataCite MDS API to its JSON API. See the upgrade instructions below, #12070, and #12270. From 5437393b17c5bdc06f2c6cd4d32b8881489ebcb5 Mon Sep 17 00:00:00 2001 From: Philip Durbin Date: Wed, 17 Jun 2026 15:41:04 -0400 Subject: [PATCH 21/56] email exclude --- .../12194-ignore-exclude-email-setting-for-collections.md | 2 -- doc/release-notes/6.11-release-notes.md | 1 + 2 files changed, 1 insertion(+), 2 deletions(-) delete mode 100644 doc/release-notes/12194-ignore-exclude-email-setting-for-collections.md diff --git a/doc/release-notes/12194-ignore-exclude-email-setting-for-collections.md b/doc/release-notes/12194-ignore-exclude-email-setting-for-collections.md deleted file mode 100644 index def993ae624..00000000000 --- a/doc/release-notes/12194-ignore-exclude-email-setting-for-collections.md +++ /dev/null @@ -1,2 +0,0 @@ -A new query parameter (`ignoreSettingExcludeEmailFromExport`) has been added to the ["View a Dataverse Collection"](https://guides.dataverse.org/en/latest/api/native-api.html#view-a-dataverse-collection) API (`/api/dataverses/{collectionId}`). -This query parameter prevents the contact emails from being excluded when the setting `ExcludeEmailFromExport` is set to true and the user has EditDataverse permissions. \ No newline at end of file diff --git a/doc/release-notes/6.11-release-notes.md b/doc/release-notes/6.11-release-notes.md index ce99c7a0db9..9ea943e53b4 100644 --- a/doc/release-notes/6.11-release-notes.md +++ b/doc/release-notes/6.11-release-notes.md @@ -68,6 +68,7 @@ The following issues were addressed in #12366: - New APIs have been added called [Update the Metadata and Instructions of a Template](https://guides.dataverse.org/en/6.11/api/native-api.html#update-the-metadata-and-instructions-of-a-template), [Update the License or Terms Of Use of a Template](https://guides.dataverse.org/en/6.11/api/native-api.html#update-the-license-or-terms-of-use-of-a-template), and [Update the Terms Of Access of a Template](https://guides.dataverse.org/en/6.11/api/native-api.html#update-the-terms-of-access-of-a-template). See #11912 and #12159. - A new API endpoint for getting the default contributor role of a collection was added. See [the guides](https://guides.dataverse.org/en/6.11/api/native-api.html#get-default-role-assigned-to-user-creating-a-dataset-in-a-dataverse-collection) and #12112. - A new API has been added to get citations in various formats such as EndNote, RIS, BibTeX, and CSL. Previously this functionality was only available via the UI. See [the guides](https://guides.dataverse.org/en/6.11/api/dataaccess.html#citation-get-citation-in-other-formats), #11733 and #12238. +- A new query parameter (`ignoreSettingExcludeEmailFromExport`) has been added to the ["View a Dataverse Collection"](https://guides.dataverse.org/en/6.11/api/native-api.html#view-a-dataverse-collection) API (`/api/dataverses/{collectionId}`). This query parameter prevents the contact emails from being excluded when the setting `:ExcludeEmailFromExport` is set to true and the user has EditDataverse permissions. See #12194 and #12195. - All API endpoints that return information about role assignments (such as `/api/dataverses/$ID/assignments`) now include additional fields in their JSON responses: `assigneeName`, `roleDescription`, `definitionPointName`, `definitionPointType`, and `definitionPointGlobalId` (if available). See #11920. - The `/datafile/{id}/listRequests` API has been extended to show request history. See [the guides](https://guides.dataverse.org/en/6.11/api/dataaccess.html#list-file-access-requests), #8013 and #12012. From 14731d9cfb067df99c2767cfff9883cfee83123f Mon Sep 17 00:00:00 2001 From: Philip Durbin Date: Wed, 17 Jun 2026 15:47:03 -0400 Subject: [PATCH 22/56] local contexts --- .../12224-local-contexts-rights-info-in-DataCite | 8 -------- doc/release-notes/6.11-release-notes.md | 6 ++++++ 2 files changed, 6 insertions(+), 8 deletions(-) delete mode 100644 doc/release-notes/12224-local-contexts-rights-info-in-DataCite diff --git a/doc/release-notes/12224-local-contexts-rights-info-in-DataCite b/doc/release-notes/12224-local-contexts-rights-info-in-DataCite deleted file mode 100644 index c0a4c7b4d7a..00000000000 --- a/doc/release-notes/12224-local-contexts-rights-info-in-DataCite +++ /dev/null @@ -1,8 +0,0 @@ -For instances enabling use of Local Contexts integration, Dataverse will now add rights information -related to the Notices and Labels from a Local Contexts Project associated with a dataset to the metadata -sent to DataCite (when using DataCite DOIs) and available in metadata exports (DataCite, OAI-ORE, and JSON). - -It is now possible to use non-string values in the retrieval-filtering context entries for external vocabulary scripts. -This can be used to allow filtered JSON that is not valid JSON-LD to be included in the OAI_ORE JSON-LD metadata export - in a way that JSON-LD parsers will accept (and not ignore/drop). The OAI_ORE export version has been updated to 1.0.3 with this change. - \ No newline at end of file diff --git a/doc/release-notes/6.11-release-notes.md b/doc/release-notes/6.11-release-notes.md index 9ea943e53b4..bf96e4a0698 100644 --- a/doc/release-notes/6.11-release-notes.md +++ b/doc/release-notes/6.11-release-notes.md @@ -46,6 +46,12 @@ In previous releases of Dataverse, the file, dataset, and collection pages showe A new button called "Show Historical Requests" checkbox has been added to the permissions page for a data file. Checking the box will show the number of times access has been granted or denied by user. See #8013 and #12012. +### Local Contexts Improvements + +For instances that have enabled the Local Contexts integration, Dataverse will now add rights information related to the Notices and Labels from a Local Contexts Project associated with a dataset to the metadata sent to DataCite (when using DataCite DOIs) and available in metadata exports (DataCite, OAI-ORE, and JSON). + +In addition, it is now possible to use non-string values in the retrieval-filtering context entries for external vocabulary scripts. This can be used to allow filtered JSON that is not valid JSON-LD to be included in the OAI_ORE JSON-LD metadata export in a way that JSON-LD parsers will accept (and not ignore/drop). The OAI_ORE export version has been updated to 1.0.3 with this change. See the [guides](https://guides.dataverse.org/en/6.11/installation/localcontexts.html#configuration) and #12224. + ### Improved Support for Handles as Persistent IDs The following issues were addressed in #12366: From 43bfc26271c06a1273fa2a7f4546508334a48020 Mon Sep 17 00:00:00 2001 From: Philip Durbin Date: Wed, 17 Jun 2026 16:01:30 -0400 Subject: [PATCH 23/56] CSL fix --- doc/release-notes/12244-fix-citations.md | 1 - doc/release-notes/6.11-release-notes.md | 1 + 2 files changed, 1 insertion(+), 1 deletion(-) delete mode 100644 doc/release-notes/12244-fix-citations.md diff --git a/doc/release-notes/12244-fix-citations.md b/doc/release-notes/12244-fix-citations.md deleted file mode 100644 index 12901225eb2..00000000000 --- a/doc/release-notes/12244-fix-citations.md +++ /dev/null @@ -1 +0,0 @@ -This release fixes a bug causing Author names of Organizations to be incorrect in styled citations (the software attempted to interpret the organization's name as a first name/last name pair). \ No newline at end of file diff --git a/doc/release-notes/6.11-release-notes.md b/doc/release-notes/6.11-release-notes.md index bf96e4a0698..6899fa74cad 100644 --- a/doc/release-notes/6.11-release-notes.md +++ b/doc/release-notes/6.11-release-notes.md @@ -61,6 +61,7 @@ The following issues were addressed in #12366: ## Bug Fixes +- In styled citations (CSL) author names were incorrect when the author was an organization rather than a person (the software attempted to interpret the organization's name as a first name/last name pair). This has been fixed. See #12244 and #12248. - When the "modifyRegistrationMetadata" API was used, some datasets with UTF-8 characters were beeing unnecessarily updated in DataCite. This has been resolved by switching from the DataCite MDS API to its JSON API. See the upgrade instructions below, #12070, and #12270. - The bug "Search API doesn't return image_url after newly created dataset is published" was fixed in the following manner. The dataset thumbnail will be created automatically when a dataset is published under the following conditions: the dataset has no existing thumbnail; the dataset has image files that can be converted to a thumbnailt the Feature Flag "disable-dataset-thumbnail-autoselect" is not enabled. See #11588 and #12403. From 7ef95a9eacf1f573817faa9a3d90beec380bc13d Mon Sep 17 00:00:00 2001 From: Philip Durbin Date: Wed, 17 Jun 2026 16:04:58 -0400 Subject: [PATCH 24/56] guestbook fix --- .../12245-anon-guestbook-download-via-persistentid.md | 4 ---- doc/release-notes/6.11-release-notes.md | 1 + 2 files changed, 1 insertion(+), 4 deletions(-) delete mode 100644 doc/release-notes/12245-anon-guestbook-download-via-persistentid.md diff --git a/doc/release-notes/12245-anon-guestbook-download-via-persistentid.md b/doc/release-notes/12245-anon-guestbook-download-via-persistentid.md deleted file mode 100644 index b926a6441a1..00000000000 --- a/doc/release-notes/12245-anon-guestbook-download-via-persistentid.md +++ /dev/null @@ -1,4 +0,0 @@ -## Bug -Guest requesting file download using :persistentId with guestbook response is now working. - -"persistentId" will be replaced by the actual fileId in the signed url that is returned by the POST call containing the guestbook response. diff --git a/doc/release-notes/6.11-release-notes.md b/doc/release-notes/6.11-release-notes.md index 6899fa74cad..39d2c4a92f5 100644 --- a/doc/release-notes/6.11-release-notes.md +++ b/doc/release-notes/6.11-release-notes.md @@ -61,6 +61,7 @@ The following issues were addressed in #12366: ## Bug Fixes +- Anonymous guestbook download via API using `:persistentId` was failing with a 401. This has been fixed. See #12245 and #12363. - In styled citations (CSL) author names were incorrect when the author was an organization rather than a person (the software attempted to interpret the organization's name as a first name/last name pair). This has been fixed. See #12244 and #12248. - When the "modifyRegistrationMetadata" API was used, some datasets with UTF-8 characters were beeing unnecessarily updated in DataCite. This has been resolved by switching from the DataCite MDS API to its JSON API. See the upgrade instructions below, #12070, and #12270. - The bug "Search API doesn't return image_url after newly created dataset is published" was fixed in the following manner. The dataset thumbnail will be created automatically when a dataset is published under the following conditions: the dataset has no existing thumbnail; the dataset has image files that can be converted to a thumbnailt the Feature Flag "disable-dataset-thumbnail-autoselect" is not enabled. See #11588 and #12403. From 3e801e6eb70c13123932d3af97790f0d00f98dfe Mon Sep 17 00:00:00 2001 From: Philip Durbin Date: Wed, 17 Jun 2026 16:43:42 -0400 Subject: [PATCH 25/56] bagpack --- doc/release-notes/12246-guard-npe-bag-generator.md | 1 - doc/release-notes/6.11-release-notes.md | 1 + 2 files changed, 1 insertion(+), 1 deletion(-) delete mode 100644 doc/release-notes/12246-guard-npe-bag-generator.md diff --git a/doc/release-notes/12246-guard-npe-bag-generator.md b/doc/release-notes/12246-guard-npe-bag-generator.md deleted file mode 100644 index 12069a8fcec..00000000000 --- a/doc/release-notes/12246-guard-npe-bag-generator.md +++ /dev/null @@ -1 +0,0 @@ -Fixed a problem in the BagPack generator, which caused the export to fail for datasets with multiple Contact Points, of which some had no name while others did. \ No newline at end of file diff --git a/doc/release-notes/6.11-release-notes.md b/doc/release-notes/6.11-release-notes.md index 39d2c4a92f5..64843df0214 100644 --- a/doc/release-notes/6.11-release-notes.md +++ b/doc/release-notes/6.11-release-notes.md @@ -65,6 +65,7 @@ The following issues were addressed in #12366: - In styled citations (CSL) author names were incorrect when the author was an organization rather than a person (the software attempted to interpret the organization's name as a first name/last name pair). This has been fixed. See #12244 and #12248. - When the "modifyRegistrationMetadata" API was used, some datasets with UTF-8 characters were beeing unnecessarily updated in DataCite. This has been resolved by switching from the DataCite MDS API to its JSON API. See the upgrade instructions below, #12070, and #12270. - The bug "Search API doesn't return image_url after newly created dataset is published" was fixed in the following manner. The dataset thumbnail will be created automatically when a dataset is published under the following conditions: the dataset has no existing thumbnail; the dataset has image files that can be converted to a thumbnailt the Feature Flag "disable-dataset-thumbnail-autoselect" is not enabled. See #11588 and #12403. +- A bug in the BagPack generator, which caused the export to fail for datasets with multiple Contact Points, of which some had no name while others did, has been fixed. See #12246. ## Other Changes From 7aece9eb272108561b1b8435240d3eab8adc3103 Mon Sep 17 00:00:00 2001 From: Philip Durbin Date: Wed, 17 Jun 2026 16:52:35 -0400 Subject: [PATCH 26/56] submit for review hidden if no files --- doc/release-notes/12258-publish-submit-contains-files.md | 2 -- doc/release-notes/6.11-release-notes.md | 4 ++++ 2 files changed, 4 insertions(+), 2 deletions(-) delete mode 100644 doc/release-notes/12258-publish-submit-contains-files.md diff --git a/doc/release-notes/12258-publish-submit-contains-files.md b/doc/release-notes/12258-publish-submit-contains-files.md deleted file mode 100644 index dd6e6d7153c..00000000000 --- a/doc/release-notes/12258-publish-submit-contains-files.md +++ /dev/null @@ -1,2 +0,0 @@ -## Bug: Publish and Submit for review must contain files -When `requireFilesToPublishDataset` is set on a Dataverse a Dataset must contain files to be published or submitted for review. This fix make sure the dataset version contains files, and not just the dataset. It also adds this check to the `Submit for Review` functionality. diff --git a/doc/release-notes/6.11-release-notes.md b/doc/release-notes/6.11-release-notes.md index 64843df0214..c77a35cd3e3 100644 --- a/doc/release-notes/6.11-release-notes.md +++ b/doc/release-notes/6.11-release-notes.md @@ -42,6 +42,10 @@ These are features that weren't already mentioned under "highlights" above. In previous releases of Dataverse, the file, dataset, and collection pages showed the .tab version of tabular files (a plain text preservation-friendly copy). This has been changed to show the original format instead (e.g. Excel, Stata, etc.). The .tab version is still available from the download menu. See #7956 and #12145. +## Submit for Review Improvements + +- When `requireFilesToPublishDataset` (added in #10994 in Dataverse 6.6) is set on a collection, a dataset must contain files for the Submit for Review button to appear. As before, publishing is also prevented if no files are present. See #12258 and #12266. + ### Show Historical File Access Requests A new button called "Show Historical Requests" checkbox has been added to the permissions page for a data file. Checking the box will show the number of times access has been granted or denied by user. See #8013 and #12012. From e9c996afc9f661afb1e29780f7f3926f853cc1e6 Mon Sep 17 00:00:00 2001 From: Philip Durbin Date: Wed, 17 Jun 2026 16:55:55 -0400 Subject: [PATCH 27/56] guestbook usage count --- .../12260-get-guestbook-with-usage-and-response-counts.md | 2 -- doc/release-notes/6.11-release-notes.md | 1 + 2 files changed, 1 insertion(+), 2 deletions(-) delete mode 100644 doc/release-notes/12260-get-guestbook-with-usage-and-response-counts.md diff --git a/doc/release-notes/12260-get-guestbook-with-usage-and-response-counts.md b/doc/release-notes/12260-get-guestbook-with-usage-and-response-counts.md deleted file mode 100644 index 8f2a4e58d24..00000000000 --- a/doc/release-notes/12260-get-guestbook-with-usage-and-response-counts.md +++ /dev/null @@ -1,2 +0,0 @@ -## API Enhancement -API call to `/api/guestbooks/{dataverseAlias}/list` can now include `"usageCount":#` and `"responseCount":#` in the response by adding the query param "includeStats=true". diff --git a/doc/release-notes/6.11-release-notes.md b/doc/release-notes/6.11-release-notes.md index c77a35cd3e3..bbaa72bfd46 100644 --- a/doc/release-notes/6.11-release-notes.md +++ b/doc/release-notes/6.11-release-notes.md @@ -81,6 +81,7 @@ The following issues were addressed in #12366: - New APIs have been added called [Update the Metadata and Instructions of a Template](https://guides.dataverse.org/en/6.11/api/native-api.html#update-the-metadata-and-instructions-of-a-template), [Update the License or Terms Of Use of a Template](https://guides.dataverse.org/en/6.11/api/native-api.html#update-the-license-or-terms-of-use-of-a-template), and [Update the Terms Of Access of a Template](https://guides.dataverse.org/en/6.11/api/native-api.html#update-the-terms-of-access-of-a-template). See #11912 and #12159. - A new API endpoint for getting the default contributor role of a collection was added. See [the guides](https://guides.dataverse.org/en/6.11/api/native-api.html#get-default-role-assigned-to-user-creating-a-dataset-in-a-dataverse-collection) and #12112. - A new API has been added to get citations in various formats such as EndNote, RIS, BibTeX, and CSL. Previously this functionality was only available via the UI. See [the guides](https://guides.dataverse.org/en/6.11/api/dataaccess.html#citation-get-citation-in-other-formats), #11733 and #12238. +- The API endpoint `/api/guestbooks/{dataverseAlias}/list` can now include `"usageCount":#` and `"responseCount":#` in the response by adding the query param "includeStats=true". See [the guides](https://guides.dataverse.org/en/6.11/api/native-api.html#get-a-list-of-guestbooks-for-a-dataverse-collection), #12260, and #12269. - A new query parameter (`ignoreSettingExcludeEmailFromExport`) has been added to the ["View a Dataverse Collection"](https://guides.dataverse.org/en/6.11/api/native-api.html#view-a-dataverse-collection) API (`/api/dataverses/{collectionId}`). This query parameter prevents the contact emails from being excluded when the setting `:ExcludeEmailFromExport` is set to true and the user has EditDataverse permissions. See #12194 and #12195. - All API endpoints that return information about role assignments (such as `/api/dataverses/$ID/assignments`) now include additional fields in their JSON responses: `assigneeName`, `roleDescription`, `definitionPointName`, `definitionPointType`, and `definitionPointGlobalId` (if available). See #11920. - The `/datafile/{id}/listRequests` API has been extended to show request history. See [the guides](https://guides.dataverse.org/en/6.11/api/dataaccess.html#list-file-access-requests), #8013 and #12012. From f1b371c177b9c15df335cb6dd18f67cc6018a793 Mon Sep 17 00:00:00 2001 From: Philip Durbin Date: Wed, 17 Jun 2026 16:59:05 -0400 Subject: [PATCH 28/56] guestbook API bugs --- doc/release-notes/12267-does-not-save-guestbook-response.md | 4 ---- doc/release-notes/6.11-release-notes.md | 1 + 2 files changed, 1 insertion(+), 4 deletions(-) delete mode 100644 doc/release-notes/12267-does-not-save-guestbook-response.md diff --git a/doc/release-notes/12267-does-not-save-guestbook-response.md b/doc/release-notes/12267-does-not-save-guestbook-response.md deleted file mode 100644 index c30fdeeda81..00000000000 --- a/doc/release-notes/12267-does-not-save-guestbook-response.md +++ /dev/null @@ -1,4 +0,0 @@ -## BUG -Fixes 2 bugs -1. missing "gbrids" in the signed url query parameter list will no longer include "&gbrids=" without a value -2. For SPA, when a user attempting to download files with a guestbook response has no api token but is authenticated by bearer token, a temporary api token will be generated with an expiration of 1 minute which is used for signing and decoding the signed url. diff --git a/doc/release-notes/6.11-release-notes.md b/doc/release-notes/6.11-release-notes.md index bbaa72bfd46..f8e72391d7f 100644 --- a/doc/release-notes/6.11-release-notes.md +++ b/doc/release-notes/6.11-release-notes.md @@ -70,6 +70,7 @@ The following issues were addressed in #12366: - When the "modifyRegistrationMetadata" API was used, some datasets with UTF-8 characters were beeing unnecessarily updated in DataCite. This has been resolved by switching from the DataCite MDS API to its JSON API. See the upgrade instructions below, #12070, and #12270. - The bug "Search API doesn't return image_url after newly created dataset is published" was fixed in the following manner. The dataset thumbnail will be created automatically when a dataset is published under the following conditions: the dataset has no existing thumbnail; the dataset has image files that can be converted to a thumbnailt the Feature Flag "disable-dataset-thumbnail-autoselect" is not enabled. See #11588 and #12403. - A bug in the BagPack generator, which caused the export to fail for datasets with multiple Contact Points, of which some had no name while others did, has been fixed. See #12246. +- Two guestbook API bugs were fixed. First, missing "gbrids" in the signed URL query parameter list will no longer include "&gbrids=" without a value. Second, when a user attempting to download files with a guestbook response has no API token but is authenticated by bearer token, a temporary api token will be generated with an expiration of 1 minute which is used for signing and decoding the signed URL. See #12267, #12277, and #12279 ## Other Changes From 361bd44175d198297cb87846a7229fa9649c2348 Mon Sep 17 00:00:00 2001 From: Philip Durbin Date: Wed, 17 Jun 2026 17:58:32 -0400 Subject: [PATCH 29/56] s3 bug --- .../12268-direct-upload-support-legacy-lowercase-dois.md | 1 - doc/release-notes/6.11-release-notes.md | 1 + 2 files changed, 1 insertion(+), 1 deletion(-) delete mode 100644 doc/release-notes/12268-direct-upload-support-legacy-lowercase-dois.md diff --git a/doc/release-notes/12268-direct-upload-support-legacy-lowercase-dois.md b/doc/release-notes/12268-direct-upload-support-legacy-lowercase-dois.md deleted file mode 100644 index a26a4b3beaf..00000000000 --- a/doc/release-notes/12268-direct-upload-support-legacy-lowercase-dois.md +++ /dev/null @@ -1 +0,0 @@ -Fixed a problem with S3 direct upload to datasets which using lower- or mixed-case PID authority/identifier in the database and to datasets using an alternative identifier for file storage. diff --git a/doc/release-notes/6.11-release-notes.md b/doc/release-notes/6.11-release-notes.md index f8e72391d7f..5c8be7ce974 100644 --- a/doc/release-notes/6.11-release-notes.md +++ b/doc/release-notes/6.11-release-notes.md @@ -68,6 +68,7 @@ The following issues were addressed in #12366: - Anonymous guestbook download via API using `:persistentId` was failing with a 401. This has been fixed. See #12245 and #12363. - In styled citations (CSL) author names were incorrect when the author was an organization rather than a person (the software attempted to interpret the organization's name as a first name/last name pair). This has been fixed. See #12244 and #12248. - When the "modifyRegistrationMetadata" API was used, some datasets with UTF-8 characters were beeing unnecessarily updated in DataCite. This has been resolved by switching from the DataCite MDS API to its JSON API. See the upgrade instructions below, #12070, and #12270. +- Fixed a problem with S3 direct upload to datasets which using lower- or mixed-case PID authority/identifier in the database and to datasets using an alternative identifier for file storage. See #12268. - The bug "Search API doesn't return image_url after newly created dataset is published" was fixed in the following manner. The dataset thumbnail will be created automatically when a dataset is published under the following conditions: the dataset has no existing thumbnail; the dataset has image files that can be converted to a thumbnailt the Feature Flag "disable-dataset-thumbnail-autoselect" is not enabled. See #11588 and #12403. - A bug in the BagPack generator, which caused the export to fail for datasets with multiple Contact Points, of which some had no name while others did, has been fixed. See #12246. - Two guestbook API bugs were fixed. First, missing "gbrids" in the signed URL query parameter list will no longer include "&gbrids=" without a value. Second, when a user attempting to download files with a guestbook response has no API token but is authenticated by bearer token, a temporary api token will be generated with an expiration of 1 minute which is used for signing and decoding the signed URL. See #12267, #12277, and #12279 From d076bafabbb4beac3a9fb7e1c96abe6f0d829a27 Mon Sep 17 00:00:00 2001 From: Philip Durbin Date: Wed, 17 Jun 2026 18:02:47 -0400 Subject: [PATCH 30/56] local reviews --- doc/release-notes/12313-local-reviews.md | 13 ------------- doc/release-notes/6.11-release-notes.md | 14 ++++++++++++++ 2 files changed, 14 insertions(+), 13 deletions(-) delete mode 100644 doc/release-notes/12313-local-reviews.md diff --git a/doc/release-notes/12313-local-reviews.md b/doc/release-notes/12313-local-reviews.md deleted file mode 100644 index 4ca22a784ff..00000000000 --- a/doc/release-notes/12313-local-reviews.md +++ /dev/null @@ -1,13 +0,0 @@ -### Local Reviews - -Datasets can have local reviews, listable via API. A local review is a review dataset ("review" for short) that points at the URL form of a persistent ID of a dataset (e.g. itemReviewedUrl:https://doi.org/10.5072/FK2/ABCDEF) that is in the same Dataverse installation. Local reviews of a dataset can be listed via API (and we plan to build a UI for it some day). - -A new metadata block called "Trusted Data Dimensions and Intensities" has been added for testing. This is described in the setup instructions for review datasets. - -If you set `dataverse.feature.croissant-with-local-reviews` to true, local reviews will appear in the croissant and croissantSlim metadata export formats for any dataset that has local reviews. This feature is experiemental, which is why it is hidden behind a feature flag. - -See the guides for the new [list reviews](https://preview.guides.gdcc.io/en/develop/api/native-api.html#list-reviews) API endpoint, #12313, #12314, and #12425. - -## New Settings - -- dataverse.feature.croissant-with-local-reviews diff --git a/doc/release-notes/6.11-release-notes.md b/doc/release-notes/6.11-release-notes.md index 5c8be7ce974..b002c1b4db1 100644 --- a/doc/release-notes/6.11-release-notes.md +++ b/doc/release-notes/6.11-release-notes.md @@ -9,6 +9,8 @@ This release brings new features, enhancements, and bug fixes to Dataverse. Than Highlights for Dataverse 6.11 include: - New expanded geospatial metadata block +- Local reviews +- Croissant 1.1 (summary statistics) - New and improved APIs - Bug fixes @@ -24,6 +26,16 @@ This new expanded metadata block aligns with the international ISO 19115 standar See [the guides](https://guides.dataverse.org/en/6.11/user/appendix.html#supported-metadata), #10398, and #11507. +### Local Reviews + +Datasets can have local reviews, listable via API. A local review is a review dataset ("review" for short) that points at the URL form of a persistent ID of a dataset (e.g. itemReviewedUrl:https://doi.org/10.5072/FK2/ABCDEF) that is in the same Dataverse installation. Local reviews of a dataset can be listed via API (and we plan to build a UI for it some day). + +A new metadata block called "Trusted Data Dimensions and Intensities" has been added for testing. This is described in the setup instructions for review datasets. + +If you set `dataverse.feature.croissant-with-local-reviews` to true, local reviews will appear in the croissant and croissantSlim metadata export formats for any dataset that has local reviews. This feature is experiemental, which is why it is hidden behind a feature flag. + +See the guides for the new [list reviews](https://guides.dataverse.org/en/6.11/api/native-api.html#list-reviews) API endpoint, #12313, #12314, and #12425. + ### Croissant 1.1 (Summary Statistics) The Croissant metadata export format has been updated from version 1.0 to 1.1. @@ -123,6 +135,8 @@ We fixed an inconsistency where the `CorsFilter` was not always being invoked wh ### New JVM Options (MicroProfile Config Settings) +- dataverse.feature.croissant-with-local-reviews + ### New Database Settings ## Updates for Documentation Writers From cdc767258e4e7798b9a554afa1980321f3a8624a Mon Sep 17 00:00:00 2001 From: Philip Durbin Date: Wed, 17 Jun 2026 21:58:54 -0400 Subject: [PATCH 31/56] locally fair --- doc/release-notes/12319-LocallyFAIRdata | 9 --------- doc/release-notes/6.11-release-notes.md | 8 ++++++++ 2 files changed, 8 insertions(+), 9 deletions(-) delete mode 100644 doc/release-notes/12319-LocallyFAIRdata diff --git a/doc/release-notes/12319-LocallyFAIRdata b/doc/release-notes/12319-LocallyFAIRdata deleted file mode 100644 index afbd0e26302..00000000000 --- a/doc/release-notes/12319-LocallyFAIRdata +++ /dev/null @@ -1,9 +0,0 @@ -This release includes experimental support for "Locally FAIR" data. -This feature allows publication of content that will only be visible to authorized users or groups within a Dataverse installation. -User without authorization will not see the Locally FAIR collections, datasets, or files in search results and cannot visit their -pages or access them via the Dataverse API. - -For more information, see the [Locally FAIR Data](https://guides.dataverse.org/en/latest/user/locally-fair-data.html) guide. - -New Config Option: -Whether Locally FAIR content can be created is controlled by the new `dataverse.feature.allow-locally-fair-data` feature flag. \ No newline at end of file diff --git a/doc/release-notes/6.11-release-notes.md b/doc/release-notes/6.11-release-notes.md index b002c1b4db1..bfd2b30bc60 100644 --- a/doc/release-notes/6.11-release-notes.md +++ b/doc/release-notes/6.11-release-notes.md @@ -8,12 +8,19 @@ This release brings new features, enhancements, and bug fixes to Dataverse. Than Highlights for Dataverse 6.11 include: +- Locally FAIR data - New expanded geospatial metadata block - Local reviews - Croissant 1.1 (summary statistics) - New and improved APIs - Bug fixes +### Locally FAIR Data + +This release includes experimental support for "Locally FAIR" data. When enabled, this feature allows publication of content that will only be visible to authorized users or groups within a Dataverse installation. User without authorization will not see the Locally FAIR collections, datasets, or files in search results and cannot visit their pages or access them via the Dataverse API. + +For more information, see [Locally FAIR Data](https://guides.dataverse.org/en/6.11/user/dataverse-management.html#locally-fair) in the guides and #12319. + ### New Expanded Geospatial Metadata Block This release introduces a major enhancement to geospatial data support with the addition of an expanded Geospatial Metadata Block, designed to improve how researchers describe, share, and discover geospatial datasets. @@ -135,6 +142,7 @@ We fixed an inconsistency where the `CorsFilter` was not always being invoked wh ### New JVM Options (MicroProfile Config Settings) +- dataverse.feature.allow-locally-fair-data - dataverse.feature.croissant-with-local-reviews ### New Database Settings From 1f3937ca40685d5c62acd181c614ebcd8aed756c Mon Sep 17 00:00:00 2001 From: Philip Durbin Date: Wed, 17 Jun 2026 22:02:46 -0400 Subject: [PATCH 32/56] inherited guestbooks --- doc/release-notes/12323-get-inherited-guestbooks-list-api.md | 2 -- doc/release-notes/6.11-release-notes.md | 1 + 2 files changed, 1 insertion(+), 2 deletions(-) delete mode 100644 doc/release-notes/12323-get-inherited-guestbooks-list-api.md diff --git a/doc/release-notes/12323-get-inherited-guestbooks-list-api.md b/doc/release-notes/12323-get-inherited-guestbooks-list-api.md deleted file mode 100644 index 89516d65653..00000000000 --- a/doc/release-notes/12323-get-inherited-guestbooks-list-api.md +++ /dev/null @@ -1,2 +0,0 @@ -Added 'includeInherited' to query parameters of /api/guestbooks/{ID}/list?includeInherited=true to return the Collection's Guestbooks as well as the Guestbooks of the Collections' hierarchical owners -Also removed the 'EditDataverse' permission requirement to get the list. diff --git a/doc/release-notes/6.11-release-notes.md b/doc/release-notes/6.11-release-notes.md index bfd2b30bc60..3b805ace820 100644 --- a/doc/release-notes/6.11-release-notes.md +++ b/doc/release-notes/6.11-release-notes.md @@ -106,6 +106,7 @@ The following issues were addressed in #12366: - A new query parameter (`ignoreSettingExcludeEmailFromExport`) has been added to the ["View a Dataverse Collection"](https://guides.dataverse.org/en/6.11/api/native-api.html#view-a-dataverse-collection) API (`/api/dataverses/{collectionId}`). This query parameter prevents the contact emails from being excluded when the setting `:ExcludeEmailFromExport` is set to true and the user has EditDataverse permissions. See #12194 and #12195. - All API endpoints that return information about role assignments (such as `/api/dataverses/$ID/assignments`) now include additional fields in their JSON responses: `assigneeName`, `roleDescription`, `definitionPointName`, `definitionPointType`, and `definitionPointGlobalId` (if available). See #11920. - The `/datafile/{id}/listRequests` API has been extended to show request history. See [the guides](https://guides.dataverse.org/en/6.11/api/dataaccess.html#list-file-access-requests), #8013 and #12012. +- "includeInherited" was added as a query parameter of `/api/guestbooks/{ID}/list?includeInherited=true` to return the collection's guestbooks as well as the guestbooks of the collections' hierarchical owners. Also the "EditDataverse" permission requirement to get the list was removed. See #12323 and #12326. ## Security Updates From 1c4244b1d0edc84aeee2cc80b6db2beb9a322892 Mon Sep 17 00:00:00 2001 From: Philip Durbin Date: Wed, 17 Jun 2026 22:11:44 -0400 Subject: [PATCH 33/56] submit for review --- .../12325-submit-for-review-message.md | 4 ---- doc/release-notes/6.11-release-notes.md | 13 +++++++++---- 2 files changed, 9 insertions(+), 8 deletions(-) delete mode 100644 doc/release-notes/12325-submit-for-review-message.md diff --git a/doc/release-notes/12325-submit-for-review-message.md b/doc/release-notes/12325-submit-for-review-message.md deleted file mode 100644 index b233c009fb1..00000000000 --- a/doc/release-notes/12325-submit-for-review-message.md +++ /dev/null @@ -1,4 +0,0 @@ -## Feature - -Added Submit for Review dialog disclaimer messages (similar to Publish disclaimer messages). Can be set using setting :SubmitForReviewDatasetDisclaimerText - Also added :DatasetSubmitForReviewPopupCustomText to allow for custom text to be displayed in the dialog similar to the Publish dialog diff --git a/doc/release-notes/6.11-release-notes.md b/doc/release-notes/6.11-release-notes.md index 3b805ace820..eda3ba47340 100644 --- a/doc/release-notes/6.11-release-notes.md +++ b/doc/release-notes/6.11-release-notes.md @@ -10,6 +10,7 @@ Highlights for Dataverse 6.11 include: - Locally FAIR data - New expanded geospatial metadata block +- Submit for Review improvements - Local reviews - Croissant 1.1 (summary statistics) - New and improved APIs @@ -33,6 +34,11 @@ This new expanded metadata block aligns with the international ISO 19115 standar See [the guides](https://guides.dataverse.org/en/6.11/user/appendix.html#supported-metadata), #10398, and #11507. +## Submit for Review Improvements + +- A disclaimer message and custom text can be added to the "Submit for Review" dialog, similar to Publish disclaimer messages. See [:SubmitForReviewDatasetDisclaimerText](https://preview.guides.gdcc.io/en/develop/installation/config.html#submitforreviewdatasetdisclaimertext), [:DatasetSubmitForReviewPopupCustomText](https://preview.guides.gdcc.io/en/develop/installation/config.html#datasetsubmitforreviewpopupcustomtext), #12325 and #12373. +- When `requireFilesToPublishDataset` (added in #10994 in Dataverse 6.6) is set on a collection, a dataset must contain files for the Submit for Review button to appear. As before, publishing is also prevented if no files are present. See #12258 and #12266. + ### Local Reviews Datasets can have local reviews, listable via API. A local review is a review dataset ("review" for short) that points at the URL form of a persistent ID of a dataset (e.g. itemReviewedUrl:https://doi.org/10.5072/FK2/ABCDEF) that is in the same Dataverse installation. Local reviews of a dataset can be listed via API (and we plan to build a UI for it some day). @@ -61,10 +67,6 @@ These are features that weren't already mentioned under "highlights" above. In previous releases of Dataverse, the file, dataset, and collection pages showed the .tab version of tabular files (a plain text preservation-friendly copy). This has been changed to show the original format instead (e.g. Excel, Stata, etc.). The .tab version is still available from the download menu. See #7956 and #12145. -## Submit for Review Improvements - -- When `requireFilesToPublishDataset` (added in #10994 in Dataverse 6.6) is set on a collection, a dataset must contain files for the Submit for Review button to appear. As before, publishing is also prevented if no files are present. See #12258 and #12266. - ### Show Historical File Access Requests A new button called "Show Historical Requests" checkbox has been added to the permissions page for a data file. Checking the box will show the number of times access has been granted or denied by user. See #8013 and #12012. @@ -141,6 +143,9 @@ We fixed an inconsistency where the `CorsFilter` was not always being invoked wh ## New Settings +- :DatasetSubmitForReviewPopupCustomText +- :SubmitForReviewDatasetDisclaimerText + ### New JVM Options (MicroProfile Config Settings) - dataverse.feature.allow-locally-fair-data From 4c4701702b13e5403eec5c27ec17f91e7e7a4586 Mon Sep 17 00:00:00 2001 From: Philip Durbin Date: Wed, 17 Jun 2026 22:13:53 -0400 Subject: [PATCH 34/56] guestbook timing --- doc/release-notes/12340-timing-issue-guestbook-response.md | 2 -- doc/release-notes/6.11-release-notes.md | 1 + 2 files changed, 1 insertion(+), 2 deletions(-) delete mode 100644 doc/release-notes/12340-timing-issue-guestbook-response.md diff --git a/doc/release-notes/12340-timing-issue-guestbook-response.md b/doc/release-notes/12340-timing-issue-guestbook-response.md deleted file mode 100644 index 39d40e5d3db..00000000000 --- a/doc/release-notes/12340-timing-issue-guestbook-response.md +++ /dev/null @@ -1,2 +0,0 @@ -## BUG -Timing issue fixed where user only had a few seconds instead of a minute to call the File download API after POSTing the guestbook response diff --git a/doc/release-notes/6.11-release-notes.md b/doc/release-notes/6.11-release-notes.md index eda3ba47340..e4470be018a 100644 --- a/doc/release-notes/6.11-release-notes.md +++ b/doc/release-notes/6.11-release-notes.md @@ -93,6 +93,7 @@ The following issues were addressed in #12366: - The bug "Search API doesn't return image_url after newly created dataset is published" was fixed in the following manner. The dataset thumbnail will be created automatically when a dataset is published under the following conditions: the dataset has no existing thumbnail; the dataset has image files that can be converted to a thumbnailt the Feature Flag "disable-dataset-thumbnail-autoselect" is not enabled. See #11588 and #12403. - A bug in the BagPack generator, which caused the export to fail for datasets with multiple Contact Points, of which some had no name while others did, has been fixed. See #12246. - Two guestbook API bugs were fixed. First, missing "gbrids" in the signed URL query parameter list will no longer include "&gbrids=" without a value. Second, when a user attempting to download files with a guestbook response has no API token but is authenticated by bearer token, a temporary api token will be generated with an expiration of 1 minute which is used for signing and decoding the signed URL. See #12267, #12277, and #12279 +- We fixed a timing issue fixed where user only had a few seconds instead of a minute to call the file download API after POSTing the guestbook response. See #12340 and #12341. ## Other Changes From 3d605afaf0b651099968c393cae5612863e483f6 Mon Sep 17 00:00:00 2001 From: Philip Durbin Date: Wed, 17 Jun 2026 22:15:32 -0400 Subject: [PATCH 35/56] s3 1 GB bug --- doc/release-notes/12358-enable-s3-multipart-upload.md | 1 - doc/release-notes/6.11-release-notes.md | 1 + 2 files changed, 1 insertion(+), 1 deletion(-) delete mode 100644 doc/release-notes/12358-enable-s3-multipart-upload.md diff --git a/doc/release-notes/12358-enable-s3-multipart-upload.md b/doc/release-notes/12358-enable-s3-multipart-upload.md deleted file mode 100644 index 22365fbbaec..00000000000 --- a/doc/release-notes/12358-enable-s3-multipart-upload.md +++ /dev/null @@ -1 +0,0 @@ -Fixed a defect that caused upload of files larger than 1G to fail silently for S3 storage, unless direct upload was used. \ No newline at end of file diff --git a/doc/release-notes/6.11-release-notes.md b/doc/release-notes/6.11-release-notes.md index e4470be018a..08f3b7e25cb 100644 --- a/doc/release-notes/6.11-release-notes.md +++ b/doc/release-notes/6.11-release-notes.md @@ -86,6 +86,7 @@ The following issues were addressed in #12366: ## Bug Fixes +- We fixed a defect that caused upload of files larger than 1 GB to fail silently for S3 storage, unless direct upload was used. See #12358. - Anonymous guestbook download via API using `:persistentId` was failing with a 401. This has been fixed. See #12245 and #12363. - In styled citations (CSL) author names were incorrect when the author was an organization rather than a person (the software attempted to interpret the organization's name as a first name/last name pair). This has been fixed. See #12244 and #12248. - When the "modifyRegistrationMetadata" API was used, some datasets with UTF-8 characters were beeing unnecessarily updated in DataCite. This has been resolved by switching from the DataCite MDS API to its JSON API. See the upgrade instructions below, #12070, and #12270. From 9e98b94dfe644e5a3799d141b49aa2c77bc13dfa Mon Sep 17 00:00:00 2001 From: Philip Durbin Date: Wed, 17 Jun 2026 22:19:27 -0400 Subject: [PATCH 36/56] manage guestbook APIs --- doc/release-notes/12386-manage-guestbook-apis.md | 12 ------------ doc/release-notes/6.11-release-notes.md | 1 + 2 files changed, 1 insertion(+), 12 deletions(-) delete mode 100644 doc/release-notes/12386-manage-guestbook-apis.md diff --git a/doc/release-notes/12386-manage-guestbook-apis.md b/doc/release-notes/12386-manage-guestbook-apis.md deleted file mode 100644 index ed28680720a..00000000000 --- a/doc/release-notes/12386-manage-guestbook-apis.md +++ /dev/null @@ -1,12 +0,0 @@ -## Feature - Manage Guestbook - -This feature adds 2 new APIs to help manage Guestbooks and Guestbook Responses. - - -This API allows the user to make edits to an existing Guestbook, including adding and removing Custom Guestbook Questions. - -`curl -PUT -H "X-Dataverse-key:$API_TOKEN" "$SERVER_URL/api/guestbooks/{ID}" -d "$JSON"` - -This API allows the user to retrieve Guestbook Responses for a specific Guestbook within a Collection. Optional pagination parameters can be added to limit the number of results, as this can get very large. - -`curl -H "X-Dataverse-key:$API_TOKEN" "$SERVER_URL/api/guestbooks/$ID/responses?limit10&offset=0"` diff --git a/doc/release-notes/6.11-release-notes.md b/doc/release-notes/6.11-release-notes.md index 08f3b7e25cb..3ed4b2a746a 100644 --- a/doc/release-notes/6.11-release-notes.md +++ b/doc/release-notes/6.11-release-notes.md @@ -106,6 +106,7 @@ The following issues were addressed in #12366: - New APIs have been added called [Update the Metadata and Instructions of a Template](https://guides.dataverse.org/en/6.11/api/native-api.html#update-the-metadata-and-instructions-of-a-template), [Update the License or Terms Of Use of a Template](https://guides.dataverse.org/en/6.11/api/native-api.html#update-the-license-or-terms-of-use-of-a-template), and [Update the Terms Of Access of a Template](https://guides.dataverse.org/en/6.11/api/native-api.html#update-the-terms-of-access-of-a-template). See #11912 and #12159. - A new API endpoint for getting the default contributor role of a collection was added. See [the guides](https://guides.dataverse.org/en/6.11/api/native-api.html#get-default-role-assigned-to-user-creating-a-dataset-in-a-dataverse-collection) and #12112. - A new API has been added to get citations in various formats such as EndNote, RIS, BibTeX, and CSL. Previously this functionality was only available via the UI. See [the guides](https://guides.dataverse.org/en/6.11/api/dataaccess.html#citation-get-citation-in-other-formats), #11733 and #12238. +- An API endpoint was added that allows the user to make edits to an existing Guestbook, including adding and removing custom guestbook questions: `curl -PUT -H "X-Dataverse-key:$API_TOKEN" "$SERVER_URL/api/guestbooks/{ID}" -d "$JSON"`. Another API was added that allows the user to retrieve guestbook responses for a specific guestbook within a collection. Optional pagination parameters can be added to limit the number of results, as this can get very large: `curl -H "X-Dataverse-key:$API_TOKEN" "$SERVER_URL/api/guestbooks/$ID/responses?limit10&offset=0"`. See #12386 and #12395. - The API endpoint `/api/guestbooks/{dataverseAlias}/list` can now include `"usageCount":#` and `"responseCount":#` in the response by adding the query param "includeStats=true". See [the guides](https://guides.dataverse.org/en/6.11/api/native-api.html#get-a-list-of-guestbooks-for-a-dataverse-collection), #12260, and #12269. - A new query parameter (`ignoreSettingExcludeEmailFromExport`) has been added to the ["View a Dataverse Collection"](https://guides.dataverse.org/en/6.11/api/native-api.html#view-a-dataverse-collection) API (`/api/dataverses/{collectionId}`). This query parameter prevents the contact emails from being excluded when the setting `:ExcludeEmailFromExport` is set to true and the user has EditDataverse permissions. See #12194 and #12195. - All API endpoints that return information about role assignments (such as `/api/dataverses/$ID/assignments`) now include additional fields in their JSON responses: `assigneeName`, `roleDescription`, `definitionPointName`, `definitionPointType`, and `definitionPointGlobalId` (if available). See #11920. From 5f6cb28325463630a66fe3055c2c3754d73ac7b8 Mon Sep 17 00:00:00 2001 From: Philip Durbin Date: Wed, 17 Jun 2026 22:22:54 -0400 Subject: [PATCH 37/56] remove classes --- doc/release-notes/12415-remove-testingest-class.md | 1 - doc/release-notes/12417-remove-meta-class.md | 1 - doc/release-notes/6.11-release-notes.md | 1 + 3 files changed, 1 insertion(+), 2 deletions(-) delete mode 100644 doc/release-notes/12415-remove-testingest-class.md delete mode 100644 doc/release-notes/12417-remove-meta-class.md diff --git a/doc/release-notes/12415-remove-testingest-class.md b/doc/release-notes/12415-remove-testingest-class.md deleted file mode 100644 index 8eae307f386..00000000000 --- a/doc/release-notes/12415-remove-testingest-class.md +++ /dev/null @@ -1 +0,0 @@ -Class TestIngest was removed as it was no longer being used diff --git a/doc/release-notes/12417-remove-meta-class.md b/doc/release-notes/12417-remove-meta-class.md deleted file mode 100644 index 83f3f683a83..00000000000 --- a/doc/release-notes/12417-remove-meta-class.md +++ /dev/null @@ -1 +0,0 @@ -Class Meta was removed as it was no longer being used diff --git a/doc/release-notes/6.11-release-notes.md b/doc/release-notes/6.11-release-notes.md index 3ed4b2a746a..0729fca9595 100644 --- a/doc/release-notes/6.11-release-notes.md +++ b/doc/release-notes/6.11-release-notes.md @@ -112,6 +112,7 @@ The following issues were addressed in #12366: - All API endpoints that return information about role assignments (such as `/api/dataverses/$ID/assignments`) now include additional fields in their JSON responses: `assigneeName`, `roleDescription`, `definitionPointName`, `definitionPointType`, and `definitionPointGlobalId` (if available). See #11920. - The `/datafile/{id}/listRequests` API has been extended to show request history. See [the guides](https://guides.dataverse.org/en/6.11/api/dataaccess.html#list-file-access-requests), #8013 and #12012. - "includeInherited" was added as a query parameter of `/api/guestbooks/{ID}/list?includeInherited=true` to return the collection's guestbooks as well as the guestbooks of the collections' hierarchical owners. Also the "EditDataverse" permission requirement to get the list was removed. See #12323 and #12326. +- The classes TestIngest (#12415) and Meta (#12417) were removed as they were no longer being used. ## Security Updates From f0cd7ceaa445be99babb9dcc2b3593b5ad055bf9 Mon Sep 17 00:00:00 2001 From: Philip Durbin Date: Wed, 17 Jun 2026 22:24:41 -0400 Subject: [PATCH 38/56] guestbook response parsing --- doc/release-notes/12446-fix-guestbook-response-parsing.md | 3 --- doc/release-notes/6.11-release-notes.md | 1 + 2 files changed, 1 insertion(+), 3 deletions(-) delete mode 100644 doc/release-notes/12446-fix-guestbook-response-parsing.md diff --git a/doc/release-notes/12446-fix-guestbook-response-parsing.md b/doc/release-notes/12446-fix-guestbook-response-parsing.md deleted file mode 100644 index f9102cdb260..00000000000 --- a/doc/release-notes/12446-fix-guestbook-response-parsing.md +++ /dev/null @@ -1,3 +0,0 @@ -## Bug ## - -Guestbook response parsing now allows a textarea value to be a string along with an array. diff --git a/doc/release-notes/6.11-release-notes.md b/doc/release-notes/6.11-release-notes.md index 0729fca9595..8526eb16913 100644 --- a/doc/release-notes/6.11-release-notes.md +++ b/doc/release-notes/6.11-release-notes.md @@ -112,6 +112,7 @@ The following issues were addressed in #12366: - All API endpoints that return information about role assignments (such as `/api/dataverses/$ID/assignments`) now include additional fields in their JSON responses: `assigneeName`, `roleDescription`, `definitionPointName`, `definitionPointType`, and `definitionPointGlobalId` (if available). See #11920. - The `/datafile/{id}/listRequests` API has been extended to show request history. See [the guides](https://guides.dataverse.org/en/6.11/api/dataaccess.html#list-file-access-requests), #8013 and #12012. - "includeInherited" was added as a query parameter of `/api/guestbooks/{ID}/list?includeInherited=true` to return the collection's guestbooks as well as the guestbooks of the collections' hierarchical owners. Also the "EditDataverse" permission requirement to get the list was removed. See #12323 and #12326. +- Guestbook response parsing now allows a textarea value to be a string along with an array. See #12446 and #12447. - The classes TestIngest (#12415) and Meta (#12417) were removed as they were no longer being used. ## Security Updates From eef28d182b7e3d501247b67d522da1aea2f5505d Mon Sep 17 00:00:00 2001 From: Philip Durbin Date: Wed, 17 Jun 2026 22:27:21 -0400 Subject: [PATCH 39/56] spelling --- doc/release-notes/6.11-release-notes.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/release-notes/6.11-release-notes.md b/doc/release-notes/6.11-release-notes.md index 8526eb16913..6fc6aba19fb 100644 --- a/doc/release-notes/6.11-release-notes.md +++ b/doc/release-notes/6.11-release-notes.md @@ -45,7 +45,7 @@ Datasets can have local reviews, listable via API. A local review is a review da A new metadata block called "Trusted Data Dimensions and Intensities" has been added for testing. This is described in the setup instructions for review datasets. -If you set `dataverse.feature.croissant-with-local-reviews` to true, local reviews will appear in the croissant and croissantSlim metadata export formats for any dataset that has local reviews. This feature is experiemental, which is why it is hidden behind a feature flag. +If you set `dataverse.feature.croissant-with-local-reviews` to true, local reviews will appear in the croissant and croissantSlim metadata export formats for any dataset that has local reviews. This feature is experimental, which is why it is hidden behind a feature flag. See the guides for the new [list reviews](https://guides.dataverse.org/en/6.11/api/native-api.html#list-reviews) API endpoint, #12313, #12314, and #12425. @@ -91,7 +91,7 @@ The following issues were addressed in #12366: - In styled citations (CSL) author names were incorrect when the author was an organization rather than a person (the software attempted to interpret the organization's name as a first name/last name pair). This has been fixed. See #12244 and #12248. - When the "modifyRegistrationMetadata" API was used, some datasets with UTF-8 characters were beeing unnecessarily updated in DataCite. This has been resolved by switching from the DataCite MDS API to its JSON API. See the upgrade instructions below, #12070, and #12270. - Fixed a problem with S3 direct upload to datasets which using lower- or mixed-case PID authority/identifier in the database and to datasets using an alternative identifier for file storage. See #12268. -- The bug "Search API doesn't return image_url after newly created dataset is published" was fixed in the following manner. The dataset thumbnail will be created automatically when a dataset is published under the following conditions: the dataset has no existing thumbnail; the dataset has image files that can be converted to a thumbnailt the Feature Flag "disable-dataset-thumbnail-autoselect" is not enabled. See #11588 and #12403. +- The bug "Search API doesn't return image_url after newly created dataset is published" was fixed in the following manner. The dataset thumbnail will be created automatically when a dataset is published under the following conditions: the dataset has no existing thumbnail; the dataset has image files that can be converted to a thumbnail the Feature Flag "disable-dataset-thumbnail-autoselect" is not enabled. See #11588 and #12403. - A bug in the BagPack generator, which caused the export to fail for datasets with multiple Contact Points, of which some had no name while others did, has been fixed. See #12246. - Two guestbook API bugs were fixed. First, missing "gbrids" in the signed URL query parameter list will no longer include "&gbrids=" without a value. Second, when a user attempting to download files with a guestbook response has no API token but is authenticated by bearer token, a temporary api token will be generated with an expiration of 1 minute which is used for signing and decoding the signed URL. See #12267, #12277, and #12279 - We fixed a timing issue fixed where user only had a few seconds instead of a minute to call the file download API after POSTing the guestbook response. See #12340 and #12341. @@ -264,4 +264,4 @@ Also, we assume that Payara is installed in `/usr/local/payara7`. If not, adjust `-Ddataverse.pid..datacite.rest-api-url=https://api.test.datacite.org` - See [the guides](https://guides.dataverse.org/en/6.11/installation/config.html#datacite-specific-settings), #12070 and #12270. \ No newline at end of file + See [the guides](https://guides.dataverse.org/en/6.11/installation/config.html#datacite-specific-settings), #12070 and #12270. From 6cafe015eb205bdd3818f7645e257227d82d6286 Mon Sep 17 00:00:00 2001 From: Philip Durbin Date: Wed, 17 Jun 2026 22:34:31 -0400 Subject: [PATCH 40/56] adjust highlights and other tweaks --- doc/release-notes/6.11-release-notes.md | 41 ++++++++++++------------- 1 file changed, 19 insertions(+), 22 deletions(-) diff --git a/doc/release-notes/6.11-release-notes.md b/doc/release-notes/6.11-release-notes.md index 6fc6aba19fb..036c163866c 100644 --- a/doc/release-notes/6.11-release-notes.md +++ b/doc/release-notes/6.11-release-notes.md @@ -11,8 +11,8 @@ Highlights for Dataverse 6.11 include: - Locally FAIR data - New expanded geospatial metadata block - Submit for Review improvements +- Show historical file access requests - Local reviews -- Croissant 1.1 (summary statistics) - New and improved APIs - Bug fixes @@ -34,11 +34,15 @@ This new expanded metadata block aligns with the international ISO 19115 standar See [the guides](https://guides.dataverse.org/en/6.11/user/appendix.html#supported-metadata), #10398, and #11507. -## Submit for Review Improvements +### Submit for Review Improvements - A disclaimer message and custom text can be added to the "Submit for Review" dialog, similar to Publish disclaimer messages. See [:SubmitForReviewDatasetDisclaimerText](https://preview.guides.gdcc.io/en/develop/installation/config.html#submitforreviewdatasetdisclaimertext), [:DatasetSubmitForReviewPopupCustomText](https://preview.guides.gdcc.io/en/develop/installation/config.html#datasetsubmitforreviewpopupcustomtext), #12325 and #12373. - When `requireFilesToPublishDataset` (added in #10994 in Dataverse 6.6) is set on a collection, a dataset must contain files for the Submit for Review button to appear. As before, publishing is also prevented if no files are present. See #12258 and #12266. +### Show Historical File Access Requests + +A new button called "Show Historical Requests" checkbox has been added to the permissions page for a data file. Checking the box will show the number of times access has been granted or denied by user. See #8013 and #12012. + ### Local Reviews Datasets can have local reviews, listable via API. A local review is a review dataset ("review" for short) that points at the URL form of a persistent ID of a dataset (e.g. itemReviewedUrl:https://doi.org/10.5072/FK2/ABCDEF) that is in the same Dataverse installation. Local reviews of a dataset can be listed via API (and we plan to build a UI for it some day). @@ -49,16 +53,6 @@ If you set `dataverse.feature.croissant-with-local-reviews` to true, local revie See the guides for the new [list reviews](https://guides.dataverse.org/en/6.11/api/native-api.html#list-reviews) API endpoint, #12313, #12314, and #12425. -### Croissant 1.1 (Summary Statistics) - -The Croissant metadata export format has been updated from version 1.0 to 1.1. - -Summary statistics (mean, min, max, etc.) are now included for tabular files that were successfully ingested. - -You can download an example Croissant file from the [Supported Metadata Export Formats](https://guides.dataverse.org/en/6.11/user/dataset-management.html#supported-metadata-export-formats) section of the guides. - -Minor backward-incompatible changes were made, which are noted below. See #12014 and #12214. - ## Features Added These are features that weren't already mentioned under "highlights" above. @@ -67,9 +61,15 @@ These are features that weren't already mentioned under "highlights" above. In previous releases of Dataverse, the file, dataset, and collection pages showed the .tab version of tabular files (a plain text preservation-friendly copy). This has been changed to show the original format instead (e.g. Excel, Stata, etc.). The .tab version is still available from the download menu. See #7956 and #12145. -### Show Historical File Access Requests +### Croissant 1.1 (Summary Statistics) -A new button called "Show Historical Requests" checkbox has been added to the permissions page for a data file. Checking the box will show the number of times access has been granted or denied by user. See #8013 and #12012. +The Croissant metadata export format has been updated from version 1.0 to 1.1. + +Summary statistics (mean, min, max, etc.) are now included for tabular files that were successfully ingested. + +You can download an example Croissant file from the [Supported Metadata Export Formats](https://guides.dataverse.org/en/6.11/user/dataset-management.html#supported-metadata-export-formats) section of the guides. + +Minor backward-incompatible changes were made, which are noted below. See #12014 and #12214. ### Local Contexts Improvements @@ -99,6 +99,7 @@ The following issues were addressed in #12366: ## Other Changes - A [list of Dataverse features](https://guides.dataverse.org/en/6.11/admin/features.html) has been added to the guides. See #11998 and #12000. +- The [Big Data Support](https://guides.dataverse.org/en/6.11/installation/big-data-support.html) page has been moved from the Developer Guide to the Installation Guide. See #12151. - The deaccession reason "Not a valid dataset." has been changed to "Not valid. This dataset does not comply with repository policies." See the Bundle.properties key file.deaccessionDialog.reason.selectItem.notValid and #11985. ## API Updates @@ -136,10 +137,6 @@ Generally speaking, see the [API Changelog](https://guides.dataverse.org/en/late We mentioned this in the Dataverse [6.6](https://github.com/IQSS/dataverse/releases/tag/v6.6), [6.8](https://github.com/IQSS/dataverse/releases/tag/v6.8), [6.9](https://github.com/IQSS/dataverse/releases/tag/v6.9), and [6.10](https://github.com/IQSS/dataverse/releases/tag/v6.10) release notes, but as a reminder, according to https://www.postgresql.org/support/versioning/ PostgreSQL 13 reached EOL on 13 November 2025. As stated in the [Installation Guide](https://guides.dataverse.org/en/6.11/installation/prerequisites.html#postgresql), we recommend running PostgreSQL 16 since it is the version we test with in our continuous integration ([since](https://github.com/gdcc/dataverse-ansible/commit/8ebbd84ad2cf3903b8f995f0d34578250f4223ff) February 2025). The [Dataverse 5.4 release notes](https://github.com/IQSS/dataverse/releases/tag/v5.4) explained the upgrade process from 9 to 13 (e.g. pg_dumpall, etc.) and the steps will be similar. If you have any problems, please feel free to reach out (see "getting help" in these release notes). -## Documentation Changes - -- [The Big Data Support](https://guides.dataverse.org/en/6.11/installation/big-data-support.html) page has been moved from the Developer Guide to the Installation Guide. See #12151. - ## Notes for Dataverse Installation Administrators ### CORS Filter Fix and Docs @@ -148,9 +145,6 @@ We fixed an inconsistency where the `CorsFilter` was not always being invoked wh ## New Settings -- :DatasetSubmitForReviewPopupCustomText -- :SubmitForReviewDatasetDisclaimerText - ### New JVM Options (MicroProfile Config Settings) - dataverse.feature.allow-locally-fair-data @@ -158,13 +152,16 @@ We fixed an inconsistency where the `CorsFilter` was not always being invoked wh ### New Database Settings +- :DatasetSubmitForReviewPopupCustomText +- :SubmitForReviewDatasetDisclaimerText + ## Updates for Documentation Writers The dependencies "sphinx-reredirects" and "sphinx-design" have been added. Please re-run the `pip install -r requirements.txt` setup [step](https://guides.dataverse.org/en/6.11/contributor/documentation.html#building-the-guides-with-sphinx) to update your environment. Otherwise you will see a "could not import extension" error. ## Updates for Developers -- New "fast redeploy" scripts have been added for the backend. See [the guides](https://guides.dataverse.org/en/6.11/container/dev-usage.html#fast-redeploy-command-line), #10156, and [Zulip](https://dataverse.zulipchat.com/#narrow/channel/379673-dev/topic/fast.20redeploy.20with.20docker.20compose/near/553715282). Please note that this solution is being further improved in #12467. +New "fast redeploy" scripts have been added for the backend. See [the guides](https://guides.dataverse.org/en/6.11/container/dev-usage.html#fast-redeploy-command-line), #10156, and [Zulip](https://dataverse.zulipchat.com/#narrow/channel/379673-dev/topic/fast.20redeploy.20with.20docker.20compose/near/553715282). Please note that this solution is being further improved in #12467. ## Complete List of Changes From 65aba9e535a0aa7f7cf4dcf0ca71a35f5e51a50b Mon Sep 17 00:00:00 2001 From: Philip Durbin Date: Wed, 17 Jun 2026 22:41:11 -0400 Subject: [PATCH 41/56] replace preview links with final --- doc/release-notes/6.11-release-notes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/release-notes/6.11-release-notes.md b/doc/release-notes/6.11-release-notes.md index 036c163866c..e7b0772b83b 100644 --- a/doc/release-notes/6.11-release-notes.md +++ b/doc/release-notes/6.11-release-notes.md @@ -36,7 +36,7 @@ See [the guides](https://guides.dataverse.org/en/6.11/user/appendix.html#support ### Submit for Review Improvements -- A disclaimer message and custom text can be added to the "Submit for Review" dialog, similar to Publish disclaimer messages. See [:SubmitForReviewDatasetDisclaimerText](https://preview.guides.gdcc.io/en/develop/installation/config.html#submitforreviewdatasetdisclaimertext), [:DatasetSubmitForReviewPopupCustomText](https://preview.guides.gdcc.io/en/develop/installation/config.html#datasetsubmitforreviewpopupcustomtext), #12325 and #12373. +- A disclaimer message and custom text can be added to the "Submit for Review" dialog, similar to Publish disclaimer messages. See [:SubmitForReviewDatasetDisclaimerText](https://guides.dataverse.org/en/6.11/installation/config.html#submitforreviewdatasetdisclaimertext), [:DatasetSubmitForReviewPopupCustomText](https://guides.dataverse.org/en/6.11/installation/config.html#datasetsubmitforreviewpopupcustomtext), #12325 and #12373. - When `requireFilesToPublishDataset` (added in #10994 in Dataverse 6.6) is set on a collection, a dataset must contain files for the Submit for Review button to appear. As before, publishing is also prevented if no files are present. See #12258 and #12266. ### Show Historical File Access Requests From 2c4294b485f7d962ebd0019aa03f490b0f3d4510 Mon Sep 17 00:00:00 2001 From: Philip Durbin Date: Wed, 17 Jun 2026 22:44:34 -0400 Subject: [PATCH 42/56] tweak upgrade instructions --- doc/release-notes/6.11-release-notes.md | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/doc/release-notes/6.11-release-notes.md b/doc/release-notes/6.11-release-notes.md index e7b0772b83b..e98dc1786c7 100644 --- a/doc/release-notes/6.11-release-notes.md +++ b/doc/release-notes/6.11-release-notes.md @@ -183,12 +183,20 @@ You are also very welcome to join the [Global Dataverse Community Consortium](ht Upgrading requires a maintenance window and downtime. Please plan accordingly, create backups of your database, etc. -Note: These instructions assume that you are upgrading from the immediate previous version. That is to say, you've already upgraded through all the 6.x releases and are now running Dataverse 6.10. See [tags on GitHub](https://github.com/IQSS/dataverse/tags) for a list of versions. If you are running an earlier version, the only supported way to upgrade is to progress through the upgrades to all the releases in between before attempting the upgrade to this version. +Note: These instructions assume that you are upgrading from the immediate previous version. That is to say, you've already upgraded through all the 6.x releases and are now running Dataverse 6.10.1. See [tags on GitHub](https://github.com/IQSS/dataverse/tags) for a list of versions. If you are running an earlier version, the only supported way to upgrade is to progress through the upgrades to all the releases in between before attempting the upgrade to this version. If you are running Payara as a non-root user (and you should be!), **remember not to execute the commands below as root**. By default, Payara runs as the `dataverse` user. In the commands below, we use sudo to run the commands as a non-root user. Also, we assume that Payara is installed in `/usr/local/payara7`. If not, adjust as needed. +1. List deployed applications. + + `/usr/local/payara7/bin/asadmin list-applications` + +1. Undeploy the previous version (should match "list-applications" above). + + `/usr/local/payara7/bin/asadmin undeploy dataverse-6.10.1` + 1. Deploy the Dataverse 6.11 war file. `wget https://github.com/IQSS/dataverse/releases/download/v6.11/dataverse-6.11.war` From 80df1132cd707d79846b581dd8c4b14c61329de6 Mon Sep 17 00:00:00 2001 From: Philip Durbin Date: Wed, 17 Jun 2026 22:45:33 -0400 Subject: [PATCH 43/56] typo --- doc/release-notes/6.11-release-notes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/release-notes/6.11-release-notes.md b/doc/release-notes/6.11-release-notes.md index e98dc1786c7..7ef1ea7df11 100644 --- a/doc/release-notes/6.11-release-notes.md +++ b/doc/release-notes/6.11-release-notes.md @@ -251,7 +251,7 @@ Also, we assume that Payara is installed in `/usr/local/payara7`. If not, adjust Please remember to update translations via [Dataverse language packs](https://github.com/GlobalDataverseCommunityConsortium/dataverse-language-packs). - If you have text customizations you can get the latest English files from . + If you have text customizations you can get the latest English files from . Note that deaccessionDialog.reason.selectItem.notValid was updated. See #11985. From 04635815c5f0188081ddda02ab5829cce81c99bc Mon Sep 17 00:00:00 2001 From: Philip Durbin Date: Thu, 18 Jun 2026 06:15:39 -0400 Subject: [PATCH 44/56] typos --- doc/release-notes/6.11-release-notes.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/release-notes/6.11-release-notes.md b/doc/release-notes/6.11-release-notes.md index 7ef1ea7df11..80e25f88634 100644 --- a/doc/release-notes/6.11-release-notes.md +++ b/doc/release-notes/6.11-release-notes.md @@ -41,7 +41,7 @@ See [the guides](https://guides.dataverse.org/en/6.11/user/appendix.html#support ### Show Historical File Access Requests -A new button called "Show Historical Requests" checkbox has been added to the permissions page for a data file. Checking the box will show the number of times access has been granted or denied by user. See #8013 and #12012. +A new checkbox called "Show Historical Requests" has been added to the permissions page for a data file. Checking the box will show the number of times access has been granted or denied by user. See #8013 and #12012. ### Local Reviews @@ -107,7 +107,7 @@ The following issues were addressed in #12366: - New APIs have been added called [Update the Metadata and Instructions of a Template](https://guides.dataverse.org/en/6.11/api/native-api.html#update-the-metadata-and-instructions-of-a-template), [Update the License or Terms Of Use of a Template](https://guides.dataverse.org/en/6.11/api/native-api.html#update-the-license-or-terms-of-use-of-a-template), and [Update the Terms Of Access of a Template](https://guides.dataverse.org/en/6.11/api/native-api.html#update-the-terms-of-access-of-a-template). See #11912 and #12159. - A new API endpoint for getting the default contributor role of a collection was added. See [the guides](https://guides.dataverse.org/en/6.11/api/native-api.html#get-default-role-assigned-to-user-creating-a-dataset-in-a-dataverse-collection) and #12112. - A new API has been added to get citations in various formats such as EndNote, RIS, BibTeX, and CSL. Previously this functionality was only available via the UI. See [the guides](https://guides.dataverse.org/en/6.11/api/dataaccess.html#citation-get-citation-in-other-formats), #11733 and #12238. -- An API endpoint was added that allows the user to make edits to an existing Guestbook, including adding and removing custom guestbook questions: `curl -PUT -H "X-Dataverse-key:$API_TOKEN" "$SERVER_URL/api/guestbooks/{ID}" -d "$JSON"`. Another API was added that allows the user to retrieve guestbook responses for a specific guestbook within a collection. Optional pagination parameters can be added to limit the number of results, as this can get very large: `curl -H "X-Dataverse-key:$API_TOKEN" "$SERVER_URL/api/guestbooks/$ID/responses?limit10&offset=0"`. See #12386 and #12395. +- An API endpoint was added that allows the user to make edits to an existing Guestbook, including adding and removing custom guestbook questions: `curl -X PUT -H "X-Dataverse-key:$API_TOKEN" "$SERVER_URL/api/guestbooks/{ID}" -d "$JSON"`. Another API was added that allows the user to retrieve guestbook responses for a specific guestbook within a collection. Optional pagination parameters can be added to limit the number of results, as this can get very large: `curl -H "X-Dataverse-key:$API_TOKEN" "$SERVER_URL/api/guestbooks/$ID/responses?limit10&offset=0"`. See #12386 and #12395. - The API endpoint `/api/guestbooks/{dataverseAlias}/list` can now include `"usageCount":#` and `"responseCount":#` in the response by adding the query param "includeStats=true". See [the guides](https://guides.dataverse.org/en/6.11/api/native-api.html#get-a-list-of-guestbooks-for-a-dataverse-collection), #12260, and #12269. - A new query parameter (`ignoreSettingExcludeEmailFromExport`) has been added to the ["View a Dataverse Collection"](https://guides.dataverse.org/en/6.11/api/native-api.html#view-a-dataverse-collection) API (`/api/dataverses/{collectionId}`). This query parameter prevents the contact emails from being excluded when the setting `:ExcludeEmailFromExport` is set to true and the user has EditDataverse permissions. See #12194 and #12195. - All API endpoints that return information about role assignments (such as `/api/dataverses/$ID/assignments`) now include additional fields in their JSON responses: `assigneeName`, `roleDescription`, `definitionPointName`, `definitionPointType`, and `definitionPointGlobalId` (if available). See #11920. From b72716fc3fad9da86f71394490b2a8ff59cf7176 Mon Sep 17 00:00:00 2001 From: Philip Durbin Date: Thu, 18 Jun 2026 09:41:41 -0400 Subject: [PATCH 45/56] explain more about the list of features --- doc/release-notes/6.11-release-notes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/release-notes/6.11-release-notes.md b/doc/release-notes/6.11-release-notes.md index 80e25f88634..a9bd4600594 100644 --- a/doc/release-notes/6.11-release-notes.md +++ b/doc/release-notes/6.11-release-notes.md @@ -98,7 +98,7 @@ The following issues were addressed in #12366: ## Other Changes -- A [list of Dataverse features](https://guides.dataverse.org/en/6.11/admin/features.html) has been added to the guides. See #11998 and #12000. +- A [list of Dataverse features](https://guides.dataverse.org/en/6.11/admin/features.html) has been added to the guides, thanks to the [Documentation Working Group](https://www.gdcc.io/working-groups/documentation.html) over many meetings (recorded, if you're interested!). Historically, the list of features has been maintained at [dataverse.org/software-features](https://dataverse.org/software-features) but by moving [the list](https://guides.dataverse.org/en/6.11/admin/features.html) into the guides, we hope to keep it up-to-date with help from the community. To make improvements, please feel free to open issues, make pull requests, [discuss](https://dataverse.zulipchat.com/#narrow/channel/446770-docs/topic/list.20of.20features/with/604499830) in Zulip, and join a Documentation Working Group meeting! See #11998 and #12000. - The [Big Data Support](https://guides.dataverse.org/en/6.11/installation/big-data-support.html) page has been moved from the Developer Guide to the Installation Guide. See #12151. - The deaccession reason "Not a valid dataset." has been changed to "Not valid. This dataset does not comply with repository policies." See the Bundle.properties key file.deaccessionDialog.reason.selectItem.notValid and #11985. From 0683e950007018baba3e43c881872eb0f3773150 Mon Sep 17 00:00:00 2001 From: Philip Durbin Date: Thu, 18 Jun 2026 10:01:40 -0400 Subject: [PATCH 46/56] mailchimp, thank Pablo and Josh --- doc/release-notes/6.11-release-notes.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/doc/release-notes/6.11-release-notes.md b/doc/release-notes/6.11-release-notes.md index a9bd4600594..4110af6ae3e 100644 --- a/doc/release-notes/6.11-release-notes.md +++ b/doc/release-notes/6.11-release-notes.md @@ -118,7 +118,11 @@ The following issues were addressed in #12366: ## Security Updates -This release contains important security updates. If you are not receiving security notices, please sign up by following [the steps](https://guides.dataverse.org/en/latest/installation/config.html#ongoing-security-of-your-installation) in the guides. +This release contains important security updates. If you are not receiving security advisories, please sign up by following [the steps](https://guides.dataverse.org/en/latest/installation/config.html#ongoing-security-of-your-installation) in the guides. + +As we [announced](https://groups.google.com/g/dataverse-community/c/wqSQYH_fSlA/m/6xcGh0CnAgAJ) on the mailing list, we are experimenting with sending security advisories via Mailchimp. The sign up steps are the same. + +We would like to thank Pablo Picurelli Ortiz and Josh Dow for notifying us about a vulnerabilities that was fixed in this release. ## Backward Incompatible Changes From 0e35006d5ba372d3daa65b23615774416684de98 Mon Sep 17 00:00:00 2001 From: Philip Durbin Date: Thu, 18 Jun 2026 10:03:03 -0400 Subject: [PATCH 47/56] typo --- doc/release-notes/6.11-release-notes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/release-notes/6.11-release-notes.md b/doc/release-notes/6.11-release-notes.md index 4110af6ae3e..c184f149787 100644 --- a/doc/release-notes/6.11-release-notes.md +++ b/doc/release-notes/6.11-release-notes.md @@ -122,7 +122,7 @@ This release contains important security updates. If you are not receiving secur As we [announced](https://groups.google.com/g/dataverse-community/c/wqSQYH_fSlA/m/6xcGh0CnAgAJ) on the mailing list, we are experimenting with sending security advisories via Mailchimp. The sign up steps are the same. -We would like to thank Pablo Picurelli Ortiz and Josh Dow for notifying us about a vulnerabilities that was fixed in this release. +We would like to thank Pablo Picurelli Ortiz and Josh Dow for notifying us about vulnerabilities that were fixed in this release. ## Backward Incompatible Changes From 8af905afb25022d52ef25c533417ea3de51bda97 Mon Sep 17 00:00:00 2001 From: Julian Gautier Date: Thu, 18 Jun 2026 10:35:26 -0400 Subject: [PATCH 48/56] Revise 6.11 release notes for clarity and grammar Made minor grammatical corrections throughout the release notes. --- doc/release-notes/6.11-release-notes.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/doc/release-notes/6.11-release-notes.md b/doc/release-notes/6.11-release-notes.md index c184f149787..d3bfc2f23ca 100644 --- a/doc/release-notes/6.11-release-notes.md +++ b/doc/release-notes/6.11-release-notes.md @@ -18,7 +18,7 @@ Highlights for Dataverse 6.11 include: ### Locally FAIR Data -This release includes experimental support for "Locally FAIR" data. When enabled, this feature allows publication of content that will only be visible to authorized users or groups within a Dataverse installation. User without authorization will not see the Locally FAIR collections, datasets, or files in search results and cannot visit their pages or access them via the Dataverse API. +This release includes experimental support for "Locally FAIR" data. When enabled, this feature allows publication of content that will be visible only to authorized users or groups within a Dataverse installation. Users without authorization will not see the Locally FAIR collections, datasets, or files in search results and cannot visit their pages or access them via the Dataverse API. For more information, see [Locally FAIR Data](https://guides.dataverse.org/en/6.11/user/dataverse-management.html#locally-fair) in the guides and #12319. @@ -30,7 +30,7 @@ This new expanded metadata block aligns with the international ISO 19115 standar - Includes 22 new metadata fields to provide more detailed and standardized descriptions of geospatial data (e.g. vector, raster, mixed or multi-format geospatial collections) - Incorporates and extends current metadata elements (Geographic Coverage and Geographic Bounding Box) -- Ensures backward compatibility while significantly improving metadata description capabilities. +- Ensures backward compatibility while significantly improving metadata description capabilities See [the guides](https://guides.dataverse.org/en/6.11/user/appendix.html#supported-metadata), #10398, and #11507. @@ -41,7 +41,7 @@ See [the guides](https://guides.dataverse.org/en/6.11/user/appendix.html#support ### Show Historical File Access Requests -A new checkbox called "Show Historical Requests" has been added to the permissions page for a data file. Checking the box will show the number of times access has been granted or denied by user. See #8013 and #12012. +A new checkbox called "Show Historical Requests" has been added to the permissions page for a data file. Checking the box will show the number of times each user has been granted or denied access. See #8013 and #12012. ### Local Reviews @@ -49,7 +49,7 @@ Datasets can have local reviews, listable via API. A local review is a review da A new metadata block called "Trusted Data Dimensions and Intensities" has been added for testing. This is described in the setup instructions for review datasets. -If you set `dataverse.feature.croissant-with-local-reviews` to true, local reviews will appear in the croissant and croissantSlim metadata export formats for any dataset that has local reviews. This feature is experimental, which is why it is hidden behind a feature flag. +If you set `dataverse.feature.croissant-with-local-reviews` to true, local reviews will appear in the Croissant and croissantSlim metadata export formats for any dataset that has local reviews. This feature is experimental, which is why it is hidden behind a feature flag. See the guides for the new [list reviews](https://guides.dataverse.org/en/6.11/api/native-api.html#list-reviews) API endpoint, #12313, #12314, and #12425. @@ -73,7 +73,7 @@ Minor backward-incompatible changes were made, which are noted below. See #12014 ### Local Contexts Improvements -For instances that have enabled the Local Contexts integration, Dataverse will now add rights information related to the Notices and Labels from a Local Contexts Project associated with a dataset to the metadata sent to DataCite (when using DataCite DOIs) and available in metadata exports (DataCite, OAI-ORE, and JSON). +For instances that have enabled the Local Contexts integration, Dataverse will now add rights information related to the Notices and Labels from a Local Contexts Project associated with a dataset to the metadata sent to DataCite (when using DataCite DOIs) and available in metadata exports (DataCite, OAI-ORE, and JSON). In addition, it is now possible to use non-string values in the retrieval-filtering context entries for external vocabulary scripts. This can be used to allow filtered JSON that is not valid JSON-LD to be included in the OAI_ORE JSON-LD metadata export in a way that JSON-LD parsers will accept (and not ignore/drop). The OAI_ORE export version has been updated to 1.0.3 with this change. See the [guides](https://guides.dataverse.org/en/6.11/installation/localcontexts.html#configuration) and #12224. From 3cbc3a310823ebb4511efc06d22ad7304a50ac31 Mon Sep 17 00:00:00 2001 From: Julian Gautier Date: Thu, 18 Jun 2026 17:11:57 -0400 Subject: [PATCH 49/56] Update release notes for version 6.11 Minor grammar fixes --- doc/release-notes/6.11-release-notes.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/release-notes/6.11-release-notes.md b/doc/release-notes/6.11-release-notes.md index d3bfc2f23ca..810c368e034 100644 --- a/doc/release-notes/6.11-release-notes.md +++ b/doc/release-notes/6.11-release-notes.md @@ -89,8 +89,8 @@ The following issues were addressed in #12366: - We fixed a defect that caused upload of files larger than 1 GB to fail silently for S3 storage, unless direct upload was used. See #12358. - Anonymous guestbook download via API using `:persistentId` was failing with a 401. This has been fixed. See #12245 and #12363. - In styled citations (CSL) author names were incorrect when the author was an organization rather than a person (the software attempted to interpret the organization's name as a first name/last name pair). This has been fixed. See #12244 and #12248. -- When the "modifyRegistrationMetadata" API was used, some datasets with UTF-8 characters were beeing unnecessarily updated in DataCite. This has been resolved by switching from the DataCite MDS API to its JSON API. See the upgrade instructions below, #12070, and #12270. -- Fixed a problem with S3 direct upload to datasets which using lower- or mixed-case PID authority/identifier in the database and to datasets using an alternative identifier for file storage. See #12268. +- When the "modifyRegistrationMetadata" API was used, some datasets with UTF-8 characters were being unnecessarily updated in DataCite. This has been resolved by switching from the DataCite MDS API to its JSON API. See the upgrade instructions below, #12070, and #12270. +- Fixed a problem with S3 direct upload to datasets that use lower- or mixed-case PID authority/identifier in the database and to datasets using an alternative identifier for file storage. See #12268. - The bug "Search API doesn't return image_url after newly created dataset is published" was fixed in the following manner. The dataset thumbnail will be created automatically when a dataset is published under the following conditions: the dataset has no existing thumbnail; the dataset has image files that can be converted to a thumbnail the Feature Flag "disable-dataset-thumbnail-autoselect" is not enabled. See #11588 and #12403. - A bug in the BagPack generator, which caused the export to fail for datasets with multiple Contact Points, of which some had no name while others did, has been fixed. See #12246. - Two guestbook API bugs were fixed. First, missing "gbrids" in the signed URL query parameter list will no longer include "&gbrids=" without a value. Second, when a user attempting to download files with a guestbook response has no API token but is authenticated by bearer token, a temporary api token will be generated with an expiration of 1 minute which is used for signing and decoding the signed URL. See #12267, #12277, and #12279 From 4caf9364f00130724bf70c0e8fe7335bbc047606 Mon Sep 17 00:00:00 2001 From: Philip Durbin Date: Mon, 22 Jun 2026 10:45:16 -0400 Subject: [PATCH 50/56] use machine readable name for `croissant` and `croissantSlim` `croissantSlim` is only available via API so it makes sense to show the machine readable name. --- doc/release-notes/6.11-release-notes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/release-notes/6.11-release-notes.md b/doc/release-notes/6.11-release-notes.md index 810c368e034..193b3d4161b 100644 --- a/doc/release-notes/6.11-release-notes.md +++ b/doc/release-notes/6.11-release-notes.md @@ -49,7 +49,7 @@ Datasets can have local reviews, listable via API. A local review is a review da A new metadata block called "Trusted Data Dimensions and Intensities" has been added for testing. This is described in the setup instructions for review datasets. -If you set `dataverse.feature.croissant-with-local-reviews` to true, local reviews will appear in the Croissant and croissantSlim metadata export formats for any dataset that has local reviews. This feature is experimental, which is why it is hidden behind a feature flag. +If you set `dataverse.feature.croissant-with-local-reviews` to true, local reviews will appear in the `croissant` and `croissantSlim` metadata export formats for any dataset that has local reviews. This feature is experimental, which is why it is hidden behind a feature flag. See the guides for the new [list reviews](https://guides.dataverse.org/en/6.11/api/native-api.html#list-reviews) API endpoint, #12313, #12314, and #12425. From 6b139593f05f9d6eb5ba5253cc7ba0757d4d0c43 Mon Sep 17 00:00:00 2001 From: Philip Durbin Date: Mon, 22 Jun 2026 13:26:38 -0400 Subject: [PATCH 51/56] typo --- doc/release-notes/6.11-release-notes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/release-notes/6.11-release-notes.md b/doc/release-notes/6.11-release-notes.md index 193b3d4161b..4dbed3f91ba 100644 --- a/doc/release-notes/6.11-release-notes.md +++ b/doc/release-notes/6.11-release-notes.md @@ -81,7 +81,7 @@ In addition, it is now possible to use non-string values in the retrieval-filter The following issues were addressed in #12366: -- When PID registration of persistent ids for files is enabled, Dataverse will create the handle as soon as the file is created (similarly to other persistent id providers) (issue #12174); +- When PID registration of persistent IDs for files is enabled, Dataverse will create the handle as soon as the file is created (similar to other persistent ID providers) (issue #12174); - When a new handle is created for a dataset or file that is still a draft, it will be reserved and registered, but not visible publicly. The handle will become visible and the redirects will start working once it is published. This is also in line with how DOI providers work (issue #8881). ## Bug Fixes From cdbc879e35a945937523059d26de18019761b10c Mon Sep 17 00:00:00 2001 From: Philip Durbin Date: Mon, 22 Jun 2026 13:35:17 -0400 Subject: [PATCH 52/56] add simplified instructions when the default Solr schema.xml will do --- doc/release-notes/6.11-release-notes.md | 16 ++++++++++++++-- 1 file changed, 14 insertions(+), 2 deletions(-) diff --git a/doc/release-notes/6.11-release-notes.md b/doc/release-notes/6.11-release-notes.md index 4dbed3f91ba..4f2031fb3da 100644 --- a/doc/release-notes/6.11-release-notes.md +++ b/doc/release-notes/6.11-release-notes.md @@ -223,11 +223,23 @@ Also, we assume that Payara is installed in `/usr/local/payara7`. If not, adjust Due to changes in the Solr schema (the addition of geospatial fields), updating the Solr schema and reindexing is required. - Back up your current Solr schema. + First, back up you existing `schema.xml` file. `cp /usr/local/solr/solr-9.8.0/server/solr/collection1/conf/schema.xml /usr/local/solr/solr-9.8.0/server/solr/collection1/conf/schema.xml.orig` - Run the `update-fields.sh` script that we supply. The example below shows the default path for a non-Docker installation, but adjust the path as necessary. Docker-based installations use this directory: `solr/data/data/collection1/conf/schema.xml`. + (Note that Docker-based installations use this directory: `solr/data/data/collection1/conf/schema.xml`.) + + If you do not have any custom metadata blocks, you can simply download an updated `schema.xml` file and put it into place. + + `wget https://raw.githubusercontent.com/IQSS/dataverse/v6.11/conf/solr/schema.xml` + + `cp schema.xml /usr/local/solr/solr-9.8.0/server/solr/collection1/conf` + + Reload the Solr core. + + `curl "http://localhost:8983/solr/admin/cores?action=RELOAD&core=collection1"` + + If you do have custom metadata blocks, run the `update-fields.sh` script that we supply. The example below shows the default path for a non-Docker installation, but adjust the path as necessary. `wget https://raw.githubusercontent.com/IQSS/dataverse/v6.11/conf/solr/update-fields.sh` From bbe4e89a687ba9e4ae40e5b57df42ff2717277c0 Mon Sep 17 00:00:00 2001 From: Philip Durbin Date: Mon, 22 Jun 2026 13:53:04 -0400 Subject: [PATCH 53/56] improve description of guestbook Access API bug --- doc/release-notes/6.11-release-notes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/release-notes/6.11-release-notes.md b/doc/release-notes/6.11-release-notes.md index 4f2031fb3da..8977df2bc80 100644 --- a/doc/release-notes/6.11-release-notes.md +++ b/doc/release-notes/6.11-release-notes.md @@ -87,7 +87,7 @@ The following issues were addressed in #12366: ## Bug Fixes - We fixed a defect that caused upload of files larger than 1 GB to fail silently for S3 storage, unless direct upload was used. See #12358. -- Anonymous guestbook download via API using `:persistentId` was failing with a 401. This has been fixed. See #12245 and #12363. +- When using the Access API to download files from a dataset that has a guestbook, and when using the dataset's :persistentId (rather than its database id), the returned signedUrl immediately failed with a 401 error. This bug was fixed so that the signedUrl correctly returns the files. Using the dataset's and datafile's database ids (rather than its :persistentId) was unaffected by this bug and continues to work. See #12245 and #12363. - In styled citations (CSL) author names were incorrect when the author was an organization rather than a person (the software attempted to interpret the organization's name as a first name/last name pair). This has been fixed. See #12244 and #12248. - When the "modifyRegistrationMetadata" API was used, some datasets with UTF-8 characters were being unnecessarily updated in DataCite. This has been resolved by switching from the DataCite MDS API to its JSON API. See the upgrade instructions below, #12070, and #12270. - Fixed a problem with S3 direct upload to datasets that use lower- or mixed-case PID authority/identifier in the database and to datasets using an alternative identifier for file storage. See #12268. From c0f954f468f5624ec2ae62603a4c78fb30e5fde4 Mon Sep 17 00:00:00 2001 From: Julian Gautier Date: Mon, 22 Jun 2026 14:04:23 -0400 Subject: [PATCH 54/56] Minor grammatical change Minor grammatical change --- doc/release-notes/6.11-release-notes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/release-notes/6.11-release-notes.md b/doc/release-notes/6.11-release-notes.md index 8977df2bc80..72971e6b483 100644 --- a/doc/release-notes/6.11-release-notes.md +++ b/doc/release-notes/6.11-release-notes.md @@ -87,7 +87,7 @@ The following issues were addressed in #12366: ## Bug Fixes - We fixed a defect that caused upload of files larger than 1 GB to fail silently for S3 storage, unless direct upload was used. See #12358. -- When using the Access API to download files from a dataset that has a guestbook, and when using the dataset's :persistentId (rather than its database id), the returned signedUrl immediately failed with a 401 error. This bug was fixed so that the signedUrl correctly returns the files. Using the dataset's and datafile's database ids (rather than its :persistentId) was unaffected by this bug and continues to work. See #12245 and #12363. +- When using the Access API to download files from a dataset that has a guestbook, and when using the dataset's :persistentId instead of its database id, the returned signedUrl immediately failed with a 401 error. This bug was fixed so that the signedUrl correctly returns the files. Using the dataset's and datafile's database ids, instead of its :persistentId, was unaffected by this bug and continues to work. See #12245 and #12363. - In styled citations (CSL) author names were incorrect when the author was an organization rather than a person (the software attempted to interpret the organization's name as a first name/last name pair). This has been fixed. See #12244 and #12248. - When the "modifyRegistrationMetadata" API was used, some datasets with UTF-8 characters were being unnecessarily updated in DataCite. This has been resolved by switching from the DataCite MDS API to its JSON API. See the upgrade instructions below, #12070, and #12270. - Fixed a problem with S3 direct upload to datasets that use lower- or mixed-case PID authority/identifier in the database and to datasets using an alternative identifier for file storage. See #12268. From 07e94822413b5c6dbf757bb51ce2cf0964eea241 Mon Sep 17 00:00:00 2001 From: Philip Durbin Date: Mon, 22 Jun 2026 16:01:55 -0400 Subject: [PATCH 55/56] contributors can see which API tests are failing, if any --- doc/release-notes/6.11-release-notes.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/doc/release-notes/6.11-release-notes.md b/doc/release-notes/6.11-release-notes.md index 72971e6b483..a27afbb7880 100644 --- a/doc/release-notes/6.11-release-notes.md +++ b/doc/release-notes/6.11-release-notes.md @@ -165,6 +165,8 @@ The dependencies "sphinx-reredirects" and "sphinx-design" have been added. Pleas ## Updates for Developers +Developers making pull requests against the main "dataverse" project on GitHub can now see for themselves which API tests are failing, if any. Look for a GitHub Action called "Container Integration Tests Workflow". See #9916 and #12368. + New "fast redeploy" scripts have been added for the backend. See [the guides](https://guides.dataverse.org/en/6.11/container/dev-usage.html#fast-redeploy-command-line), #10156, and [Zulip](https://dataverse.zulipchat.com/#narrow/channel/379673-dev/topic/fast.20redeploy.20with.20docker.20compose/near/553715282). Please note that this solution is being further improved in #12467. ## Complete List of Changes From 0623d8273119ad09dcfa60385062ceb2da10df7a Mon Sep 17 00:00:00 2001 From: Philip Durbin Date: Tue, 23 Jun 2026 17:14:06 -0400 Subject: [PATCH 56/56] remove suggestion that #12244 is fully fixed --- doc/release-notes/6.11-release-notes.md | 1 - 1 file changed, 1 deletion(-) diff --git a/doc/release-notes/6.11-release-notes.md b/doc/release-notes/6.11-release-notes.md index a27afbb7880..167fc13396e 100644 --- a/doc/release-notes/6.11-release-notes.md +++ b/doc/release-notes/6.11-release-notes.md @@ -88,7 +88,6 @@ The following issues were addressed in #12366: - We fixed a defect that caused upload of files larger than 1 GB to fail silently for S3 storage, unless direct upload was used. See #12358. - When using the Access API to download files from a dataset that has a guestbook, and when using the dataset's :persistentId instead of its database id, the returned signedUrl immediately failed with a 401 error. This bug was fixed so that the signedUrl correctly returns the files. Using the dataset's and datafile's database ids, instead of its :persistentId, was unaffected by this bug and continues to work. See #12245 and #12363. -- In styled citations (CSL) author names were incorrect when the author was an organization rather than a person (the software attempted to interpret the organization's name as a first name/last name pair). This has been fixed. See #12244 and #12248. - When the "modifyRegistrationMetadata" API was used, some datasets with UTF-8 characters were being unnecessarily updated in DataCite. This has been resolved by switching from the DataCite MDS API to its JSON API. See the upgrade instructions below, #12070, and #12270. - Fixed a problem with S3 direct upload to datasets that use lower- or mixed-case PID authority/identifier in the database and to datasets using an alternative identifier for file storage. See #12268. - The bug "Search API doesn't return image_url after newly created dataset is published" was fixed in the following manner. The dataset thumbnail will be created automatically when a dataset is published under the following conditions: the dataset has no existing thumbnail; the dataset has image files that can be converted to a thumbnail the Feature Flag "disable-dataset-thumbnail-autoselect" is not enabled. See #11588 and #12403.