Schemas for the Data Object Service (DOS) API
View the schemas in Swagger UI
The goal of DOS is to create a generic API on top of existing object storage systems so workflow systems can access data in a single, standard way regardless of where it's stored. It's maintained by the GA4GH Cloud Workstream.
Key features
The API is split into two sections:
- data object management, which enables the creation, updating, deletion, versioning, and unique identification of files and data bundles (flat collections of files); and
- data object querying, which can locate data objects across different cloud environments and DOS implementations.
Getting started
Installing is as easy as:
$ pip install ga4gh-dos-schemas
This will install both a demonstration server and a Python client that will allow you to
manage Data Objects in a local server. You can start the demo server using ga4gh_dos_server.
This starts a Data Object Service at http://localhost:8080.
wget http://hgdownload.cse.ucsc.edu/goldenPath/hg38/chromosomes/chr22.fa.gz
md5sum chr22.fa.gz
# 41b47ce1cc21b558409c19b892e1c0d1 chr22.fa.gz
curl -X POST -H 'Content-Type: application/json' \
--data '{"data_object":
{"id": "hg38-chr22",
"name": "Human Reference Chromosome 22",
"checksums": [{"checksum": "41b47ce1cc21b558409c19b892e1c0d1", "type": "md5"}],
"urls": [{"url": "http://hgdownload.cse.ucsc.edu/goldenPath/hg38/chromosomes/chr22.fa.gz"}],
"size": "12255678"}}' http://localhost:8080/ga4gh/dos/v1/dataobjects
# We can then get the newly created Data Object by id
curl http://localhost:8080/ga4gh/dos/v1/dataobjects/hg38-chr22
# Or by checksum!
curl -X GET http://localhost:8080/ga4gh/dos/v1/dataobjects -d checksum=41b47ce1cc21b558409c19b892e1c0d1
For more on getting started, check out the quickstart guide or the rest of the documentation at ReadtheDocs!
Getting involved!
The Data Object Service Schemas are Apache 2 Licensed Open Source software. Please join us in the issues or check out the contributing docs!
Metadata
Release files for ga4gh-dos-schemas 0.4.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| ga4gh_dos_schemas-0.4.2.tar.gz | 19.0 kB | Without provenance | Details |
Release files / ga4gh_dos_schemas-0.4.2.tar.gz
| Download URL | ga4gh_dos_schemas-0.4.2.tar.gz |
|---|---|
| Size | 19.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ef8c539d86615f2044cae24660ed8854263855e9a11902bc1b4ea3116dad0dcb
|
|
BLAKE2b-256 checksum How to use checksums |
f7cb5d2a3dc7fe63e2d0b5719fe64b042d1be714b66ccc98ca405a973e983687
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.11.0 pkginfo/1.4.2 requests/2.19.1 setuptools/40.2.0 requests-toolbelt/0.8.0 tqdm/4.26.0 CPython/3.6.3
|
Security for ga4gh-dos-schemas 0.4.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.