You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Added the missing `isDefault` field to the **Get Dataset Templates** API response.
5
+
- Added the missing `fileAccessRequest` field of terms of use and access to the **Get Dataset Templates** API response.
6
+
- Added the missing `contactForAccess` field of terms of use and access to the **Get Dataset Templates** API response.
7
+
- Resolved an API **500 error** that occurred when working with templates containing custom license terms.
8
+
- Updated API behavior so templates are **no longer returned from parent dataverses** when the "Include Templates from Root" option is unchecked in the UI.
9
+
10
+
## Notifications API fixes
11
+
- Fixed API errors caused by NullPointerException when retrieving notifications without a requestor.
Copy file name to clipboardExpand all lines: doc/sphinx-guides/source/developers/deployment.rst
+7-5Lines changed: 7 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -110,14 +110,16 @@ Migrating Datafiles from Local Storage to S3
110
110
111
111
A number of pilot Dataverse installations start on local storage, then administrators are tasked with migrating datafiles into S3 or similar object stores. The files may be copied with a command-line utility such as `s3cmd <https://s3tools.org/s3cmd>`_. You will want to retain the local file hierarchy, keeping the authority (for example: 10.5072) at the bucket "root."
112
112
113
-
The below example queries may assist with updating dataset and datafile locations in the Dataverse installation's PostgresQL database. Depending on the initial version of the Dataverse Software and subsequent upgrade path, Datafile storage identifiers may or may not include a ``file://`` prefix, so you'll want to catch both cases.
113
+
The below example queries may assist with updating dataset and datafile locations in the Dataverse installation's PostgresQL database. Depending on the initial version of the Dataverse Software and subsequent upgrade path, Datafile storage identifiers may or may not include a ``file://`` prefix, so you'll want to catch both cases.
114
+
115
+
In the following queries, ``<id>://`` refers to the ``id`` you have set for the datastore in the configuration (see the :ref:`file-storage` section of the Installation Guide).
114
116
115
117
To Update Dataset Location to S3, Assuming a ``file://`` Prefix
Copy file name to clipboardExpand all lines: doc/sphinx-guides/source/installation/config.rst
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3797,6 +3797,9 @@ please find all known feature flags below. Any of these flags can be activated u
3797
3797
* - shibboleth-use-localhost
3798
3798
- A Shibboleth-using Dataverse instance needs to make network calls to the locally-running ``shibd`` service. The default behavior is to use the address configured via the ``siteUrl`` setting. There are however situations (firewalls, etc.) where localhost would be preferable.
3799
3799
- ``Off``
3800
+
* - add-local-contexts-permission-check
3801
+
- Adds a permission check to ensure that the user calling the /api/localcontexts/datasets/{id} API can edit the dataset with that id. This is currently the only use case - see https://github.com/gdcc/dataverse-external-vocab-support/tree/main/packages/local_contexts. The flag adds additional security to stop other uses, but would currently have to be used in conjunction with the api-session-auth feature flag (the security implications of which have not been fully investigated) to still allow adding Local Contexts metadata to a dataset.
3802
+
- ``Off``
3800
3803
* - enable-pid-failure-log
3801
3804
- Turns on creation of a monthly log file (logs/PIDFailures_<yyyy-MM>.log) showing failed requests for dataset/file PIDs. Can be used directly or with scripts at https://github.com/gdcc/dataverse-recipes/python/pid_reports to alert admins.
0 commit comments