Feature #8689

Trigger an arvados job to retrieve the data and import it into Keep

Added by Ward Vandewege almost 4 years ago. Updated almost 4 years ago.

Status:
In Progress
Priority:
Normal
Assigned To:
Category:
Third party integration
Start date:
03/14/2016
Due date:
% Done:

88%

Estimated time:
(Total: 0.00 h)
Story points:
1.0

Description

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 that is done, Tapestry needs to get notified or notice; see #8697)

Subtasks

Task #8794: Notify user that transfer has been initiatedNewTom Clegg

Task #8948: Make arvados SDK work in ruby 1.8.7ResolvedTom Clegg

Task #8927: Run job in huXXXXXX project, create & share one if necessaryResolvedTom Clegg

Task #8793: Generate user log entryResolvedTom Clegg

Task #8960: Review 8689-use-downloaded-filenameResolvedWard Vandewege

Task #8949: Review 8697-ruby187-compat commit:arvados|fd696faResolvedWard Vandewege

Task #8950: Review 8689-participant-project at commit:492d441ResolvedWard Vandewege

Task #8902: Use actual filename in "add user_file" callback instead of FIXMEResolvedTom Clegg


Related issues

Related to Tapestry - Feature #8688: Accept authenticated API calls from data providers to add datasets to a public profileResolved03/24/2016

Associated revisions

Revision 913a2b9f
Added by Tom Clegg almost 4 years ago

Merge branch '8689-participant-project'

refs #8689

Revision e61d3f48
Added by Tom Clegg almost 4 years ago

Merge branch '8689-use-downloaded-filename'

refs #8689

History

#1 Updated by Tom Clegg almost 4 years ago

  • Description updated (diff)

#2 Updated by Tom Clegg almost 4 years ago

  • Story points set to 1.0

#3 Updated by Tom Clegg almost 4 years ago

  • Category set to Third party integration
  • Assigned To set to Tom Clegg

#4 Updated by Tom Clegg almost 4 years ago

  • Status changed from New to In Progress

#5 Updated by Ward Vandewege almost 4 years ago

Reviewing origin/8697-ruby187-compat:

I see this changes the gemspec dependencies for google-api-client:

-  s.add_dependency('google-api-client', '~> 0.6.3', '>= 0.6.3')
+  s.add_dependency('google-api-client', '>= 0.7', '< 0.9')

Does that mean that we no longer need that geriatric google-api-client version for our Ruby sdk?

#6 Updated by Tom Clegg almost 4 years ago

Yes... we're graduating from a 3-year-old version (0.6.4) to a 1-year-old version (0.8.6).

AFAICT our dependence on 0.6.3 was an accident: According to commit logs, I pinned to 0.6.x to make bundle stop complaining that ">= 0.6.3" was too open-ended (which is kind of silly, given semver doesn't guarantee anything in 0.x).

Now we need <0.9 to avoid a Ruby >= 1.9 dependency. (IIRC one of google-api-client 0.9's dependencies, not google-api-client 0.9 itself, abandoned Ruby 1.8.)

Current version is 0.9.4.

#7 Updated by Ward Vandewege almost 4 years ago

Tom Clegg wrote:

Yes... we're graduating from a 3-year-old version (0.6.4) to a 1-year-old version (0.8.6).

AFAICT our dependence on 0.6.3 was an accident: According to commit logs, I pinned to 0.6.x to make bundle stop complaining that ">= 0.6.3" was too open-ended (which is kind of silly, given semver doesn't guarantee anything in 0.x).

Now we need <0.9 to avoid a Ruby >= 1.9 dependency. (IIRC one of google-api-client 0.9's dependencies, not google-api-client 0.9 itself, abandoned Ruby 1.8.)

Current version is 0.9.4.

Aha. LGTM then, thanks!

#8 Updated by Ward Vandewege almost 4 years ago

reviewing 8689-participant-project @492d441fedc8796a08b078a1d715d265ca7c1ae2: LGTM, thanks!

#9 Updated by Ward Vandewege almost 4 years ago

Reviewing 8689-use-downloaded-filename: LGTM

Also available in: Atom PDF