IQSS/dataverse v4.6.1

on GitHub

Overview:

This release introduces support for ORCID authentication, a file replace feature and several important enhancements:

• Support for OAuth2 remote authentication using ORCID, Google, or Github
• File replace functionality makes updating files easier
• A file version history on the file landing page
• A download URL for public files
• A reworked Log in page includes support for Remote Authentication Only mode
• Support uploading and replacing files with Native API
• Include file tags in metadata returned through the API
• Fixed a mapping bug introduced in v4.6 that prevents editing an existing map
• Fixed a request access bug affecting access to a single restricted file
• Some native API endpoint support CORS, allowing client-side Javascript code to use them (see here for native API guide - CORS enabled endpoints are labeled).

For the complete list of issues, see the 4.6.1 milestone in Github.

For help with upgrading, installing, or general questions please email support@dataverse.org.

Installation:

If this is a new installation, please see our Installation Guide.

Upgrade:

If you are upgrading from v4.x, you must upgrade to each intermediate version before installing this version. When upgrading from the previous version, you will need to do the following:

1. Undeploy the previous version.

   • /glassfish4/bin/asadmin list-applications
   • /glassfish4/bin/asadmin undeploy dataverse

2. Stop glassfish and remove the generated directory

   • service glassfish stop
   • remove the generated directory: rm -rf /usr/local/glassfish4/glassfish/domains/domain1/generated

3. If not yet present, add a jvm option to /usr/local/glassfish4/glassfish/domains/domain1/config/domain.xml to support timers, start glassfish

   • -Ddataverse.timerServer=true (note, see http://guides.dataverse.org/en/latest/admin/timers.html if using more than one server)
   • service glassfish start

4. Verify the two jhove files are in the config directory:
   For the file uploads to work properly, please follow the instructions in the README.txt file in https://github.com/IQSS/dataverse/tree/master/conf/jhove (In future version of the Dataverse the installer script will be taking care of this).

5. Deploy this version.

   • {glassfish install path}/glassfish4/bin/asadmin deploy {path}dataverse-4.6.1.war

6. Run the database update script.
   psql -U {db user} -d {db name} -f upgrade_v4.6_to_v4.6.1.sql

7. If using Shibboleth, update the configuration to work with the new Log In page
   Refer to the "Add the Shibboleth Authentication Provider to Dataverse" instructions on adding an authenticationProviders:
   http://guides.dataverse.org/en/4.6.1/installation/shibboleth.html

8. Remove old Shibboleth configuration setting :
   From the console of a server running Dataverse,
   curl -X DELETE http://localhost:8080/api/admin/settings/:ShibEnabled

9. You might want to make use of the new :DefaultAuthProvider setting if you want an auth provider other than Username/Email to be the default: http://guides.dataverse.org/en/4.6.1/installation/config.html#defaultauthprovider

If you are upgrading from v3.x, you will need to perform a migration to v4.x since our application was redesigned and the database schema are completely different. This is a significant undertaking. Please contact us (support at dataverse.org) before beginning. Also refer to our migration google group for additional support and information: https://groups.google.com/d/msgid/dataverse-migration-wg

Please note: v4.x does not currently support creating new handles though it will support existing ones. We intend to add this feature but have not yet scheduled this work.

IMPORTANT: If you are running TwoRavens with your dataverse:
Make sure the two applications are using the same version of the "pre-processed statistics" R code. Compare the 2 files:
On the TwoRavens side:
.../dataexplore/rook/preprocess/preprocess.R
On the Dataverse side:
.../applications/dataverse-4.6/WEB-INF/classes/edu/harvard/iq/dataverse/rserve/scripts/preprocess.R

If they are different, replace the Dataverse copy with the TwoRavens copy (i.e., the TwoRavens version wins!).
And, also, remove all the already-generated pre-processed fragments in your Dataverse file directory, for example:

cd [files directory]
rm -f find . -name '*.prep'

If the two copies are the same, you don't need to do any of this.
Please note that this is a temporary measure, we are working on a fix that will make the two applications resolve code version conflicts like this automatically.