Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update 5.14-release-notes.md #9702

Closed
wants to merge 1 commit into from
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions doc/release-notes/5.14-release-notes.md
Original file line number Diff line number Diff line change
Expand Up @@ -91,7 +91,7 @@ OR, alternatively, you can edit the following lines in your schema.xml by hand a

8\. Run ReExportAll to update dataset metadata exports. Follow the directions in the [Admin Guide](http://guides.dataverse.org/en/5.14/admin/metadataexport.html#batch-exports-through-the-api).

## New JVM Options and MicroProfile Config Options
## New MicroProfile/JVM Config Options

The following PID provider options are now available. See the section "Changes to PID Provider JVM Settings" below for more information.

Expand All @@ -107,27 +107,27 @@ The following PID provider options are now available. See the section "Changes t
- `dataverse.pid.ezid.username`
- `dataverse.pid.ezid.password`

The following MicroProfile Config options have been added as part of [Signposting](https://signposting.org/) support. See the section "Signposting for Dataverse" for details.
The following options have been added as part of [Signposting](https://signposting.org/) support. See the section "Signposting for Dataverse" for details.

- `dataverse.signposting.level1-author-limit`
- `dataverse.signposting.level1-item-limit`

The following JVM options are descrbed in the "Creating datasets with incomplete metadata through API" section below.
The following options are described in the "Creating datasets with incomplete metadata through API" section below.

- `dataverse.api.allow-incomplete-metadata`
- `dataverse.ui.show-validity-filter`
- `dataverse.ui.allow-review-for-incomplete`

The following JVM/MicroProfile setting is for External Exporters, see "Mechanism Added for Adding External Exporters".
The following option is for External Exporters, see "Mechanism Added for Adding External Exporters".

- `dataverse.spi.export.directory`

The JVM/MicroProfile setting for handling of support emails ("Contact Email Improvements")
These options are related to handling of support emails, see "Contact Email Improvements"

- `dataverse.mail.support-email`
- `dataverse.mail.cc-support-on-contact-emails`

The JVM/MicroProfile setting for extracting a geospatial bounding box
This option is for extracting a geospatial bounding box

- `dataverse.netcdf.geo-extract-s3-direct-upload`

Expand Down