Greenstand / Greenstand/treetracker-admin-client
Capture matching tool - new workflow
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 36
- Forks
- 212
- PR merge metrics
- No merged PRs in 30d
Description
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.
[^1]: there could be an additional filter for big organizations,
[^2]: additional backend work needed to cater for that
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by reviewing the existing admin-panel workflow and use the requested grower and session lists as the basis for UX exploration; done means an agreed UX direction that covers the listed fields, filtering needs, and the backend boolean requirement.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react
- Domain
- design, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100