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
(Note that you likely already have the `java.base/java.io` option there, but without the `[17|]` prefix. Make sure to replace it with the version above)
366
366
367
367
Start Payara:
368
368
369
369
```shell
370
-
sudo service payara start
370
+
sudo service payara start
371
371
```
372
372
373
373
4\. Deploy this version.
374
374
375
-
-`$PAYARA/bin/asadmin deploy dataverse-6.3.war`
375
+
```shell
376
+
$PAYARA/bin/asadmin deploy dataverse-6.3.war
377
+
```
376
378
377
379
5\. For installations with internationalization:
378
380
379
381
- Please remember to update translations via [Dataverse language packs](https://github.com/GlobalDataverseCommunityConsortium/dataverse-language-packs).
380
382
381
383
6\. Restart Payara
382
384
383
-
-`service payara stop`
384
-
-`service payara start`
385
+
```shell
386
+
service payara stop
387
+
service payara start
388
+
```
385
389
386
-
7\. Update the following Metadata Blocks to reflect the incremental improvements made to the handling of core metadata fields:
390
+
7\. Update the following metadata blocks to reflect the incremental improvements made to the handling of core metadata fields:
Solr 9.4.1 is now the version recommended in our installation guides and used with automated testing. There is a known security issue in the previously recommended version 9.3.0: https://nvd.nist.gov/vuln/detail/CVE-2023-36478. While the risk of an exploit should not be significant unless the Solr instance is accessible from the outside networks (which we have always recommended against), we recommend to upgrade.
409
+
Solr 9.4.1 is now the version recommended in our Installation Guide and used with automated testing. There is a known security issue in the previously recommended version 9.3.0: https://nvd.nist.gov/vuln/detail/CVE-2023-36478. While the risk of an exploit should not be significant unless the Solr instance is accessible from outside networks (which we have always recommended against), we recommend to upgrade.
406
410
407
-
-Install solr-9.4.1 following the instructions from the Installation guide.
411
+
Install Solr 9.4.1 following the [instructions](https://guides.dataverse.org/en/6.3/installation/prerequisites.html#solr) from the Installation Guide.
408
412
409
413
The instructions in the guide suggest to use the config files from the installer zip bundle. Upgrading an existing instance, it may be easier to download them from the source tree:
8\. For installations with custom or experimental metadata blocks:
421
+
8a\. For installations with custom or experimental metadata blocks:
418
422
419
-
- Stop Solr instance (usually `service solr stop`, depending on Solr installation/OS, see the [Installation Guide](https://guides.dataverse.org/en/6.3/installation/prerequisites.html#solr-init-script))
423
+
- Stop Solr instance (usually `service solr stop`, depending on Solr installation/OS, see the [Installation Guide](https://guides.dataverse.org/en/6.3/installation/prerequisites.html#solr-init-script)).
420
424
421
-
- Run the `update-fields.sh` script that we supply, as in the example below (modify the command lines as needed to reflect the correct path of your solr installation):
- Run the `update-fields.sh` script that we supply, as in the example below (modify the command lines as needed to reflect the correct path of your Solr installation):
9\. Enable the Metadata Source facet for harvested content (Optional):
431
436
432
437
If you choose to enable this new feature, set the optional feature flag (jvm option) `dataverse.feature.index-harvested-metadata-source=true` before reindexing.
433
438
434
-
10\. Reindex Solr, if you upgraded Solr, or chose to enable any options that require a reindex:
439
+
10\. Reindex Solr, if you upgraded Solr (recommended), or chose to enable any options that require a reindex:
435
440
436
441
```shell
437
-
curl http://localhost:8080/api/admin/index
442
+
curl http://localhost:8080/api/admin/index
438
443
```
439
444
440
-
Note: if you choose to perform a migration of your `keywordValue` metadata fields (section below), that will require a reindex as well, so do that first.
445
+
Note: if you choose to perform a migration of your `keywordValue` metadata fields (section below), that will require a reindex as well, so do that first.
441
446
442
447
## Notes for Dataverse Installation Administrators
443
448
@@ -446,7 +451,7 @@ If you choose to enable this new feature, set the optional feature flag (jvm opt
446
451
You can migrate your `keywordValue` data containing URIs to the new `keywordTermURI` field.
447
452
In case of data migration, view the affected data with the following database query:
WHEREdf.datasetfieldtype_id= (SELECT id FROM datasetfieldtype WHERE name ='keywordValue')
@@ -455,7 +460,7 @@ AND value ILIKE 'http%';
455
460
456
461
If you wish to migrate your data, a database update is then necessary:
457
462
458
-
```
463
+
```sql
459
464
UPDATE datasetfield df
460
465
SET datasetfieldtype_id = (SELECT id FROM datasetfieldtype WHERE name ='keywordTermURI')
461
466
FROM datasetfieldvalue dfv
@@ -464,6 +469,6 @@ AND df.datasetfieldtype_id = (SELECT id FROM datasetfieldtype WHERE name = 'keyw
464
469
ANDdfv.value ILIKE 'http%';
465
470
```
466
471
467
-
A ['Reindex in Place'](https://guides.dataverse.org/en/latest/admin/solr-search-index.html#reindex-in-place) will be required and ReExportAll will need to be run to update the metadata exports of the dataset. Follow the directions in the [Admin Guide](http://guides.dataverse.org/en/latest/admin/metadataexport.html#batch-exports-through-the-api).
472
+
A [reindex in place](https://guides.dataverse.org/en/latest/admin/solr-search-index.html#reindex-in-place) will be required. ReExportAll will need to be run to update the metadata exports of the dataset. Follow the directions in the [Admin Guide](http://guides.dataverse.org/en/latest/admin/metadataexport.html#batch-exports-through-the-api).
0 commit comments