As part of MC2 Center data routing, the CRDC DataHub is an expected terminal repository that 1) excepts a broad range of data types, 2) accepts human-derived datasets, and 3) has independent metadata requirements for assays, specimens, individuals, etc.
MC2 --> DataHub package prep and transfer protocols need to be established, using the available tools, guidelines, and schemas from DataHub.
Initial thoughts:
MC2 metadata templates will incorporate DataHub attributes where possible. Mappings will be designed as needed, but integration is higher priority
Building Synapse Datasets + Collections that comprise a DataHub submission package would integrate well with our release strategy (relative to #71)
Automated transfer through an API would be desirable
Establishing access restrictions will require some further thinking. Synapse has its own ACR implementation, but DataHub/CRDC uses DbGaP to manage ACRs and requests for sequencing and imaging data
As part of MC2 Center data routing, the CRDC DataHub is an expected terminal repository that 1) excepts a broad range of data types, 2) accepts human-derived datasets, and 3) has independent metadata requirements for assays, specimens, individuals, etc.
MC2 --> DataHub package prep and transfer protocols need to be established, using the available tools, guidelines, and schemas from DataHub.
Initial thoughts: