Giter Site home page Giter Site logo

rdp-portal's Introduction

Reusable Data best practice portal (rdp-portal)

CTSA hubs produce many valuable datasets which can be shared across the broader research community. A significant gap exists between the data providers and the data discovery portals where researchers look for relevant datasets (including the generic Google Dataset search and many biomedical specific data portals). Data providers typically lack sufficient guides to expose their dataset metadata to these data portals. This web-based data-sharing best-practice will serve as the interactive widgets to guide through the important steps of data-sharing, which will make providers' datasets discoverable through multiple data portals.

Problem statement

This portal aims to help investigators share their data (or information about their data) using best practices for metadata, identifiers, licensing, and other attributes; the goal is to enable discovery and reuse.

Project description

The biomedical and informatics communities have largely endorsed the spirit and basic components of the FAIR Data Principles. Biomedical data producers, including CTSA hubs, need actionable best-practice guidance on how to make their data discoverable and reusable, and bring the practical benefits of data sharing to researcher’s own research projects, as well as the research community as a whole. This project will target the specific steps during the data-sharing process, such as data-hosting, data-licensing and metadata-authoring.

Alignment to program objectives

TODO see here

Contact person

We require a contact person for each project for administrative purposes. Each project should also have a CD2H Program director assigned.

Point person (github handle) Site Program Director
Chunlei Wu (@newgene) Scripps Melissa Haendel (@mellybelly)

Leads

Lead(s) (github handle) Site
Chunlei Wu (@newgene) Scripps
Robin Champieux (@rchampieux) OHSU
Kristi Holmes (@kristiholmes) Northwestern

Team members

see team page

Repositories

Deliverables

A collaborative guidebook, an interactive web portal, and an metadata-authoring web portal

Milestones

The milestones for this rdp-portal project is here:

https://github.com/data2health/rdp-portal/milestones

We are still in the process of finalizing them.

Evaluation

Each project should propose a set of evaluation measures, recorded in a separate Evaluation Plan file, for example here. These will be reviewed by the Evaluation committee and approved by the Program Directors and NCATS. The Evaluation committee will meet with each Project team leads to assist.

Each project should have Evaluation-realated issues, that can be tagged with the "evaluation" tag. see Example Evaluation Issue

Education

Each project should propose a set of educational activities, listed separately in the Education Plan file. Please reference any of the following that apply:

  • Educational resources that will be generated (these can be milestones and/or files in the repo)
  • Educational opportunities (please indicate for which type of learner and how to participate)
  • Best practices guides

Please include education related issues where relevant, tagged with "education".

Get involved

We encourage the community to get involved.

We require all CD2H projects to have non-CD2H CTSA participants, as CD2H is a CTSA coordinating center. Each project should include an Engagement plan file, example here.

Please tag any engagment related issues with "engagement".

Working documents

Documentation may be natively in GitHub using the wiki or .md files in the appropriate folder, or in Google Drive. Documentating projects in Github

The project Google drive folder is accessible to onboarded participants.

Slack room

The project slack room is accessible to onboarded participants. You will not automatically be added to Slack, please join via the link above.

Need help with GitHub? See the Managing Tranlational Informatics Projects (MTIP) tutorial

This tutorial covers markdown basics and more.

rdp-portal's People

Contributors

cgcook avatar eichmann avatar jmcmurry avatar kristiholmes avatar newgene avatar rchampieux avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar

Forkers

tricfran mdkan

rdp-portal's Issues

Choose V.10 practice areas

Finalized that licensing, repositories, and metadata will be focus of V1.0 of guidebook documentation.

Example data sharing plan for CTSA proposals

This should include an example data sharing plan, but also a menu of options for each component. It would be good to see if we can get some examples from our own CTSAs to start with.

Break data license selector into three sections

Targeting three use cases:

  • I want to pick an available CC licence.
  • I need to build a customized usage agreement (pick certain DUO terms?)
  • I have a customized data license already (then provide the url to the terms)

Develop a schema.org schema viewer

This web-based schema viewer renders the input JSON-LD based schema.org schema definition in an easy-to-browse HTML page.

This is useful when we need to define our own extension of the core schema.org types (e.g. Dataset, people, etc).

Identify factors can be used to filter down repositories

These factors from the data repository spreadsheet (produced from #20) can be used to build the interactive web widget to help users to narrow down the repository choices.

e.g.:

  • allow data repository
  • support DOI
  • support schema.org (indexed by Google Dataset Search)

Consider data registration as part of IRB or DUA processes

so that its part of clinical study registration processes to create a representation. This will be important for data that cannot be shared due to compliance needs.

We could then provide the linking more readily to other content items- edu, studies, papers, etc.

from discussion w @eichmann

Implement the metadata authoring forms based on supported metadata models

Based on the output from #29, build an interactive form user can edit their dataset metadata.

Some design considerations:

  • Shared metadata fields between models should be able to transfer.
  • Separate minimally required and additional metadata fields.
  • Use some visual indications for metadata completeness (e.g. progress bar)
  • Specify the benefits of the additional metadata fields

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.