Storing and Organizing Data » History » Version 9
Tom Clegg, 04/04/2014 02:28 PM
| 1 | 7 | Tom Clegg | h1. Storing and Organizing Data |
|---|---|---|---|
| 2 | 3 | Tom Clegg | |
| 3 | 7 | Tom Clegg | Rough demo outline |
| 4 | 3 | Tom Clegg | |
| 5 | 8 | Tom Clegg | # Automatic ingest from a POSIX directory to Keep |
| 6 | 9 | Tom Clegg | #* Staging area is set up ahead of time |
| 7 | #* Someone (possibly 3rd party) uploads some files to the staging area via SFTP or whatever |
||
| 8 | #* API call to {something? ingestor app? arvados?} |
||
| 9 | #* API call provides a tag (e.g., a sample ID) |
||
| 10 | #* In Workbench the imported Datasets appear as Collections in the designated project |
||
| 11 | 6 | Tom Clegg | # My data gets into the right project as specified by the uploader (API call) |
| 12 | # Subscribe to notifications (by email and/or Workbench dashboard): when files start/finish uploading; when files are shared with customer; when files are downloaded by third party |
||
| 13 | # Move/copy collections between projects (Project RX1234, or Customer X’s files), tag them in destination project with the appropriate string (e.g., sample ID) -- defaulting to existing tag used in source project (e.g., provided at time of upload). |
||
| 14 | # “Anyone with this secret link can view/download” mode. Enable, disable, change magic link. Use cases: browser + “wget -r”. |
||
| 15 | # See log/overview of who has accessed your shared data (incl. “anonymous user” if using secret-link-to-share); when shared/unshared; when each upload started/finished -- for a single project, and across all projects |