Skip to content

Commit 78a04c8

Browse files
fedorovgitbook-bot
authored andcommitted
GITBOOK-433: change request with no subject merged in GitBook
1 parent 394c524 commit 78a04c8

File tree

7 files changed

+436
-425
lines changed

7 files changed

+436
-425
lines changed

SUMMARY.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -25,18 +25,19 @@
2525

2626
* [Introduction](data/introduction.md)
2727
* [Data model](data/data-model.md)
28-
* [Data versioning](data/data-versioning.md)
2928
* [Organization of data](data/organization-of-data/README.md)
3029
* [Files and metadata](data/organization-of-data/files-and-metadata.md)
30+
* [BigQuery tables](data/organization-of-data/bigquery-tables.md)
3131
* [DICOM stores](data/organization-of-data/dicom-stores.md)
3232
* [Clinical data](data/organization-of-data/clinical.md)
33-
* [Resolving CRDC Globally Unique Identifiers (GUIDs)](data/organization-of-data/guids-and-uuids.md)
33+
* [UUIDs and GUIDs](data/organization-of-data/guids-and-uuids.md)
3434
* [Deprecated functionality](data/organization-of-data/deprecated-functionality/README.md)
3535
* [Organization of data in v1 (deprecated)](data/organization-of-data/organization-of-data-v1.md)
3636
* [Organization of data, v2 through V13 (deprecated)](data/organization-of-data/organization-of-data-v2-through-v13-deprecated/README.md)
3737
* [Files and metadata](data/organization-of-data/organization-of-data-v2-through-v13-deprecated/files-and-metadata.md)
3838
* [Resolving CRDC Globally Unique Identifiers (GUIDs)](data/organization-of-data/organization-of-data-v2-through-v13-deprecated/guids-and-uuids.md)
3939
* [Clinical data](data/organization-of-data/organization-of-data-v2-through-v13-deprecated/clinical.md)
40+
* [Data versioning](data/data-versioning.md)
4041
* [Downloading data](data/downloading-data/README.md)
4142
* [idc-index and 3D Slicer](data/downloading-data/downloading-data.md)
4243
* [s5cmd](data/downloading-data/downloading-data-with-s5cmd.md)

api/getting-started.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,8 @@
11
# Getting Started
22

3-
<mark style="color:red;">Note: As of 15-July-2025, support for user defined cohorts has been removed from the both the IDC API V1 and the IDC API V2. The API documentation has been revised accordingly.</mark>
3+
{% hint style="danger" %}
4+
As of 15-July-2025, support for user defined cohorts has been removed from the both the IDC API V1 and the IDC API V2. The API documentation has been revised accordingly.
5+
{% endhint %}
46

57
This section describes version 2 of the IDC REST API . The documentation for the version 1 API will be found [here](https://learn.canceridc.dev/api/v1-api).
68

data/data-versioning.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,7 @@ In order to reproduce the result of such analysis, it must be possible to precis
4242

4343
Because an IDC version exactly defines the set of data against which the filter/query is applied, and because all versions of all data, except data removed due to PHI/PII concerns, should continue to be available, a cohort is therefore persistent over the course of the evolution of IDC data.
4444

45-
## DICOM Entities are versioned
45+
4646

4747
There are various reasons that can cause modification of the existing collections in IDC:
4848

Lines changed: 8 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,15 +1,13 @@
11
# Organization of data
22

3-
This section describes the current organization of IDC data. The organization of data was static from IDC Version 2 through IDC Version 13 except that [clinical data](organization-of-data-v2-through-v13-deprecated/clinical.md) was added in Version 11. Development of the clinical data resource is an ongoing project. From IDC v14, our data [became available](https://registry.opendata.aws/nci-imaging-data-commons/) from the Amazon AWS Open Data Registry, and the files in storage buckets were organized into series-level folders.
3+
IDC provides a variety of interfaces to access both the data (as files) and metadata (to subset files and build cohorts). The flow of data and the relationship between the various components IDC uses is summarized in the following figure.
44

5-
### IDC data model
5+
{% embed url="https://docs.google.com/presentation/d/1UVpNVyVy3xIYLDnm4rtgAUmSu-uKQo5krekI9DSMT8o/edit?usp=sharing" %}
66

7-
### [Files and metadata](files-and-metadata.md)
7+
We maintain the following resources to enable access to IDC data:
88

9-
### [GA4GH DRS objects](https://learn.canceridc.dev/data/organization-of-data/guids-and-uuids)
10-
11-
### [Clinical Data](organization-of-data-v2-through-v13-deprecated/clinical.md)
12-
13-
### [Organization of data, v1 through V13 (deprecated)](./#organization-of-data-v1-through-v13-deprecated)
14-
15-
### [Organization of data in v1 (deprecated)](organization-of-data-v1.md)
9+
* [Cloud storage buckets](./#files-and-metadata): files maintained by IDC are mirrored between Google and AWS public storage buckets that provide fee-free egress without requiring login. The buckets organize files by DICOM series, each series stored in a separate folder. Given the large overall size of data in IDC, you will likely need to use one of the search interfaces to identify relevant series first.
10+
* BigQuery tables: collection-level metadata, DICOM metadata, [clinical data tables](clinical.md) available via SQL query interface.
11+
* Python API: pip-installable [idc-index package](https://idc-index.readthedocs.io/en/latest/) provides programmatic interface and command-line tools to search IDC data using most important metadata attributes, and to download files corresponding to the selected cohorts from the cloud buckets
12+
* [REST API](broken-reference): alternative language-independent API for selecting subsets of data
13+
* [DICOMweb](dicom-stores.md): DICOM files and metadata queries available from Google Healthcare DICOM stores

0 commit comments

Comments
 (0)