Feature #8689

Updated by Tom Clegg over 5 years ago

When the API call described in #8688 is received, that should trigger
an email to the participant saying the transfer has been requested/started
* a user log entry to that effect
* an
Arvados job that will ingest the data (when data, and when that is done, Tapestry needs to get notified or notice; see #8697)