search

tnc-br / ddf-isoscapes

4 stars 0 forks source link

Document proposal for better controls of inputs and outputs to the colab #53

Closed jmogarrio closed 1 year ago

jmogarrio commented 1 year ago

Right now there's some descriptions of the data in comments in the main notebook, as well as some details in this doc.

Ideally, we probably want something like a Data Card for each dataset. This likely involves some collaboration with the Samples workstream, since any new dataset should come with (at least part of) a Data Card.

benwulfe commented 1 year ago

@gretaabib will take a look. At a high level, we need better controls on the datasets that the sample workstream produces, ensuring they are well documented, named and tracked. May be data cards - greta will take a look.

Sprint 5

benwulfe commented 1 year ago

greta to work with @jjcastro and @kazob1998 to develop a holistic approach to managing all data. We will have a design doc created in Sprint 5

benwulfe commented 1 year ago

changed title, sprint 5 item

jmogarrio commented 1 year ago

This was also missed in our sync with @gretaabib for the same reason, I'll follow up on it next week.

jmogarrio commented 1 year ago

We weren't sure in triage whether this is something that is still necessary, assigning to Luis to assess.

benwulfe commented 1 year ago
  1. Validation doc addressed this to some degree by proposing stamping the isoscape with validation results
  2. https://github.com/tnc-br/ddf-isoscapes/issues/148 covers using earth engine as a way to standardize our inputs.