You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Moving/inconsistent data locations - a tough one since different foundations and NCI offer free storage, forcing us to change buckets, breaking links etc. Also, currently having to use very sensitive AWS keys to get the data.
Priority:
Desired solution:
Preferred or recommended technical approach:
Miguel: a solution might be to use cavatica to create projects, but keeping up with updates is something bix ops struggles with seemingly.
Would it be possible to keep a list of "known locations" and have the data Extraction scripts consider multiple potential locations? In this way, maintenance could be reduced to simply updating a configuration file with a list of locations.
The text was updated successfully, but these errors were encountered:
Moving/inconsistent data locations - a tough one since different foundations and NCI offer free storage, forcing us to change buckets, breaking links etc. Also, currently having to use very sensitive AWS keys to get the data.
Priority:
Desired solution:
Preferred or recommended technical approach:
DoD:
Questions
Ideas
The text was updated successfully, but these errors were encountered: