The Data Explorer combines the previous Data Curation Tool and Data Explorer, built for use with the open-source Dataverse data repository. Data Explorer connects to Dataverse repository tabular data files and enables open metadata discovery and exploration of data such as visualizing charts, statistical analysis and cross tabulations, as well as authorized curation and permission controls for editing and curation of variable metadata such as labels, questions, universe, notes, weights, plus. Any DDI compliant metadata can be adapted for use with this tool, and any stand-alone component is built to complement The Dataverse Project. The Data Curation tool options, now built into Data Explorer, are integrated into Dataverse for .tab files under the configure button.
Data Explorer is an Angular application.
- 🌍 Connect to Dataverse repositories
- 📊 Visualize data with charts and tables
- 📊 Create cross tabulations
- 📈 Create cross charts
- 📝 Edit variable metadata
- 📝 Import DDI XML for curation workflows
A demo of the tool is available here; note that this Github pages demo is not recommended for use in a production environment: https://scholarsportal.github.io/Dataverse-Data-Explorer/?dfId=127759&siteUrl=https://borealisdata.ca.
- NodeJS (runtime for Angular and client)
- Angular CLI (client framework)
-
Clone the repository
git clone https://github.com/scholarsportal/Dataverse-Data-Explorer.git
-
Change to the project directory
cd ./Dataverse-Data-Explorer -
Install dependencies
npm install- Run the development server
ng serveYou can customize the dataverse instance name in the en.json (make sure to update the other language files as well).
Integrating Data Explorer in your institution? See the Dataverse guide for more information about installing external tools.
You can serve the Data Explorer app like you would any other website.
Use ng build to get the dist directory, and serve the dist directly using Apache, Nginx, or whatever server you use.
Note
You can also deploy this via docker.
The tool has a state divided into three distinct state groups.
The XML State is the final DDI file that will be uploaded to Dataverse.
The Dataset State contains information about operations being operated on the dataset (upload and download status), any extra information gained from an API call (variable cross tab data), as well as imported file information.
The UI state represents any UI changes, including any temporary visual changes to the dataset (invalid values in the chart modal).
