Open aislinnpearson opened 2 weeks ago
Hi @paul121,
Following our call yesterday, I mocked up the below and then asked the Farm staff if it meets all their requirements:
It's not obvious from my image (apologies) but we would include hyperlinks where possible - that way you can go to a study or an experiment quite easily. I also wonder if we should include 'Design name' and 'Status' along with the list of studies.
They thought everything had been included, but had a few comments:
Given these comments, I am wondering if we make the Field, Crop and Experiment searches a pop up box - similar to the 'Select Asset' on a Log form. They can then search or filter.
The other thing I have noticed is that what people are usually looking for is Plans (which I think I am going to start referring to as Studies, because that is what they are called in the ISA framework and I think it would be good to get people used to the idea that an Experiment can have multiple studies). So for the Experiment search box, I am wondering if it should search all of the Experiment module (or maybe just experiments, designs and plans/ study's) but only return Experiments. That way you'd have to click on the experiment to find the plan? I am not sure. Something we should probably talk about in more detail.
In order to make it easier for scientists to find their experiments, we have previously discussed the idea of updating and customising the FarmOS landing page dashboard.
My basic thinking here is that the landing page would keep the farm map at the top of the page and beneath that we would include three search fields, one each for:
What I am less sure about is how/ if we want to include in this a general search query as described in issue #676
Beneath this I was thinking we could have a more customised element, where there is a data field for Proposals and Experiments the user is associated with (perhaps with a link below that takes you to your notifications page as discussed in issue xxx). Ideally we'd build this in a way that is extensible - for example, if we might in future want to add crop assets, management plans or even specific subsets of logs (e.g. those that need review) which the logged in user is responsible for.