-
-
Notifications
You must be signed in to change notification settings - Fork 192
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Capture matching tool - new workflow #1098
Comments
A map view of the sessions will be a great help to visualize the areas that should be matched. http://dev.dadiorchen.com/ is Dadiorchen´s first prototype to show what can be done with session data. Standard filters should include a date start and end. |
Priyanka and I have started to work on the UX and should have a draft by Thursday 8/3. |
@meghasahgal What's the status of this? |
@pranavkparti We have some initial designs that we need to review with Shubham. Am scheduling a meeting with him and Priyanka for this Tuesday so hopefully we can share with the rest of the team soon. |
The current workflow is proving to be unpractical. In order to make the capture matching more contextual we suggest the following workflow.
Operator gets shown a list of all growers 1 in their admin panel (org) with the following info:
GrowerID, Name+Surname, OrgName, number of approved trees, number of unapproved trees, number of rejected trees and number of unmatched sessions, number of matched sessions.
When clicking on a specific grower there should be a list of sessions with date, session matched (bolean) 2, amount of captures matched and amount of captures not able to be matched
We need UX support first.
Footnotes
there could be an additional filter for big organizations, ↩
additional backend work needed to cater for that ↩
The text was updated successfully, but these errors were encountered: