Dataverse®

Dataverse is an open source web application for sharing, citing, analyzing, and preserving research data (developed by the Data Science and Products team at the Institute for Quantitative Social Science and the Dataverse community).

dataverse.org is our home on the web and shows a map of Dataverse installations around the world, a list of features, integrations that have been made possible through REST APIs, our development roadmap, and more.

We maintain a demo site at demo.dataverse.org which you are welcome to use for testing and evaluating Dataverse.

To install Dataverse, please see our Installation Guide which will prompt you to download our latest release.

To discuss Dataverse with the community, please join our mailing list, participate in a community call, chat with us at chat.dataverse.org, or attend our annual Dataverse Community Meeting.

We love contributors! Please see our Contributing Guide for ways you can help.

Dataverse is a trademark of President and Fellows of Harvard College and is registered in the United States.

Deployment

/usr/local/glassfish4/bin/asadmin list-applications
/usr/local/glassfish4/bin/asadmin undeploy dataverse-webapp-1.0.0-SNAPSHOT
/usr/local/glassfish4/bin/asadmin deploy /dataverse/dataverse-webapp/target/dataverse-webapp-1.0.0-SNAPSHOT.war

Running integration tests

All tests:

./mvnw verify

Single test:

./mvnw verify -Dit.test=UserNotificationRepositoryIT -pl dataverse-persistence

Integration test dependencies can be started manually in order to execute integration tests through the IDE:

./mvnw docker:start -pl dataverse-webapp

Once started, all the integration tests can be run through the IDE. When finished, containers can be stopped with:

./mvnw docker:stop -pl dataverse-webapp

CI builds

CI builds can be configured with the provided Jenkinsfile. It defines the following 6 stages:

• Prepare: Just creates the image used for the build. It is based on openjdk:8u342-jdk and has been adapted to run on jenkins (jenkins user has been added)
• Build: Performs clean build of the checked out branch
• Unit tests: Executes the unit tests and collects the results
• Integration tests: Executes the integration tests and collects the results. Required docker containers (solr & postgres) are started and it's made sure that they're in the same network as the container running the tests
• Deploy: Publishes the snapshot artifacts to artifactory. This usually should only be performed on develop, but there's an option to override the check and let it execute also on other branches.
• Release: Perform the release of the current development version. The next development version will be set according to the nextDevVersion parameter (default is patch). If current version is 1.0.3-SNAPSHOT the next dev version will be:
  • patch: 1.0.4-SNAPSHOT
  • minor: 1.1.0-SNAPSHOT
  • major: 2.0.0-SNAPSHOT

All stages are parameterized and can be skipped as desired for a given jenkins job.