Get info about a DrsObject
const url = 'https://your-candig-domain/drs/ga4gh/drs/v1/objects/example?expand=false';const options = {method: 'GET'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url 'https://your-candig-domain/drs/ga4gh/drs/v1/objects/example?expand=false'Returns object metadata, and a list of access methods that can be used to fetch object bytes.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”DrsObject identifier
Query Parameters
Section titled “Query Parameters”If false and the object_id refers to a bundle, then the ContentsObject array contains only those objects directly contained in the bundle. That is, if the bundle contains other bundles, those other bundles are not recursively included in the result. If true and the object_id refers to a bundle, then the entire set of objects in the bundle is expanded. That is, if the bundle contains aother bundles, then those other bundles are recursively expanded and included in the result. Recursion continues through the entire sub-tree of the bundle. If the object_id refers to a blob, then the query parameter is ignored.
Example
falseResponses
Section titled “Responses”The DrsObject was found successfully
A DrsObject that describes the sequencing experiment.
object
The biosample identifier for the experiment.
A unique ID for the experiment. Often the alias for the experiment, as defined by the sequencing center
The specific analysis contents objects that were generated from this experiment.
object
The identifier of the linked DRS object
Alternate identifier for the linked DRS object
The DRS uri(s) to the linked DrsObject
The library strategy used in this experiment
The program this object was ingested as part of
Metadata about the experiment (see Experiment in ingest_openapi.yaml)
object
A list of strings that can be used to find other metadata about this DrsObject from external metadata sources. These aliases can be used to represent secondary accession numbers or external GUIDs.
A drs:// hostname-based URI, as defined in the DRS documentation, that tells clients how to access this object.
The intent of this field is to make DRS objects self-contained, and therefore easier for clients to store and pass around. For example, if you arrive at this DRS JSON by resolving a compact identifier-based DRS URI, the self_uri presents you with a hostname and properly encoded DRS ID for use in subsequent access endpoint calls.
The cumulative size, in bytes, of items in the contents field.
Timestamp of content creation in RFC3339. (This is the creation time of the underlying content, not of the JSON object.)
Timestamp of content update in RFC3339, identical to created_time in systems that do not support updates. (This is the update time of the underlying content, not of the JSON object.)
A string representing a version. (Some systems may use checksum, a RFC3339 timestamp, or an incrementing version number.)
object
The hex-string encoded checksum for the data
The digest method used to create the checksum. The value (e.g. sha-256) SHOULD be listed as Hash Name String in the https://www.iana.org/assignments/named-information/named-information.xhtml#hash-alg[IANA Named Information Hash Algorithm Registry]. Other values MAY be used, as long as implementors are aware of the issues discussed in https://tools.ietf.org/html/rfc6920#section-9.4[RFC6920]. GA4GH may provide more explicit guidance for use of non-IANA-registered algorithms in the future. Until then, if implementors do choose such an algorithm (e.g. because it’s implemented by their storage provider), they SHOULD use an existing standard type value such as md5, etag, crc32c, trunc512, or sha1.
A DrsObject that describes the raw read files.
object
The experiment’s name that this run is generated from.
The unique ID for the run.
The specific raw FASTQ files that were generated in this Run.
object
The identifier of the linked DRS object
Alternate identifier for the linked DRS object
The DRS uri(s) to the linked DrsObject
For a Run object, the description should be raw_reads
The program this object was ingested as part of
A drs:// hostname-based URI, as defined in the DRS documentation, that tells clients how to access this object.
The intent of this field is to make DRS objects self-contained, and therefore easier for clients to store and pass around. For example, if you arrive at this DRS JSON by resolving a compact identifier-based DRS URI, the self_uri presents you with a hostname and properly encoded DRS ID for use in subsequent access endpoint calls.
A list of strings that can be used to find other metadata about this DrsObject from external metadata sources. These aliases can be used to represent secondary accession numbers or external GUIDs.
Metadata about the run (see Run in ingest_openapi.yaml)
object
The cumulative size, in bytes, of items in the contents field.
Timestamp of content creation in RFC3339. (This is the creation time of the underlying content, not of the JSON object.)
Timestamp of content update in RFC3339, identical to created_time in systems that do not support updates. (This is the update time of the underlying content, not of the JSON object.)
A string representing a version. (Some systems may use checksum, a RFC3339 timestamp, or an incrementing version number.)
object
The hex-string encoded checksum for the data
The digest method used to create the checksum. The value (e.g. sha-256) SHOULD be listed as Hash Name String in the https://www.iana.org/assignments/named-information/named-information.xhtml#hash-alg[IANA Named Information Hash Algorithm Registry]. Other values MAY be used, as long as implementors are aware of the issues discussed in https://tools.ietf.org/html/rfc6920#section-9.4[RFC6920]. GA4GH may provide more explicit guidance for use of non-IANA-registered algorithms in the future. Until then, if implementors do choose such an algorithm (e.g. because it’s implemented by their storage provider), they SHOULD use an existing standard type value such as md5, etag, crc32c, trunc512, or sha1.
A DrsObject that describes a sequencing analysis. It usually will consist of a data file, e.g. a variant or read file, and its associated index file. Its contents should also include any associated Experiments (as ContentObjects), ordered in order of appearance in the associated variant/read files.
object
The unique ID for this analysis
Same as name
The specific analysis contents objects that comprise this analysis DRS entity. Should contain one or more ContentsObjects that describe the data files in the analysis, and one or more ContentsObjects corresponding to the experiments analyzed in the analysis.
object
The identifier of the linked DRS object
Alternate identifier for the linked DRS object
The DRS uri(s) to the linked DrsObject
Type of sequencing analysis
The program this object was ingested as part of
The reference genome used to compile this analysis
1 if the object has been indexed for search, 0 if not
A list of strings that can be used to find other metadata about this DrsObject from external metadata sources. These aliases can be used to represent secondary accession numbers or external GUIDs.
A drs:// hostname-based URI, as defined in the DRS documentation, that tells clients how to access this object.
The intent of this field is to make DRS objects self-contained, and therefore easier for clients to store and pass around. For example, if you arrive at this DRS JSON by resolving a compact identifier-based DRS URI, the self_uri presents you with a hostname and properly encoded DRS ID for use in subsequent access endpoint calls.
The cumulative size, in bytes, of items in the contents field.
Timestamp of content creation in RFC3339. (This is the creation time of the underlying content, not of the JSON object.)
Timestamp of content update in RFC3339, identical to created_time in systems that do not support updates. (This is the update time of the underlying content, not of the JSON object.)
A string representing a version. (Some systems may use checksum, a RFC3339 timestamp, or an incrementing version number.)
object
The hex-string encoded checksum for the data
The digest method used to create the checksum. The value (e.g. sha-256) SHOULD be listed as Hash Name String in the https://www.iana.org/assignments/named-information/named-information.xhtml#hash-alg[IANA Named Information Hash Algorithm Registry]. Other values MAY be used, as long as implementors are aware of the issues discussed in https://tools.ietf.org/html/rfc6920#section-9.4[RFC6920]. GA4GH may provide more explicit guidance for use of non-IANA-registered algorithms in the future. Until then, if implementors do choose such an algorithm (e.g. because it’s implemented by their storage provider), they SHOULD use an existing standard type value such as md5, etag, crc32c, trunc512, or sha1.
Metadata about the analysis (see Analysis in ingest_openapi.yaml)
object
A DrsObject that describes a data file, e.g. a variant or read file.
object
The filename for this data file, including its file extensions.
The filename for this data file, including its file extensions.
Type of file
The list of access methods that can be used to fetch the DrsObject.
A full URL describing the file’s location
object
object
An access id and region that might be needed to specify to get a signed URL for obtaining bytes
object
The location of the file, specified as endpoint/bucket/filename.
Name of the region in the cloud service provider that the object belongs to.
The program this object was ingested as part of
Example
{ "description": "wgs", "self_uri": "drs://drs.example.org/314159", "checksums": [ { "type": "sha-256" } ]}