Use Cases

Owned by AmberLeahey (Unlicensed)
Last updated: Mar 16, 2017 by Julian Gautier


  • DDI Import (metadata transfer)

    • Need improved tools for uploading DDI XML in Dataverse UI (for researchers, support staff);

    • No current comparison list of supported DDI elements between repositories that could be helpful for identifying gaps in support;

    • Need improved tools for migrating DDI from other system into Dataverse (e.g. through command line import,  API, migration scripts)

      • Support DDI-Codebook (Nesstar flavour)

      • DDI Lifecycle (DDI Lifecycle 3.2; local profiles)


  • Metadata reusability

    • Could dataverse support reusable metadata for researchers to search and reuse in the design of data (e.g. for reuse in questionnaires, variable coding, value coding, etc.?)

      • Some discussion from group using DDI Lifecycle metadata to improve distinction between concepts and variables, enable discovery of concepts across Dataverses (e.g. Gender (or Sex) concepts and variables to represent those concepts could become reusable or discoverable)

      • Reusability factor of concepts, questions, variables, value lists, etc.

      • Could enable attribution of reusable metadata (e.g. standardized codelists (such as NAICS classifications), attribution for concepts and implementation of abstract concepts)


  • Harmonize by-design

    • Similar to metadata reusability; makes metadata items reusable for researchers during the conceptual and study design phase of the lifecycle.


  • Variable-level DDI

    • Improved description of variables in general:

      • (e.g. frequencies, summary statistics, missing values, questions, concepts, universe notes, units of measurement, routing / skip logic (questionnaires), mappings between questions, concepts AND variables, provenance at the variable-level)

    • DDI Lifecycle has support for distinction between questions and variables, and questions, variables, and concepts.

    • System could benefit from more access rights (metadata) being captured at the variable-level; could be incorporated into DataTags workflow? To help with understanding restricted data access; master copies, access copies, etc.

    • Attribution at the variable level (e.g. stop the naming of variables “ _____ scale of …”)

    • DDI XML for support of TAB file downloads; otherwise the TAB file isn’t enough, maybe DDI could be written to a setup file structure for reuse?


  • Support for DDI controlled vocabularies

    • In general more controlled vocabularies could help with metadata generation

      • DDI controlled vocabularies would help with filling in DDI

      • Could be enforced

      • Support for local controlled vocabularies

      • Need for multilingual controlled vocabulary support (also need for multilingual interface; Scholars Portal working on french interface)


  • Support for Local DDI Profile

    • Customize metadata fields and potentially prepare templates for local DDI Profile upon configuration of an instance

    • Or support DDI profile as a template at the DAtaverse level (bring back templates)

    • (E.g. CESSDA, ODESI, and others have DDI Profiles or DDI Best Practice Documents)


  • Improved variable and metadata visualization

    • Scholars Portal developing DataExplorer app that uses DDI metadata to explore variables in context of dataset

    • Identified need to improve discovery of variables in the system, with more DDI metadata (for tabular files)