Design and implement schema for storing run information from DataWolf in GIDB

[selimnairb]

A scenario can be associated with one or more run table entries that contain:

• JSON representation of parameters
• URL to DataWolf for more information
• JSON representation of output results

[selimnairb]

@navarroc Can you look at this issue when you have a chance? My assumption here is that DataWolf will be storing, or can generate, JSON data representing scenario run inputs and outputs. Is this the case? Is the above simple data model adequate? If so, I can implement this and then we can update the DataWolf workflows to replicate model run information back to the GIDB. However I'm not sure we need these data, for example for the report generation, if the same data can simply be queried from DataWolf. What are your thoughts?

[indiragp]

We should add a datawolf_ids or something similar which could be an empty list, so we can write into it. Thanks.

[selimnairb]

@indira1026 Would the URL to DataWolf field in the run table (see above) fulfill the same role as datawolf_ids?

[selimnairb]

Depends on #74

[selimnairb]

This is related to #62