Skip to content

DB Design vision #3

Description

@mr-eyes

Since we are very keen to keep all of Snippet services open-source, client-side only as much as possible, I imagine this to be a serverless API to be used centrally by snipe explore and snipe CLI to fetch QC tables and signatures.

Simple use cases:

# for fetching URLs for direct download
- api/run=$run_id
- api/exp=$exp_id
- api/bioproject=$bioproject

- api/db/search?species=dog
- api/db/search?species=dog&genome=canfam3
.
.
- api/profile/search?sha256=wijad98ijwa9dqwdji98qiw
- api/metadata/?lzstring=amdaoimiaJND(IAjdiadiaoujdoasd

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions