v4.7.1

Overview:

This release introduces a user management view to the administrator dashboard, listing relevant user information, providing search and super user promotion/demotion functionality. A few other community requested fixes and modifications are also provided.

• Display installation users in table format.
• Provide super user toggle functionality.
• Add additional information to user table: creation time, last login, last api use.
• Open search API to not require an API key.
• Properly validate username field on account creation to prevent non-functioning accounts.
• Add Department as a dataverse category.
• Prevent the Files facet on the MyData page hanging.
• On dataset page, autofill Identifier Scheme field with ORCiD id if available/logged in.

As always, 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.1 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.1.war
4. Run the database update script.
   psql -U -d -f upgrade_v4.7_to_v4.7.1.sql
   Note: this script will also remove any partially created, not functioning user accounts that may have resulted from a bug fixed in this release of not validating username on account creation.
5. Optionally restore old behavior of requiring API tokens to use Search API.
   -Search API does not require token now but if want to preserve old behavior run command:

curl -X PUT -d true http://localhost:8080/api/admin/settings/:SearchApiRequiresToken

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