v4.7

Overview:

This release provides more customization and branding options for installations, improves documentation, provides better interoperability with citation tools, and incorporates code and bug fixes contributed by the Dataverse developer community during our recent community meeting hackathon.

• Allow creating a custom homepage, header, footer, navbar logo.
• Remove the system generated word Dataverse from dataverse names, making it optional.
• Make all system notifications use the name of the root dataverse in place of the word Dataverse.
• Make About link optional, off by default, on if link is specified.
• Make default guides link be an entry point to User Guide only to allow for other installation-specific structures.
• Allow specifying guides URL and overriding guides URL versioning mechanism.
• User and API Guide improvements contributed during the community meeting. Thank you, @acme146 for your help proofreading the User Guide!
• Developer Guide improvements, updates to README.md and CONTRIBUTING.md
• Add metadata tags to dataset page to improve interoperability with citations tools: Zotero, Endnote, Altmetrics
• Redirect after log in to page of origin for Shibboleth users. Thank you @aivanov100 for pull request #3910 and @donsizemore for testing it!

Big thanks to all members of the Dataverse Community who contributed to this release by submitting suggestions, code, or other changes.

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

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

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, start
   • service glassfish stop
   • remove the generated directory: rm -rf /usr/local/glassfish4/glassfish/domains/domain1/generated
   • service glassfish start
3. Deploy this version.
   • /glassfish4/bin/asadmin deploy dataverse-4.7.war
4. Optionally run the database update script.
   Run this script if you want to preserve the word Dataverse after your current dataverse names. Uncomment the UPDATE line before running it.
   psql -U -d -f upgrade_v4.6.2_to_v4.7.sql
5. Optionally reindex all
   If you do not wish to keep Dataverse in existing dataverse names and so did not run the update script in step 4, you should reindex so that search cards reflect the new names.

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/forum/#!forum/dataverse-migration-wg

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.7/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.