Task #745

Story #954: GMN specific features

Selecting if objects should be managed by client or by GMN.

Added by Roger Dahl almost 12 years ago. Updated over 11 years ago.

Target version:
Start date:
Due date:
% Done:


Product Version:
Story Points:


GMN can store science objects locally or can stream them from a web server on request. When an object is registered on GMN, GMN currently examines the object to determine if the object should be stored locally or be streamed from a web server. Investigate possibility of extending the REST interface to let client select how an object should be handled.


#1 Updated by Dave Vieglais almost 12 years ago

This would seem to be a GMN specific functionality so perhaps should not be expressed in the D1 service APIs. However it would seem likely that as we work with a broader array of Data Repositories, it may be necessary to provide vendor specific attributes in the create() request. Perhaps create an additional, optional parameter in the create method signature for "options". This parameter should be ignored by targets that don't support the options. The type for "options" would be a dictionary - key, value pairs that are defined by the vendor.

#2 Updated by Roger Dahl over 11 years ago

  • Parent task set to #954

#3 Updated by Dave Vieglais over 11 years ago

  • Tracker changed from Bug to Task

#4 Updated by Roger Dahl over 11 years ago

  • Status changed from New to In Progress

#5 Updated by Roger Dahl over 11 years ago

  • Status changed from In Progress to Closed

Implemented a vendor specific option in MN_crud.create called vendor_gmn_remote_storage. Added a description of the option in REST_object. Did not add it to API.

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)