Roadmap: The Dataverse Project

dataverse project logo

The Strategic Goals of the Dataverse Project are our highest-level guide.  These goals are to:

  • increase adoption (users, Dataverse repositories, Dataverse collections, datasets, journals)
  • develop capability to handle sensitive, large scale, and streaming data
  • expand data and metadata features for existing and new disciplines
  • expand archival and preservation features
  • increase interoperability through implementation of standards
  • increase contributions from the open-source development community
  • improve UX and UI
  • continue to increase the quality of the software

Throughout the year, we'll identify big steps that we can take to focus on one or more of these goals. These big steps are detailed on our Roadmap, below.

The big things the development team and the community are working on right now are shown in the Implementation section. In the Planning/Design section, you can see those strategic items that we've prioritized and are designing and testing with the community. In the Future section, you'll see the things that we'd like to work on but haven't yet prioritized. A list of Recent Releases is available at the bottom of the page. 

This roadmap is only focused on the big initiatives. We're always working on smaller bug fixes and enhancements. If you'd like to see everything that the Dataverse Project Team and Community are working on right now, check out the Project Board on Github.

Implementation

Q1 2022 Continued Dataset and File Redesign

  • A new experience around downloading and accessing data will be provided as part of the continued redesign of the dataset and file pages. This follows the adding of previewers, filtering and sorting, and tree views on the dataset and file pages. 
  • Github Issue #6684

Q1 2022 Mutiple Licenses

  • Authors will be able to create dataset and file metadata in a Dataverse collection and set up a timed-release process for the individual data files. Work supported by Data Archiving and Networked Services (DANS-KNAW), the Netherlands.
  • Github Issue #7440

Planning/Design

Q1 2022 Simplified Add Data, Linking, and Dataverse Collection Creation Workflows

  • By making it easier to create Dataverse collections and link datasets, researchers can more easily create and curate custom collections of data.
  • Github Issue #5874#5890#5615

Q1 2022 Globus Integration

  • Researchers will be able to use Globus to transfer files into Dataverse installation storage, or create a metadata record in a Dataverse installation for discovery while making the data itself available at a Globus endpoint.
  • Github Issue #5994#7626

Q1 2022 Trusted Remote Storage Agent (TRSA) Integration for Sensitive and Large Data

  • TRSAs allow data providers to create metadata records in a Dataverse repository for research data that is too large or sensitive to deposit into a Dataverse repository. Researchers can discover the metadata in a Dataverse repository and be directed to the appropriate steps or automated workflows to access the data itself. Additional Information is available from cyberimpact.us.
  • Github Issue #5213
  • Check out the Code in Progress

 

    Future

    2022 Expanded Software Metadata and Workflows Support

    • Code can currently be deposited into a Dataverse repository, but we'll provide some code-specific metadata and updated support for workflows.

    2022 Linked Data Notification Integration

    • Dataverse will be able to integrate with other repositories through Linked Data Notifications, following COAR Notify.

    2022 Citations for Dataverse Collections

    • Researchers will be able to cite Dataverse collections as well as Datasets and Files.
    • Github Issue #6112 

    2022 Green, Blue, Yellow DataTags Support

    • Through an integration with Datatags, researchers will be able to deposit and share datasets that contain sensitive information up to the Yellow level.  
    • Github Issue #871 

    2022 Orange DataTags Support

    • Through an integration with Datatags, researchers will be able to deposit and share datasets that contain sensitive information up to the Orange level.
    • Github Issue #871

     

      Recent Releases

      • 5.11 Terms for Restricted Files, Muting Notifications 6/13/22
      • 5.10.1 Bug Fixes 4/6/2022
      • 5.10 Multiple License Support 3/18/2022
      • 5.9 System Optimizations 12/9/2021
      • 5.8 Embargo 11/5/2021
      • 5.7 External Vocabulary Integration 10/13/2021
      • 5.6  Support for Double Blind Review, Migration APIs, Guestbook Responses API 8/4/2021
      • 5.5  Auxiliary Files Accessible through the UI, Performance Enhancements 5/19/2021
      • 5.4 Key Technology Upgrades, New File Access API, Deactivate Users API, 4/5/2021
      • 5.3 Auxiliary Files to Support Differentially Private Metadata Deposit, Updated Banner Options 12/10/2020 
      • 5.2 Continued Dataset and File Redesign, Google Cloud Archiver Integration 11/9/2020
      • 5.1 and 5.1.1 >5 GB Upload to AWS S3, Additional Store Options for Administrators, Performance Enhancements 10/8/2020
      • 5.0 Continued Dataset and File Redesign, Payara Upgrade, Download Dataset 8/18/2020
      • 4.20 Multiple S3 Stores, Direct S3 Upload 4/1/2020
      • 4.19 OIDC Connect, Python Installer 1/22/2020
      • 4.18 File Preview, Microsoft Login 11/14/2019
      • 4.17 Dataset Level Explore Tools, Performance Enhancements 10/3/2019
      • 4.16 Metrics Redesign and Make Data Count Support, HTML Codebook Exports, Harvesting Improvements 8/28/2019 
      • 4.15.1  Performance Enhancements, Variable Metadata Edit APIs 7/10/2019
      • 4.15 Sorting and Filtering Files in a Dataset, Better Recognition and Categorization of Files 6/14/2019
      • 4.14 OpenAIRE-compliant exports, expanded analytics options 5/10/2019
      • 4.13 File Hierarchy Support, File Metadata Edit APIs 4/22/2019 

      Last updated 12/16/2021