External Tools¶
External tools can provide additional features that are not part of the Dataverse Software itself, such as data file previews, visualization, and curation.
Contents:
Inventory of External Tools¶
Tool |
Type |
Scope |
Description |
---|---|---|---|
TwoRavens |
explore |
file |
A system of interlocking statistical tools for data exploration, analysis, and meta-analysis: http://2ra.vn. See the TwoRavens: Tabular Data Exploration section of the User Guide for more information on TwoRavens from the user perspective and the TwoRavens section of the Installation Guide. |
Data Explorer |
explore |
file |
A GUI which lists the variables in a tabular data file allowing searching, charting and cross tabulation analysis. See the README.md file at https://github.com/scholarsportal/dataverse-data-explorer-v2 for the instructions on adding Data Explorer to your Dataverse. |
Whole Tale |
explore |
dataset |
A platform for the creation of reproducible research packages that allows users to launch containerized interactive analysis environments based on popular tools such as Jupyter and RStudio. Using this integration, Dataverse users can launch Jupyter and RStudio environments to analyze published datasets. For more information, see the Whole Tale User Guide. |
File Previewers |
explore |
file |
A set of tools that display the content of files - including audio, html, Hypothes.is annotations, images, PDF, text, video, tabular data, and spreadsheets - allowing them to be viewed without downloading. The previewers can be run directly from github.io, so the only required step is using the Dataverse API to register the ones you want to use. Documentation, including how to optionally brand the previewers, and an invitation to contribute through github are in the README.md file. Initial development was led by the Qualitative Data Repository and the spreasdheet previewer was added by the Social Sciences and Humanities Open Cloud (SSHOC) project. https://github.com/GlobalDataverseCommunityConsortium/dataverse-previewers |
Data Curation Tool |
configure |
file |
A GUI for curating data by adding labels, groups, weights and other details to assist with informed reuse. See the README.md file at https://github.com/scholarsportal/Dataverse-Data-Curation-Tool for the installation instructions. |
Managing External Tools¶
Adding External Tools to a Dataverse Installation¶
To add an external tool to your Dataverse installation you must first download a JSON file for that tool, which we refer to as a “manifest”. It should look something like this:
{
"displayName": "Fabulous File Tool",
"description": "Fabulous Fun for Files!",
"toolName": "fabulous",
"scope": "file",
"types": [
"explore",
"preview"
],
"toolUrl": "https://fabulousfiletool.com",
"contentType": "text/tab-separated-values",
"toolParameters": {
"queryParameters": [
{
"fileid": "{fileId}"
},
{
"key": "{apiToken}"
}
]
}
}
Go to Inventory of External Tools and download a JSON manifest for one of the tools by following links in the description to installation instructions.
Configure the tool with the curl command below, making sure to replace the fabulousFileTool.json
placeholder for name of the JSON manifest file you downloaded.
curl -X POST -H 'Content-type: application/json' http://localhost:8080/api/admin/externalTools --upload-file fabulousFileTool.json
Listing All External Tools in a Dataverse Installation¶
To list all the external tools that are available in a Dataverse installation:
curl http://localhost:8080/api/admin/externalTools
Showing an External Tool in a Dataverse Installation¶
To show one of the external tools that are available in a Dataverse installation, pass its database id:
export TOOL_ID=1
curl http://localhost:8080/api/admin/externalTools/$TOOL_ID
Removing an External Tool From a Dataverse Installation¶
Assuming the external tool database id is “1”, remove it with the following command:
export TOOL_ID=1
curl -X DELETE http://localhost:8080/api/admin/externalTools/$TOOL_ID
Testing External Tools¶
Once you have added an external tool to your Dataverse installation, you will probably want to test it to make sure it is functioning properly.
File Level vs. Dataset Level¶
File level tools are specific to the file type (content type or MIME type). For example, a tool may work with PDFs, which have a content type of “application/pdf”.
In contrast, dataset level tools are always available no matter what file types are within the dataset.
File Level Explore Tools¶
File level explore tools provide a variety of features from data visualization to statistical analysis.
For each supported file type, file level explore tools appear in the file listing of the dataset page as well as under the “Access” button on each file page.
File Level Preview Tools¶
File level preview tools allow the user to see a preview of the file contents without having to download it.
When a file has a preview available, a preview icon will appear next to that file in the file listing on the dataset page. On the file page itself, the preview will appear in a Preview tab either immediately or once a guestbook has been filled in or terms, if any, have been agreed to.
File Level Configure Tools¶
File level configure tools are only available when you log in and have write access to the file. The file type determines if a configure tool is available. For example, a configure tool may only be available for tabular files.
Dataset Level Explore Tools¶
Dataset level explore tools allow the user to explore all the files in a dataset.
Dataset Level Configure Tools¶
Configure tools at the dataset level are not currently supported.
Writing Your Own External Tool¶
If you plan to write a external tool, see the Building External Tools section of the API Guide.
If you have an idea for an external tool, please let the Dataverse Project community know by posting about it on the dataverse-community mailing list: https://groups.google.com/forum/#!forum/dataverse-community