Merge remote-tracking branch 'iqss/develop' into npe-cvoc

Author: jo-pol

.github/workflows/copy_labels.yml

@@ -6,6 +6,10 @@ on:
 
 jobs:
   copy-labels:
+    # Avoid being triggered by forks
+    if: "! github.event.pull_request.head.repo.fork && github.actor != 'dependabot[bot]'"
+    permissions:
+      pull-requests: write
     runs-on: ubuntu-latest
     name: Copy labels from linked issues
     steps:

.github/workflows/deploy_beta_testing.yml

@@ -43,6 +43,7 @@ jobs:
 
   deploy-to-payara:
     needs: build
+    if: ${{ github.repository_owner == 'IQSS' }}
     runs-on: ubuntu-latest
 
     steps:
@@ -80,10 +81,10 @@ jobs:
             APPLICATION_NAME=dataverse-backend
             ASADMIN='/usr/local/payara6/bin/asadmin --user admin'
             $ASADMIN undeploy $APPLICATION_NAME
-            $ASADMIN stop-domain
-            rm -rf /usr/local/payara6/glassfish/domains/domain1/generated
-            rm -rf /usr/local/payara6/glassfish/domains/domain1/osgi-cache
-            $ASADMIN start-domain
+            #$ASADMIN stop-domain
+            #rm -rf /usr/local/payara6/glassfish/domains/domain1/generated
+            #rm -rf /usr/local/payara6/glassfish/domains/domain1/osgi-cache
+            #$ASADMIN start-domain
             $ASADMIN deploy --name $APPLICATION_NAME $INPUT_WAR_FILE
-            $ASADMIN stop-domain
-            $ASADMIN start-domain
+            #$ASADMIN stop-domain
+            #$ASADMIN start-domain

conf/solr/solrconfig.xml

@@ -238,7 +238,7 @@
          have some sort of hard autoCommit to limit the log size.
       -->
     <autoCommit>
-      <maxTime>${solr.autoCommit.maxTime:30000}</maxTime>
+      <maxTime>${solr.autoCommit.maxTime:300000}</maxTime>
       <openSearcher>false</openSearcher>
     </autoCommit>
 

doc/release-notes/10520-datasetType-enable-licenses.md

@@ -0,0 +1,8 @@
+## Dataset Types can set available Licenses
+
+Licenses (e.g. "MIT") can now be linked to dataset types (e.g. "software") using new superuser APIs. The create Dataset Type APIs have been extended to allow you to set metadata blocks and/or licenses on the creation of a Dataset Type. 
+
+If a license is not available for a given dataset type then the Create Dataset API will prevent that license from being applied to the dataset.
+Also, the UI will only show those licenses that are available to a the dataset's dataset type.
+
+For more information, see the guides ([overview](https://dataverse-guide--11385.org.readthedocs.build/en/11385/user/dataset-management.html#dataset-types), [new APIs](https://dataverse-guide--11385.org.readthedocs.build/en/11385/api/native-api.html#set-available-licenses-for-a-dataset-type)), #10519 and #11001.

doc/release-notes/10680-Bagit-Change.md

@@ -0,0 +1,9 @@
+### Archival Bag Configuration Change
+
+Archival Bags now use the JVM option `dataverse.bagit.sourceorg.name` in generating the bag-info.txt file's "Internal-Sender-Identifier" (in addition to its use for "Source-Organization") rather than pulling the value from a deprecated `bagit.SourceOrganization` entry in Bundle.properties ("Internal-Sender-Identifier" is generated by appending " Catalog" in both cases). Sites using archival bags would not see a change if these settings were already using the same value. See #10680 and #11416.
+
+## Upgrade Instructions
+
+If you are using archival bags, be sure that the `dataverse.bagit.sourceorg.name` JVM option is set.
+
+

doc/release-notes/10941-remove-custom-guides-navbar.md

@@ -0,0 +1 @@
+Navigation across the guides has been improved. You can now click in the upper left to go "home". The navbar has been simplified with fewer links. The bottom of every page now has "Next" and "Previous" links. A "Source" link at the bottom has also been added. See #10942.

doc/release-notes/11271-edit-files-metadata-api-call

@@ -0,0 +1,5 @@
+Update File Metadata API (PR #11271)
+
+A new API endpoint has been added to allow updating file metadata for one or more files in a dataset.
+
+See the [Native API documentation](https://guides.dataverse.org/en/latest/api/native-api.html) for details on usage.

doc/release-notes/11305-export-drafts.md

@@ -0,0 +1,7 @@
+### Dataset Metadata Can Be Exported From Draft Datasets (via API)
+
+In previous versions of Dataverse, it was only possible to export metadata from published datasets. It is now possible to export metadata from draft datasets via API as long as you supply an API token that has access to the draft. As before, when exporting metadata from published datasets, only the latest published version is supported. Internal exporters have been updated to work with drafts but external exporters might need to be updated (Croissant definitely does). See "upgrade instructions" below for details. See [the guides](https://dataverse-guide--11398.org.readthedocs.build/en/11398/api/native-api.html#export-metadata-of-a-dataset-in-various-formats), #11305, and #11398.
+
+## Upgrade Instructions
+
+If you are using the Croissant exporter, [update it](https://github.com/gdcc/exporter-croissant) to version 0.1.4 or newer for compatibility with exporting drafts. Other external exporters may need to be updated as well. See https://github.com/gdcc/dataverse-exporters for a list.

doc/release-notes/11374-indexing-improvement.md

@@ -0,0 +1,5 @@
+### Solr Indexing speed improved
+
+The performance of Solr indexing has been significantly improved, particularly for datasets with many files.
+
+A new dataverse.solr.min-files-to-use-proxy microprofile setting can be used to further improve performance/lower memory requirements for datasets with many files (e.g. 500+) (defaults to Integer.MAX, disabling use of the new functionality)

doc/release-notes/11394-versionNoteBug.md

@@ -0,0 +1,3 @@
+### versionNote Bug fix
+
+An issue causing more than one edit of a versionNote to fail, when done without a page refresh, has been fixed.