Parent Tracking Issue: Improved user experience

[aislinnpearson]

Following the role out of the experiment module, which focused on the data model rather than usability, we were told that, when completed, the information is incredibly useful but it is also hard to find the information you want and the overall system not very intuitive, which makes difficult to use. This as a parent issue to keep track of suggestions and issues for development related to this topic.

Queued issues:

• Experiment module: improve the layout of Experiment entities #686 (Effort: Large)
• Experiment Module: Update and customise the FarmOS landing page dashboard #679 (Effort: Large)
• Quick forms: consider if submission should direct to data entered #567 (Effort: Medium)
• Experiment Module: Create an experiment module dashbaord #682 (Effort: Medium). I assumed effort medium as very similar to the landing page, but please let me know if it is effort: large.
• Experiment Module: update left hand pick list for experiment module #683 (Effort: Medium) Ideally done in the same milestone as 682
• Experiment module: consistent naming for Researchers on Experiment Entities #684 (Effort: Medium)
• Experiment Module: allow Researchers to have multiple roles #685 (Effort: Medium)
• Mapping: Print maps from viewer #669 (Effort: Medium)
• Experiment module: update side bar options #709 (Effort: Medium)
• Quick forms: restrict the locations box on all quick forms to only include land assets with the type 'field' #698 (Effort: Small)
• Experiment Module: Add general search functionality to Experiment entities #687 (Effort: Small)
• Experiment Module: Add submit button to Proposals #658 (Effort: Small)
• Permissions: view own permissions/ roles #656 (Effort: Small)
• Experiment Proposals: Limit Field Locations to type 'Field' and 'Experiment Boundary' #448 (Effort: Small)
• Show all items in Plots tab! #362 (Effort: Small)
• Experiment Module: rename 'Related' button as 'Quick Links' #672 (Effort: Trivial)
• Rothamsted FarmOS: Filter by log id #655 (Effort: Trivial)
• Experiment module: Add Field Name as a filter option #670 (Effort: Trivial)

Monitor:

• Experiment Proposal: Improve the way proposals reference experiments and designs #453 (Effort: Extra Large)
• Feature request: Bulk upload for commercial assets #267 (Effort: Extra Large)
• FarmOS dashboard: remove/ review widgets (upcoming tasks, late tasks, metrics, active plans) #748 (Effort: Medium)
• FarmOS Core: Improve UI to hide hh:mm:ss from timestamp #375
• Experiment Module: Improve CSV upload process #516
• Experiment module: Add 'record field observation' button #566
• Useability: Improve error messages #579
• E-mail alerts: make rich text #626
• Improve UI access for restricted viewers #582
• Rothamsted Core: "All Fields" search functionality to landing page dashboard #676 (Effort: Medium, originally in 2.23.0 milestone but see comment here)
• Experiment module: Add quick links to Researchers #729 (Effort: Small)

FarmOS Core Issues

• Experiment Module: Move detailed management plans to Proposal and link with task list #661 (Not actually a FarmOS Core issue, but the Plan and Task modules need to be released so we can look at integrations)
• FarmOS core: viewing revisions that open in new tab #572
• Visualisation: Suppress entity number at the end of assets #628 (Drupal Core Issue)

Related:

• Experiment Module: Once approved, push information through to Experiment/ Design/ Plan entites #505 (Experiment module, new functionality)
• Experiment Module/ Visualisation: add Study Period ID to the the Proposals and Improve Filter Terms #648 (Experiment module, new functionality/ fields)
• Experiment Module: Improve Visualisation of Related Entities to Duplicate Plots and Experiment Boundaries #540 (Experiment module. Also an issue for data model/ data standardisation)
• Quick forms: remove completed assets/ plots from quick form lists #689 (Quality assurance)
• Experiment Module: Improve CSV upload process #516 (Experiment Module)

[aislinnpearson]

The below on ideas of how to improve the visualisation and user interaction with the experiment module from one of our scientists:

I was thinking how FarmOS could become easier for folks like me. I also get quite a few others talking to me about their field experiments – I think most sponsors will actually use FarmOS very infrequently, just a few times a year – and it is difficult to find stuff. One thought is on the front page to have just two options: a ‘For Researchers’ button and a ‘For non- researchers’ . Then, after clicking ‘For Researchers’, get options 3 ‘Find my experiment by field’, ‘Find my experiment by code and title’, ‘Find my experiment by sponsor’ – then for field and code, list all the fields, or all the experiments respectively – so I can choose from a list – (often I forget the exact code or title, so I’d rather look at a list than have to type in). A list of sponsors would also be nice – sometimes I want to find someone else's experiment

It is also really important to me to find details of previous experiments, not sure how best – at level 2, could add ‘find previous year's experiments’ or ‘find by harvest year’ – and then after selecting year, get the same options – by code and title, field, sponsor.

What do you think?

I’d also prefer ‘plans’ to be called ‘management plans’ – but I guess you get all sorts of conflicting opinions, would be impossible to incorporate them all!

This is linked to @paul121 idea of creating a Research Dashboard but would extend that idea to include a Commercial dashboard.

As an aside, I do think it is useful to differentiate between 'field plans' and 'management plans' (and maybe study periods)

[aislinnpearson]

Another request here from the arable operators:

"On the dashboard (so as soon as you open FarmOS) please can we have the functionality to find/ search for fields and plant assets."

Within the above context, I'd probably label these as something like 'Find a Field" and "Search for Crop Assets". For fields, you really only need to know the name (or could use the map to search by location, the functionality for which already exists). For crop assets it would be nice to have additional functionality to search for them by field (location), by crop type (wheat, etc), by variety and by season (Autumn 2024, Spring 2025, etc).

Although the point above suggests different tabs for researchers and "non-researchers" what has been requested by the farm staff seems very general to me so I wonder if we either combine these two requests into a single dashboard where you have the map at the top of the page, and below the map the four search fields; one for Fields, one for Crops one for Experiments and one for Management Plans (laid out in such a way that we could expand this in future if there was the need - for example 'find any asset' and 'find any log').

Beneath the map and general search fields, I wonder if we could then have a 'my FarmOS' section which displays the assets you are associated with. For the time being we would limit this to Experiments and Proposals, but in future I could see this as including plant assets and logs - for example, logs that you have entered which have been flagged as 'need review'. The ideal might be if this section was customisable so you can decide what you want to visualise, but that might be a pie in the sky idea... certainly something that would be a more long-term goal (if we find there is the user demand for it).

[paul121]

Related farmOS issues for improving the render/view pages of entities:

• Reorder and improve entity field rendering farmOS/farmOS#847
• Entity layout and minor UI changes farmOS/farmOS#832