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
Scientists 1 and 2 are working on a project that needs to use file A on local storage, but File A is only on the cloud. Scientist 1 uses BFF to copy the file to the Vast. The file is 4TB so it isn't immediately available. Scientist 2 goes to BFF to do the same thing: they would like to know if the download is already in progress.
Design
In “canonical file path field” write “Copying to Vast in progress…” (italics) for in-progress downloads
Implementation details
Cloud only: shouldBeInLocal is False
Download in progress: shouldBeInLocal is True and eviction date is null
Download complete: shouldBeInLocal is True and eviction date is non-null
The text was updated successfully, but these errors were encountered:
More design decisions needed: The plan above uses "File Path (Canonical)" but does not account for "File Path (Local)", since our test usage of BFF didn't surface files with a "File Path (Local)". Need to get clarity on how the three paths (Cloud, Local, Canonical) interact and decide which to display for downloads in progress. "Canonical" path may be of little value to users, compared to the other two.
User story
Scientists 1 and 2 are working on a project that needs to use file A on local storage, but File A is only on the cloud. Scientist 1 uses BFF to copy the file to the Vast. The file is 4TB so it isn't immediately available. Scientist 2 goes to BFF to do the same thing: they would like to know if the download is already in progress.
Design
In “canonical file path field” write “Copying to Vast in progress…” (italics) for in-progress downloads
Implementation details
shouldBeInLocal
is FalseshouldBeInLocal
is True and eviction date is nullshouldBeInLocal
is True and eviction date is non-nullThe text was updated successfully, but these errors were encountered: