Overview:
This release includes improvements to mapping tabular data via WorldMap, support for object storage using Swift, support for Handles as persistent identifiers, improvements to the guides and various bug fixes:
- Fixed classification for latitude/longitude maps
- Restored WorldMap preview modal
- Added map thumbnail to dataset page
- Remove map data that subsequently becomes restricted
- Verify WorldMap links remain valid
- Improved Geoconnect documentation based on UX review
- Support for Handles as persistent identifiers
- Support for optional cloud-based object storage using Swift, including download URLs
- Support for alternative local identifier schemes, eg. sequential numbers rather than random strings
- Allow users to upload a dataset thumbnail
- Support for non-interactive installation
- A new Style Guide section for developers, Patterns
- Updated Two Ravens documentation
- Updated Developer Guide to reflect current process
- Fixed Guestbook Response Download to properly handle records for deleted files
Big thanks to all members of the Dataverse Community who contributed to this release by submitting suggestions, code, or other changes. Special thanks to the groups from DANS and CIMMYT that worked to restore the Handles functionality in the application.
For the complete list of issues, see the 4.6.2 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.
- {glassfish install path}/glassfish4/bin/asadmin list-applications
- {glassfish install path}/glassfish4/bin/asadmin undeploy dataverse
-
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
-
Deploy this version.
- {glassfish install path}/glassfish4/bin/asadmin deploy {path}/dataverse-4.6.2.war
-
Run the database update script.
psql -U {db user} -d {db name} -f upgrade_v4.6.1_to_v4.6.2.sql -
Update the citations metadatablock:
We have made a minor update to the Citations metadata configuration: The "Related Publication" fields
will now be included on the "Create New Dataset" page. (And not just on the "Edit Metadata" page for
existing datasets. To keep your Citation metadata configuration up-to-date, re-ingest the metadata
block file supplied with the Dataverse distribution, as follows:curl http://localhost:8080/api/admin/datasetfield/load -X POST --data-binary @data/metadatablocks/citation.tsv -H "Content-type: text/tab-separated-values"
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.6.2/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.