Dataverse: v4.9.3 Release

Release date:
September 28, 2018
Previous version:
v4.9.2 (released August 8, 2018)
Magnitude:
378 Diff Delta
Contributors:
4 total committers
Data confidence:
Commits:

101 Features Released with v4.9.3

Top Contributors in v4.9.3

oscardssmith
thaorell
JayanthyChengan
pdurbin

Directory Browser for v4.9.3

We haven't yet finished calculating and confirming the files and directories changed in this release. Please check back soon.

Release Notes Published

Note: We recommend upgrading to 4.9.4, which includes a fix for a bug that prevented users from logging in using an email address. Learn more in the 4.9.4 Release Notes.

This release is focused on expanded options for handling datasets and files in Dataverse. The dataset linking feature is now available to all users, not just superusers. It is now accessible through the UI in addition to the API. Users now have the option of downloading all files in a dataset in their original file format via the Download All button, in addition to the already available "archival format" option. Installations can now configure whether or not PIDs will be minted for files. We have also made the application more stable by addressing leaks.

For the complete list of issues, see the <a href="https://github.com/IQSS/dataverse/milestone/74?closed=1">4.9.3 milestone</a> in Github.

For help with upgrading, installing, or general questions please email [email protected].

Installation:

If this is a new installation, please see our <a href=http://guides.dataverse.org/en/4.9.3/installation/>Installation Guide</a>.

Upgrade:

  1. Undeploy the previous version.
    • <glassfish install path>/glassfish4/bin/asadmin list-applications
    • <glassfish install path>/glassfish4/bin/asadmin undeploy dataverse
  2. Stop glassfish and remove the generated directory, start
    • service glassfish stop
    • remove the generated directory: rm -rf <glassfish install path>glassfish4/glassfish/domains/domain1/generated
    • service glassfish start
  3. Deploy this version.
    • <glassfish install path>/glassfish4/bin/asadmin deploy <path>dataverse-4.9.3.war
  4. Run db update script psql -U <db user> -d <db name> -f upgrade_v4.9.2_to_v4.9.3.sql
  5. Restart glassfish
  6. Replace Solr schema.xml -stop solr instance (service solr stop, depending on solr installation/OS, see http://guides.dataverse.org/en/4.9.3/installation/prerequisites.html#solr-init-script) -replace schema.xml cp /tmp/dvinstall/schema.xml /usr/local/solr/solr-7.3.0/server/solr/collection1/conf -start solr instance (service solr start, depending on solr/OS)
  7. Kick off in place reindex http://guides.dataverse.org/en/4.9.3/admin/solr-search-index.html#reindex-in-place curl -X DELETE http://localhost:8080/api/admin/index/timestamps curl http://localhost:8080/api/admin/index/continue

  8. If you are running TwoRavens as part of your Dataverse installation, please find the following line in your TwoRavens app_ddi.js file:

dataurl = dataurl+"?key="+apikey+"&gbrecs=true";

(or, if you are using an older version, it may look like this:) dataurl = dataurl+"?key="+apikey; and change it as follows: dataurl = dataurl+"?key="+apikey+"%26gbrecs=true"; (this ensures that the download counts are properly incremented for TwoRavens explore sessions, and eliminates the confusing "Warning: The request is not valid json. Check for special characters" messages that some users were seeing after the 4.8.6 upgrade)

If you are upgrading from v4.x, you must upgrade to each intermediate version before installing this version.