Skip to content

v4.6
Compare
Choose a tag to compare
@kcondon kcondon released this 13 Dec 19:30
· 21577 commits to master since this release
v4.6
c913662

Overview:

This release introduces a new File Landing Page and several important enhancements:

  • Introduce a new File Landing Page
  • Improve Deaccession Behavior
  • API clean up
  • OAI-PMH compliance improvements
  • Optionally support SHA1 in place of MD5 checksum
  • Fix an important issue with Request Access workflow
  • Improve File Upload behavior, particularly drag and drop
  • Document how to run Dataverse with SELinux enabled

For the complete list of issues, see the 4.6 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
  4. Deploy this version.
    • /glassfish4/bin/asadmin deploy dataverse-4.6.war
  5. Run the database update script.
    psql -U -d -f upgrade_v4.5.1_to_v4.6.sql
  6. Update tool tip in metadata block.
    • Download the attached, latest social science metadata block file (social_science.tsv) to your glassfish server:
    • Update metadata block with latest .tsv file. From glassfish server in directory where .tsv was downloaded:
  7. Update schema.xml.
    • Stop running solr process (kill -9 )
    • Replace current schema.xml file with latest attached version.
    • Restart solr (java -jar start.jar &)
  8. Run incremental index.

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.

Assets 7