Overview:
The main feature of this release is the restoration of the IP Groups functionality. Additional features include email verification, dynamic copyright in the page footer, and support for Piwik.
- #700 IP groups in Dataverse are a way to specify a certain IP address range so that permissions can be applied based on the user's location or the device used to access the application. This is useful for installations that want to allow traffic from certain networks.
- #2170 Email verification encourages new users to confirm their account email address.
- #2905 Dynamic copyright automatically keeps the copyright date current and allows installations to add information about their organization.
- #3018 Piwik support provides an alternative to Google Analytics, that supports local collection and hosting of usage metrics.
Special thanks to Jeremy Richard from Sciences Po who contributed the Piwik support feature.
For the complete list of issues, see the 4.5.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:
- Undeploy the previous version.
- /glassfish4/bin/asadmin list-applications
- /glassfish4/bin/asadmin undeploy dataverse
- Stop glassfish and remove the generated directory
- service glassfish stop
- remove the generated directory: rm -rf /usr/local/glassfish4/glassfish/domains/domain1/generated
- If not yet present, add a jvm option to /usr/local/glasssfish4/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
- Deploy this version.
- /glassfish4/bin/asadmin deploy dataverse-4.5.1.war
- Run the database update script.
"psql -U -d -f upgrade_v4.5_to_4.5.1.sql"
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.5.1/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.