References closed-as-not-planned issue #201
Serverside portion in ACCESS-NRI/tracking-services#33

Background

Now that we have multi-HPC workflows, we should get around to updating the model release database. We're opting to incorporate the model release database into @tmcadam s tracking-services projection, rather than a separate database.

Considerations

• Since we want to keep the client (us) light, we can just send the data in a JSON blob in any structure that we want. Lets make it as easy as possible, since we don't want to bog down the CD with provenance stuff.
• Determine if the data that we want to send is easily accessible to us, and if not, leave it out for a later iteration.