This release adds schema.org metadata to dataset pages for better indexing by search engines, allows downloading of dataset metadata in schema.org format, fixes a bug in publishing a dataset where affiliation is not set, and several orcid-related issues.

Add schema.org markup to dataset pages
Export dataset metadata in schema.org format and add it to download list
Fix navbar search box that was throwing errors
Fix issue where dataset without an author affiliation could not be published
Fix oauth button labels where connect button became statically typed to orcid rather than the authentication provider (thanks to Ruben Andreassen and Pete Meyer for the fix)
Fix internal server error when logging in using Google
Fix url provided in sample orcid.json file. It was not allowing user account info to be prepopulated on create
Remove default gray background in dataverse theme
Reword failed ingest error message to emphasize upload completed, only ingest failed

For the complete list of issues, see the <a href="https://github.com/IQSS/dataverse/milestone/67?closed=1">4.8.4 milestone</a> in Github.

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

Installation:

If this is a new installation, please see our <a href=http://guides.dataverse.org/en/4.8.4/installation/>Installation Guide</a>.

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. - <glassfish install path>/glassfish4/bin/asadmin list-applications - <glassfish install path>/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. - <glassfish install path>/glassfish4/bin/asadmin deploy <path>dataverse-4.8.4.war 4. Run db update script psql -U <db user> -d <db name> -f upgrade_v4.8.3_to_v4.8.4.sql 5. Restart glassfish

Note: the url provided in the v2.0 orcid.json file was slightly in error, requiring an update. Using the v2.0 orcid.json file, http://guides.dataverse.org/en/4.8.4/_downloads/orcid.json , enter the client id and secret and then update the provider information: curl -X POST -H 'Content-type: application/json' --upload-file orcid.json http://localhost:8080/api/admin/authenticationProviders After updating this information, restart glassfish.

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

TROUBLESHOOTING NOTE:

Potential issue with the PostgreSQL JDBC driver version incompatibility causing the Dataverse timer to malfunction.

Dataverse uses the EJB timer perform scheduled tasks: harvesting from remote servers and keeping the local OAI sets and metadata expor\ ts updated. We've discovered that this timer may stop working if the version of the JDBC driver used by Glassfish is no longer in sync\ with the version of the PostgreSQL database. The symptoms: if your scheduled harvests are no longer running and there are error messa\ ges in the server.log with the following lines in them:

Internal Exception: java.io.StreamCorruptedException: invalid stream header ... Exception Description: Could not deserialize object from byte array ...

it most likely means that your GDBC driver needs to be upgraded. For example, if you are running the version 9.3 of PostgresQL, make s\ ure you have the driver postgresql-9.3-1104.jdbc4.jar in your <GLASSFISH FOLDER>/glassfish/lib directory. The correct version of the d\ river for your version of PostgreSQL can be found at https://jdbc.postgresql.org/download.html. If you have an older driver in glassf\ ish/lib, stop Glassfish, remove the old driver and replace it with the new version. We recommend that you remove the entire contents o\ f <GLASSFISH FOLDER>/glassfish/domains/domain1/generated/ before starting Glassfish again.