Closed suryasaha closed 2 months ago
See cloud work stream discussion notes from last DRS discussion from 2/12/24: https://docs.google.com/document/d/1hayvWLIoymomPI9oXcaTZirn5YxFv1cYAs70zyvlvnA/edit#bookmark=id.stgpsb1mhzwn
Today at GA4GH connect we decided this should be an enum and the values should be "immediate" and "delayed"
quick note form Connect Switzerland, recording the decision:
Let's make it an enumeration: --> immediate, delayed as the two terms. Lots of thumbs up in the room.
Interest from driver projects at Connect: CRDC, BDC, SRA, European 1M genomes project, AnVIL, Australian Genomics
@ianfore I am using availability as the label now with boolean value. Do you think this looks better?
as of 20240812 we decided the boolean is the right way to go. We can discuss delay time reporting back during the thaw mechanism
Indicate that a given access method is to cold/offline/less available storage
A DRS object is said to be in 'Cold' storage when it is not immediately available via a DRS request. Hot/Cold is binary. Goal is to indicate that a given access method is to a cold/offline/less available storage. Please see https://github.com/ga4gh/data-repository-service-schemas/issues/395 for community discussion.
We are taking a phased approach. For Phase 1, we just want to answer this question: Can the user can retrieve the file at the moment of the request?
In phase 2, we can think about having a better way to provide details on the storage and the thawing process.