-
Task
-
Resolution: Fixed
-
Normal
-
None
-
None
-
None
-
CCROP Sprint 5, CCROP Sprint 6, CCROP Sprint 7, CCROP Sprint 8, CCROP Sprint 9, CCROP Sprint 10, CCROP Sprint 11
While we continue to use the experiment file template, we can start working on the MyFarm feature. My thinking here is, on the MyFarm page, we can allow a user to upload an experiment file to datawolf. We can record the dataset id in the postgres database for the user, I think we have this mocked up on the wiki where we did the initial postgres db design. Then, on the MyFarm page, we can display a summary to begin with as shown in the invision mockup that Lisa did here:
https://projects.invisionapp.com/d/main#/console/13696383/289779594/preview
Eventually, we want to work towards this:
https://projects.invisionapp.com/d/main#/console/13696383/289779596/preview
But that should be broken down into smaller tasks.
-------------------------------------------------------------------------------------------------
- the download button on the experiment file, we download the experiment template file, which contains $CROP_CULTIVAR$?
- where to get “FIELD PROFILE”, for example the drainage type?
- I use /datawolf/dataset/{datasetID}/{fileID}/file and then parse the txt file directly, is that ok? (otherwise have an endpoint in service that parse the txt file and return json).
- tables like "CULTIVARS" is that fixed or not? meaning always the same in all experiment files?