david4096
commented
6 years ago DCPPC-DRAFT-6_KC7 Initial Products (Crosscut Metadata Model, Stage 1 Metadata Instance, and Exchange Format): Contact Ian Foster https://docs.google.com/document/d/1Qf5L4PNBb7zN9H7yqJpTfZCOGO6CfqzyB2V7FpFBqPw/edit?usp=sharing The KC7 Summary Report identifies three major products for Phase 1 work:
Crosscut Metadata Model: A data model designed to allow each FS team rapid and interoperable access to metadata and associated data.
Stage 1 Metadata Instance: This cloud-hosted store will allow centralized DCPPC access to a metadata subset from AGR, GTEx, and TOPMed, conformant with the Crosscut Metadata Model and represented using the Exchange Format.
Exchange Format: A representation for metadata in the Stage 1 Metadata Instance to allow for the specification of a set of data objects plus associated integrity checks and metadata.We document here our goals, plans, and progress to date in each of these areas, with the goal of providing a single, definitive source for information on these topics. We intend this living document to evolve throughout the Data Commons Pilot Phase, as we develop prototypes and products and learn from those experiences.
2) Announcing 5 DCPPC-DRAFTs: Five documents have reached team consensus and have been submitted for Consortium comment. Please take time to review each of these and comment early and often. Consortium members outside the submitting team have comment access only. RFC Governance project management will track that each team has taken the opportunity to comment. Each submitting team will respond to comments and iterate on their DCPPC-DRAFT, ensuring that comments are archived. If and when the submitting team feels they have reached general consensus, they will close the commenting period and create a summary that addresses comments. The submitting team can then submit an RFC at their discretion.
DCPPC-DRAFT-1_KC6 Use Cases: Contact Kevin Wilson https://docs.google.com/document/d/1Eizi5W7oV45gmQ-QO3AqXwZOPQdhWGDPX_qecroR3xI/edit?usp=sharing This document contains a series of use cases, which serve to inform the Security, Ethics, and Privacy-related functionality that needs to be incorporated into the NIH Data Commons full stack systems. Each user story identifies a key use case along with a recommendation for whether the functionality should be incorporated into the systems within the 180-day pilot phase of the project or whether it is a longer-term activity. The purpose of this document is to facilitate communication and consensus around Security, Ethics, and Privacy-related functionality and once approved, it will serve as a roadmap for policy and technical implementation.
DCPPC-DRAFT-2_KC1 Phase 1 Overview for Full Stacks: Contact Avi Ma'ayan and Stan Ahalt https://docs.google.com/document/d/19-0NtTutSoe6T9XkDAFcIdH7fEDMGVW69OIqCUh0D-M/edit?usp=sharing An informational overview of the KC1 recommendations, standards, and technologies aimed at the Full Stacks for Phase 1. The FAIR principles lay out a path to augment the potential for discovering and reusing existing digital resources as well as those produced by the NIH research community. An important consideration, therefore, is to assess the degree to which digital resources in the Commons are FAIR, and to provide constructive feedback to increase their FAIRness. To achieve the goal of performing FAIR assessments, members of KC1 designed the Data Commons Assessment for FAIRness (DCAF) Application Programming Interfaces (APIs).
DCPPC-DRAFT-3_KC2 Phase 1 Overview for Full Stacks: Contact Mercè Crosas https://docs.google.com/document/d/1lx3uakz4foYN8vw8E5U6NM2F7RcBjyIGA4ZE2zvE9_g/edit?usp=sharing This document provides information for the Full Stacks that wish to demonstrate Key Capability 2, which is concerned largely with providing a set of Globally Unique Identifiers (GUIDs) that can be used to find are findable, accessible, interoperable, and reusable in the Data Commons infrastructure.
DCPPC-DRAFT-4_KC3 Phase 1 Overview for Full Stacks: Contact Paul Avillach, Isaac Kohane https://docs.google.com/document/d/1jh9rF9gNjxIBHm3wCQTBBUZHNJ4-xRUPFsb8z1m4qBI/edit?usp=sharing An overview of the KC recommendations, standards, and technologies aimed at the Full Stacks for Phase 1. This document details the landscape of APIs available for the NIH DCPPC and extended community. KC3 will leverage and expand on existing standards within the community to achieve the open standard APIs goals of the Data Commons Platform (DCP). There are 65 APIs across 15 different domains in various stages of development and production for prospective use in one or more of the 4 DCP fullstack efforts. This KC3 RFC describes the following about each API: API date of availability; API use in one or more full-stacks; API role in providing access to DCPPC resources and data.
DCPPC-DRAFT-5_KC6 OAuth/OIDC Registry for the Data Commons: Contact David Bernick https://docs.google.com/document/d/1VsGmO17gwu8lGV-8V-TqjyVjmxTBIRRlYq3-jjKAPOw/edit?usp=sharing This document describes two core ways to make things interoperable, and presents caveats and tradeoffs for each. This will give the Data Commons something akin to Single Sign On (SSO) across all stacks, without forcing unity in choice of OIDC Providers. This means that a user only has to sign in once for their session to be valid across all the stacks.