DRS is a ga4gh standard that "provides a generic interface to data repositories so data consumers can access data objects in a single, standard way regardless of where they are stored and how they are managed".
I would like bedhost to implement this standard for accessing bed files. This standard is designed to address how we have the "remote" options, of s3 vs http, for example. I think do to his we need:
I provide an endpoint, /objects/{object_id}, which returns a JSON response that includes a list of access methods, and some other information about the file. So, it's providing some metadata. It includes:
file size
list of access methods, with (access_id or access_url)
identifier
description
an endpoint, /objects/{object_id}/access/{access_id}, which returns the URL to the file according to the existing access method. this is basically already implemented, but at a different endpoint -- so we would need to adapt to this way of forming the endpoint.
nsheff
commented
1 year ago
DRS is a ga4gh standard that "provides a generic interface to data repositories so data consumers can access data objects in a single, standard way regardless of where they are stored and how they are managed".
I would like bedhost to implement this standard for accessing bed files. This standard is designed to address how we have the "remote" options, of
s3vshttp, for example. I think do to his we need:/objects/{object_id}, which returns a JSON response that includes a list of access methods, and some other information about the file. So, it's providing some metadata. It includes:/objects/{object_id}/access/{access_id}, which returns the URL to the file according to the existing access method. this is basically already implemented, but at a different endpoint -- so we would need to adapt to this way of forming the endpoint.