Merge remote-tracking branch 'IQSS/develop' into IQSS/11592-HandleFix

Author: qqmyers

doc/release-notes/11558-show-collections.md

@@ -0,0 +1,12 @@
+The Search API now supports a `show_collections` parameter for dataset results.
+When the parameter is set, each result includes a `collections` array showing the dataset’s parent and linked collections. Each entry includes `id`, `name`, and `alias`, for example:
+
+```json
+"collections": [
+  {
+    "id": 11,
+    "name": "My cool collection",
+    "alias": "dvcb50a190"
+  }
+]
+```

doc/release-notes/11645-existing-oauth-external-users-api-auth.md

@@ -0,0 +1,6 @@
+Implemented a new feature flag ``dataverse.feature.api-bearer-auth-use-oauth-user-on-id-match``, which supports the use of the new Dataverse client in instances that have historically allowed login via GitHub, ORCID, or Google. Specifically, with this flag enabled, when an OIDC bridge is configured to allow OIDC login with validation by the bridged OAuth providers, users with existing GitHub, ORCID, or Google accounts in Dataverse can log in to those accounts, thereby maintaining access to their existing content and retaining their roles.
+
+## New Settings
+
+- dataverse.feature.api-bearer-auth-use-oauth-user-on-id-match
+

doc/release-notes/11648-notifications-api-extension.md

@@ -0,0 +1,7 @@
+# getAllNotificationsForUser API extension
+
+- Extended endpoint getAllNotificationsForUser(``/notifications/all``), which now supports an optional query parameter ``inAppNotificationFormat`` which, if sent as ``true``, retrieves the fields needed to build the in-app notifications for the Notifications section of the Dataverse UI, omitting fields related to email notifications. See also #11648 and #11696.
+
+# Notifications triggered by API endpoints
+
+The addDataset and addDataverse API endpoints now trigger user notifications upon successful execution. See also #1342 and #11696.

doc/release-notes/11724-extend-list-dataverse-collection-links.md

@@ -0,0 +1 @@
+The [API for listing the collections a dataverse has been linked to](https://guides.dataverse.org/en/latest/admin/dataverses-datasets.html#list-dataverse-collection-links) (`api/dataverses/$dataverse-alias/links`) has been refactored to return a new Json format. This is a breaking API.

doc/release-notes/issue-10523.md

@@ -0,0 +1,6 @@
+
+## Developer Updates
+
+### Writing External Exporters
+
+The getDatasetFileDetails data structure now contains "directoryLabel" (file path). See #10523 and #11618.

doc/sphinx-guides/source/api/native-api.rst

@@ -6001,6 +6001,35 @@ The expected OK (200) response looks something like this:
               }
   ...
 
+This endpoint supports an optional query parameter ``inAppNotificationFormat`` which, if sent as ``true``, retrieves the fields needed to build the in-app notifications for the Notifications section of the Dataverse UI, omitting fields related to email notifications.
+
+.. code-block:: bash
+
+  curl -H "X-Dataverse-key:$API_TOKEN" "$SERVER_URL/api/notifications/all?inAppNotificationFormat=true"
+
+The expected OK (200) response looks something like this:
+
+.. code-block:: text
+
+  {
+      "status": "OK",
+      "data": {
+          "notifications": [
+              {
+                  "id": 79,
+                  "type": "CREATEACC",
+                  "displayAsRead": false,
+                  "sentTimestamp": "2025-08-08T08:00:16Z",
+                  "installationBrandName": "Your Installation Name",
+                  "userGuidesBaseUrl": "https://guides.dataverse.org",
+                  "userGuidesVersion": "6.7.1",
+                  "userGuidesSectionPath": "user/index.html"
+              }
+          ]
+      }
+  }
+  ...
+
 Get Unread Count
 ~~~~~~~~~~~~~~~~
 

doc/sphinx-guides/source/api/search.rst

@@ -29,7 +29,7 @@ type             string   Can be either "dataverse", "dataset", or "file". Multi
 subtree          string   The identifier of the Dataverse collection to which the search should be narrowed. The subtree of this Dataverse collection and all its children will be searched.  Multiple "subtree" parameters can be used to include multiple Dataverse collections. For example, https://demo.dataverse.org/api/search?q=data&subtree=birds&subtree=cats .
 sort             string   The sort field. Supported values include "name" and "date". See example under "order".
 order            string   The order in which to sort. Can either be "asc" or "desc".  For example, https://demo.dataverse.org/api/search?q=data&sort=name&order=asc
-per_page         int      The number of results to return per request. The default is 10. The max is 1000. See :ref:`iteration example <iteration-example>`.
+per_page         int      The number of results to return per request. The default is 10. The max is 1000. See :ref:`iteration example <iteration-example>`.
 start            int      A cursor for paging through search results. See :ref:`iteration example <iteration-example>`.
 show_relevance   boolean  Whether or not to show details of which fields were matched by the query. False by default. See :ref:`advanced search example <advancedsearch-example>`.
 show_facets      boolean  Whether or not to show facets that can be operated on by the "fq" parameter. False by default. See :ref:`advanced search example <advancedsearch-example>`.
@@ -41,6 +41,7 @@ metadata_fields  string   Includes the requested fields for each dataset in the
 geo_point        string   Latitude and longitude in the form ``geo_point=42.3,-71.1``. You must supply ``geo_radius`` as well. See also :ref:`geospatial-search`.
 geo_radius       string   Radial distance in kilometers from ``geo_point`` (which must be supplied as well) such as ``geo_radius=1.5``.
 show_type_counts boolean  Whether or not to include total_count_per_object_type for types: Dataverse, Dataset, and Files.
+show_collections boolean  Whether or not to include a list of Dataverse collections for each dataset search result.
 search_service   string   The name of the search service to use for this query. If omitted, the default search service will be used. For available search services, see :ref:`discovering-available-search-services`.
 ================ =======  ===========
 
@@ -794,7 +795,7 @@ Note: Configurable Search Services are an optional, experimental feature than ma
 
 Example API endpoint: https://demo.dataverse.org/api/search/services
 
-This endpoint returns a list of available search services, including their names, and display names. It also indicates the default search service. 
+This endpoint returns a list of available search services, including their names, and display names. It also indicates the default search service.
 
 Example response:
 

doc/sphinx-guides/source/installation/config.rst

@@ -3755,6 +3755,9 @@ please find all known feature flags below. Any of these flags can be activated u
     * - api-bearer-auth-use-shib-user-on-id-match
       - Allows the use of a Shibboleth user account when an identity match is found during API bearer authentication. This feature enables automatic association of an incoming IdP identity with an existing Shibboleth user account, bypassing the need for additional user registration steps. This feature only works when the feature flag ``api-bearer-auth`` is also enabled. **Caution: Enabling this flag could result in impersonation risks if (and only if) used with a misconfigured IdP.**
       - ``Off``
+    * - api-bearer-auth-use-oauth-user-on-id-match
+      - Allows the use of an OAuth user account (GitHub, Google, or ORCID) when an identity match is found during API bearer authentication. This feature enables automatic association of an incoming IdP identity with an existing OAuth user account, bypassing the need for additional user registration steps. This feature only works when the feature flag ``api-bearer-auth`` is also enabled. **Caution: Enabling this flag could result in impersonation risks if (and only if) used with a misconfigured IdP.**
+      - ``Off``
     * - avoid-expensive-solr-join
       - Changes the way Solr queries are constructed for public content (published Collections, Datasets and Files). It removes a very expensive Solr join on all such documents, improving overall performance, especially for large instances under heavy load. Before this feature flag is enabled, the corresponding indexing feature (see next feature flag) must be turned on and a full reindex performed (otherwise public objects are not going to be shown in search results). See :doc:`/admin/solr-search-index`. 
       - ``Off``