Merge remote-tracking branch 'IQSS/develop' into TKLabels

Author: qqmyers

doc/release-notes/10490-COAR-Notify.md

@@ -0,0 +1,23 @@
+### Support for COAR Notify Relationship Announcement
+
+Dataverse now supports sending and receiving [Linked Data Notification ](https://www.w3.org/TR/ldn/) messages involved in the 
+[COAR Notify Relationship Announcement Workflow](https://coar-notify.net/catalogue/workflows/repository-relationship-repository/).
+
+Dataverse can send messages to configured repositories announcing that a dataset has a related publication (as defined in the dataset metadata). This may be done automatically upon publication or triggered manually by a superuser. The receiving repository may do anything with the message, with the default expectation being that the repository will create a backlink from the publication to the dataset (assuming the publication exists in the repository, admins agree the link makes sense, etc.)
+
+Conversely, Dataverse can receive notices from other configured repositories announcing relationships between their publications and datasets. If the referenced dataset exists in the Dataverse instance, a notification will be sent to users who can publish the dataset, or, optionally, only superusers who can publish the dataset. They can then decide whether to create a backlink to the publication in the dataset metadata.
+
+(Earlier releases of Dataverse had experimental support in this area that was based on message formats defined prior to finalization of the COAR Notify specification for relationship announcements.)
+
+#### New Settings/JVM Options
+
+Configuration for sending messages involves specifying the
+:COARNotifyRelationshipAnnouncementTargets and :COARNotifyRelationshipAnnouncementTriggerFields
+
+Configuration to receive messages involves specifying
+DATAVERSE_LDN_ALLOWED_HOSTS (dataverse.ldn.allowed-hosts)
+
+Notifications are sent by default to users who can publish a dataset. The option below can be used to restrict notifications to superusers who can publish the dataset.
+ 
+DATAVERSE_COAR_NOTIFY_RELATIONSHIP_ANNOUNCEMENT_NOTIFY_SUPERSUSERS_ONLY
+

doc/release-notes/11695-11940-change-api-get-storage-driver.md

@@ -0,0 +1,12 @@
+## Get Dataset/Dataverse Storage Driver API
+
+### Changed Json response - breaking change!
+
+The API for getting the Storage Driver info has been changed/extended.
+/api/datasets/{identifier}/storageDriver
+/api/admin/dataverse/{dataverse-alias}/storageDriver
+Rather than returning just the name/id of the driver (with the key "message"), the api call now returns a JSONObject with the driver's "name", "type" and "label", and booleans indicating whether the driver has "directUpload", "directDownload", and/or "uploadOutOfBand" enabled.
+
+This change also affects the /api/admin/dataverse/{dataverse-alias}/storageDriver api call. In addition, this call now supports an optional ?getEffective=true to find the effective storageDriver (the driver that will be used for new datasets in the collection)
+
+See also [the guides](https://dataverse-guide--11664.org.readthedocs.build/en/11664/api/native-api.html#configure-a-dataset-to-store-all-new-files-in-a-specific-file-store), #11695, and #11664.

doc/release-notes/11695-change-api-get-storage-driver.md

@@ -0,0 +1,21 @@
+## Notifications API Update
+
+**Endpoint:** `notifications/all`
+
+**Enhancements:**
+
+* When the query parameter `inAppNotificationFormat=true` is set:
+
+    * Notifications of types:
+
+        * `REQUESTFILEACCESS`
+        * `REQUESTEDFILEACCESS`
+        * `GRANTFILEACCESS`
+        * `REJECTFILEACCESS`
+
+  now return both the **dataset display name** and **dataset persistent identifier**.
+
+    * Notifications of type `DATASETMENTIONED` now return a **formatted JSON** in the `additionalInfo` field when this field contains a valid persisted JSON string, instead of a raw JSON string.
+
+Related issue: #11804
+Related PR: #11851

doc/release-notes/11804-notifications-api-updates.md

@@ -0,0 +1 @@
+This release adds database indexes on GuestbookResponse and DatasetMetrtics, speeding up Dataset deletes. It also adds a constraint preventing null VersionState, as a matter of good housekeeping practice. 

doc/release-notes/11828-unacceptable-performance-deleting-datasets.md

@@ -0,0 +1,3 @@
+### Big Data Admin Section
+
+- A new section - Scaling Dataverse with Data Size - has been added to the Admin Guide. It is intended to help administrators configure Dataverse appropriately to handle larger amounts of data.

doc/release-notes/11850-big-data-admin-guide.md

@@ -0,0 +1,72 @@
+## Notifications API Update
+
+**Endpoint:** `notifications/all`
+
+The user notifications endpoint has been enhanced with new optional query parameters to allow for more specific and
+efficient data retrieval.
+
+**1. Filter by Unread Status**
+
+You can now fetch only unread notifications by using the `onlyUnread` boolean parameter.
+
+* **`onlyUnread`**: (Optional, boolean) When set to `true`, the API will only return notifications that the user has not
+  yet marked as read.
+
+**Example:**
+
+```bash
+curl -H "X-Dataverse-key:$API_TOKEN" "$SERVER_URL/api/notifications/all?onlyUnread=true"
+```
+
+**2. Pagination Support**
+
+Pagination is now supported through the limit and offset parameters, allowing you to retrieve notifications in smaller,
+manageable chunks.
+
+- **`limit`**: (Optional, integer) Specifies the maximum number of notifications to return.
+
+- **`offset`**: (Optional, integer) Specifies the number of notifications to skip before starting to return results.
+
+Example (Retrieve notifications 11 through 20):
+
+```bash
+curl -H "X-Dataverse-key:$API_TOKEN" "$SERVER_URL/api/notifications/all?limit=10&offset=10"
+```
+
+**3 Breaking Change: API Response Format Updated**
+
+To support pagination and improve consistency across the API, the JSON response format for this endpoint has been
+changed. This is a breaking change and will require updates to any client code currently using this endpoint.
+
+**Old Format:**
+
+Previously, the response nested the notification list inside a notifications object within the data field.
+
+```
+{
+  "status": "OK",
+  "data": {
+    "notifications": [
+      / ... /
+    ]
+  }
+}
+```
+
+**New Format:**
+
+The response now includes a top-level totalCount field (required for pagination) and places the notification list
+directly in the data field. This flattens the structure and makes it consistent with other paginated endpoints.
+
+```
+{
+  "status": "OK",
+  "totalCount": 2,
+  "data": [
+    / ... /  
+  ]
+}
+```
+
+Related issue: #11852
+Related PR: #11854

doc/release-notes/11852-notifications-api-pagination-and-only-unread.md

@@ -0,0 +1,5 @@
+### External Vocabulary Mechanism enhancement
+
+- The external vocabulary mechanism (see https://github.com/gdcc/dataverse-external-vocab-support/) now supports 
+  assigning metadatablock dataset field types of fieldType textbox (multiline inputs) as managed fields. This new functionality is
+  being leveraged to support automated generation of citation text for Related Publications entries. (a url could be added once the work in the external vocabulary repo is done).

doc/release-notes/11954-CVoC-for-textarea-inputs.md

@@ -0,0 +1,4 @@
+It is now possible to define storage quotas on individual datasets. See the API guide for more information.
+The practical use case is for datasets in the top-level, root collection. This does not address the use case of a user creating multiple datasets. But there is an open dev. issue for adding per-user storage quotas as well.
+
+A convenience API `/api/datasets/{id}/uploadlimits` has been added to show the remaining storage and/or number of files quotas, if present.

doc/release-notes/11987-storage-quotas-on-datasets.md

@@ -0,0 +1,5 @@
+### Bug Fix
+
+Editing a controlled vocabulary field (i.e. one with values specified in the field's metadatablock) that only allows a single selection would also update the value in the prior published version if (and only if) the edit was made starting from the published version (versus an existing draft). This is now fixed.
+The bug appears to be 11+ years old and previously unreported. As the value in the database was overwritten, there is no simple way to detect if/when this occurred without looking at backups or archival file copies. 
+