Closed seandavi closed 6 years ago
Related to #40.
For the time being, I have:
gdcdata
with an extra argument to force the use of gdc-client
with the default being the data
endpoint. gdc_cache()
and a setter gdc_set_cache()
that uses an option to store the path to the "cache directory". The caching behavior is very simple. If the file to be transferred exists in the cache, use it (unless explicitly told not to). Otherwise, download. At this time, I have not used BiocFileCache, but that is because 1) some of the caching using files was already done using files and 2) because I would like to take advantage of the more interesting features of BiocFileCache (metadata, etc.) in the future, but wanted caching behavior first and 3) because I wanted to treat the uuids as the primary key in the "database", enforcing uniqueness and such. As things stand, I leave the BiocFileCache layer to the user. I think doing so represents a nice balance for the time being.
Related to #45
can this be closed or are you still tracking this?
We can close for now. I do want to revisit the BiocFileCache approach, but that is going to require a bit of retooling and can wait for another day.
We desire a caching behavior for data coming from the NCI GDC. Features might include:
API suggestions:
gdcdata
andtransfer
into one method that accepts file UUIDs and serves back files.Considerations:
files()
endpoint to gather metadata, on demand?