NIH | National Cancer Institute | NCI Wiki  

NumberSourceRequirementPre or Post MVPResolved?Date CompletedComments
1SOW

The Contractor shall develop and implement a prototype of the Integrated Canine Data Commons (ICDC) for housing the results of canine tumor sequences and outcomes of canine clinical trials from the Comparative Oncology Trials Consortium and the NCI-sponsored Canine Immunotherapy Trials Network.

PreYes

2SOW

Building the storage for the datasets to be entered into the system (database, files system, etc).

PreYes

3SOW

Building the capabilities for end users to search the data in the system. This includes deciding what to allow to become searchable (data, metadata), indexing that data, etc.

PreYes

4SOW

Building a system that allows end users to submit their data for public display.

PostNo

5SOW

Providing a means to help users with issues they might have, for example, helpdesk, tutorials, documentation.

PostNo

6SOW

Deciding exactly what types of datasets, data types, and file formats could be submitted to the system. (This is a Steering Committee Goal).

PreYes
DGAB
7COR - 1/14/19

Should be able to look for all “oral” ”melanomas” from a particular breed from a particular source.

PreYes
See Search criteria - Req. 3
8COR - 1/14/19

What technology was used for analyses?  Reference genome used?

NANA
This information is contained in the BAM files and is used at the Cloud Resources.
9COR - 1/14/19

Be able to perform meta-analysis of data in the system aggregated from many studies (e.g. for biomarker/prognostic factor analysis).

NANA
This is a Cloud Resources requirement.
10COR - 1/14/19Include data visualization of aggregated data and live viewing of results when you added or delete data.PreYes
Widgets on Dashboard
11COR - 1/14/19

The system should be limited to oncology studies – not cardiology/dermatology or anything like that.

NANA
This is limiting the data coming in, an NCI control, not a functional requirement.
12COR - 1/14/19

The system should be able to support all canine cancer studies.

PreYes

13COR - 1/14/19

Only Completed/Stopped studies are allowed in the system.

NANA
This is limiting the data coming in, an NCI control, not a functional requirement.
14COR - 1/14/19

Look up data on specific treatments.





15COR - 1/14/19

Could include literature mined data from another source.





16COR - 1/14/19

Have a library of data models available in the system for users to choose from when designing a study or uploading a study.





17SC Presentation - 2/20/19

Full genotype and phenotype characterization of the major canine tumors (and normal tissues) including tumor mutational burden (TMB) and neoantigens (seen by T cells in the context of canine MHC antigens)





18SC Presentation - 2/20/19Description of the tumor microenvironment (TME) including numbers and types of subsets of immune (and other) cells



19SC Presentation - 2/20/19Clinical data from COTC and other canine cancer trials (including images)



20SC Presentation - 2/20/19Treatment naïve, post-treatment, and relapse data



21SC Presentation - 2/20/19Including all the clinical data elements for canines



22SC Presentation - 2/20/19

Obtain canine-specific design criteria and data models from the SC





23SC Presentation - 2/20/19Adapt the infrastructure from the Cancer Research Data Commons (CRDC), customize for canine with input from the SC, and prepare tools for cloud analysis



24SC Presentation - 2/20/19Test and validate this “1st Prototype” with an existing canine dataset(s) for performance that is inter-operable with the CRDC



25SC Presentation - 2/20/19Load datasets from the supplements and other sites (after publication) and verify performance



26SC Presentation - 2/20/19Refine and update; validate all systems; launch public accessible ICDC; add data, maintenance.



27Team StandupWhen loading records, need to have a progress bar to indicate loading progress and more importantly to prevent hitting the submit button again. The system currently allows the user to click the submit button while processing which causes duplicate records to be added to the system.



28TeamGUI design should be responsive to mobile and desktop.



29TeamGUI should be configurable for easy customization in future.



30PM discussion of 5/17/19
  • Users can access the Home page and the Dashboard without logging in.
  • The Dashboard will not contain any PHI or PII, either display or searching.
  • Users can search off of the Dashboard without logging in.
  • Users will have to login, through iTrust or Google (though Fence), to save a search or recover and previously saved searches.
  • Users can download data on the Dashboard (since it doesn’t have PHI or PII) without logging in.




31
Users should be able to build a subset of cases from a superset of cases/cohorts, should look like the cases main view. Should be able to export this list to Cloud Resources (unknown format).



  • No labels