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
Bug fixed for the ``incomplete metadata`` label being shown for published dataset with incomplete metadata in certain scenarios. This label will now be shown for draft versions of such datasets and published datasets that the user can edit. This label can also be made invisible for published datasets (regardless of edit rights) with the new option ``dataverse.ui.show-validity-label-when-published`` set to `false`.
Changed ``api/dataverses/{id}/metadatablocks`` so that setting the query parameter ``onlyDisplayedOnCreate=true`` also returns metadata blocks with dataset field type input levels configured as required on the General Information page of the collection, in addition to the metadata blocks and their fields with the property ``displayOnCreate=true`` (which was the original behavior).
2
+
3
+
A new endpoint ``api/dataverses/{id}/inputLevels`` has been created for updating the dataset field type input levels of a collection via API.
Copy file name to clipboardExpand all lines: doc/release-notes/6.2-release-notes.md
+8-4
Original file line number
Diff line number
Diff line change
@@ -417,12 +417,16 @@ In the following commands we assume that Payara 6 is installed in `/usr/local/pa
417
417
418
418
As noted above, deployment of the war file might take several minutes due a database migration script required for the new storage quotas feature.
419
419
420
-
6\. Restart Payara
420
+
6\. For installations with internationalization:
421
+
422
+
- Please remember to update translations via [Dataverse language packs](https://github.com/GlobalDataverseCommunityConsortium/dataverse-language-packs).
423
+
424
+
7\. Restart Payara
421
425
422
426
-`service payara stop`
423
427
-`service payara start`
424
428
425
-
7\. Update the following Metadata Blocks to reflect the incremental improvements made to the handling of core metadata fields:
429
+
8\. Update the following Metadata Blocks to reflect the incremental improvements made to the handling of core metadata fields:
Copy file name to clipboardExpand all lines: doc/sphinx-guides/source/api/native-api.rst
+40-1
Original file line number
Diff line number
Diff line change
@@ -898,7 +898,46 @@ The following attributes are supported:
898
898
* ``filePIDsEnabled`` ("true" or "false") Restricted to use by superusers and only when the :ref:`:AllowEnablingFilePIDsPerCollection <:AllowEnablingFilePIDsPerCollection>` setting is true. Enables or disables registration of file-level PIDs in datasets within the collection (overriding the instance-wide setting).
899
899
900
900
.. _collection-storage-quotas:
901
-
901
+
902
+
Update Collection Input Levels
903
+
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
904
+
905
+
Updates the dataset field type input levels in a collection.
906
+
907
+
Please note that this endpoint overwrites all the input levels of the collection page, so if you want to keep the existing ones, you will need to add them to the JSON request body.
908
+
909
+
If one of the input levels corresponds to a dataset field type belonging to a metadata block that does not exist in the collection, the metadata block will be added to the collection.
910
+
911
+
This endpoint expects a JSON with the following format::
Even when you do not allow incomplete metadata to be saved in dataverse, some metadata may end up being incomplete, e.g., after making a metadata field mandatory. Datasets where that field is
2954
+
not filled out, become incomplete, and therefore can be labeled with the ``incomplete metadata`` label. By default, this label is only shown for draft datasets and published datasets that the
2955
+
user can edit. This option can be disabled by setting it to ``false`` where only draft datasets with incomplete metadata will have that label. When disabled, all published dataset will not have
2956
+
that label. Note that you need to reindex the datasets after changing the metadata definitions. Reindexing will update the labels and other dataset information according to the new situation.
2957
+
2958
+
When enabled (by default), published datasets with incomplete metadata will have an ``incomplete metadata`` label attached to them, but only for the datasets that the user can edit.
2959
+
You can list these datasets, for example, with the validity of metadata filter shown in "My Data" page that can be turned on by enabling the :ref:`dataverse.ui.show-validity-filter` option.
2960
+
2961
+
Defaults to ``true``.
2962
+
2963
+
Can also be set via any `supported MicroProfile Config API source`_, e.g. the environment variable
2964
+
``DATAVERSE_API_SHOW_LABEL_FOR_INCOMPLETE_WHEN_PUBLISHED``. Will accept ``[tT][rR][uU][eE]|1|[oO][nN]`` as "true" expressions.
2965
+
2948
2966
.. _dataverse.signposting.level1-author-limit:
2949
2967
2950
2968
dataverse.signposting.level1-author-limit
@@ -3142,6 +3160,8 @@ Defaults to ``false``.
3142
3160
Can also be set via any `supported MicroProfile Config API source`_, e.g. the environment variable
3143
3161
``DATAVERSE_UI_ALLOW_REVIEW_FOR_INCOMPLETE``. Will accept ``[tT][rR][uU][eE]|1|[oO][nN]`` as "true" expressions.
0 commit comments