The growth of the biodiversity report UX has become cumbersome. In addition, there has been a long-standing mismatch between what the biodiversity report is, and how data is to be entered into Ecotone.
In most use cases, students are entering just one kind of sample at a time. So rather than create a huge biodiversity report in which most fields are empty, and bearing the burden of managing what is optional vs what needs validated, let's enable the user to just directly create soil samples, plant samples, etc.
The essence of the app is for students to look at all the sample data, and then make a calculation and determination of the biodiversity in that plot.
So let's decouple the samples. Users can add any kind of sample for any plot at any time.
Later, a student can create a biodiversity report for a particular plot by looking at all the sample data for that plot.
The growth of the biodiversity report UX has become cumbersome. In addition, there has been a long-standing mismatch between what the biodiversity report is, and how data is to be entered into Ecotone.
In most use cases, students are entering just one kind of sample at a time. So rather than create a huge biodiversity report in which most fields are empty, and bearing the burden of managing what is optional vs what needs validated, let's enable the user to just directly create soil samples, plant samples, etc.
The essence of the app is for students to look at all the sample data, and then make a calculation and determination of the biodiversity in that plot.
So let's decouple the samples. Users can add any kind of sample for any plot at any time.
Later, a student can create a biodiversity report for a particular plot by looking at all the sample data for that plot.
Confirmed w/ Ann P 11/1/17.