Greenstand / Greenstand/treetracker-admin-client
Rebuilding the species management tool
- Dominant language
- JavaScript
- Stars
- 36
- Forks
- 212
- PR merge metrics
- No merged PRs in 30d
Description
## Species Management Redesign (Admin Panel)
### Problem
The current species tool has two major limitations:
1. **Centralized control only**
- Only Greenstand Super Admins can create and manage species.
2. **Unscoped dropdown in verification**
- When a user opens the dropdown in the verification tool, **all species** are listed.
- This creates:
- poor UX (long, cluttered list)
- slower verification
- higher risk of incorrect species selection
See related discussion: **#919**
---
### Current State
Below is the current species tool. Only Super Admins can add species, and all species appear globally in verification:
---
### Proposed Solution
Introduce a **two-layer species management system**:
---
### 1. Global Species Pool (Super Admin)
Super Admins manage the master list of species available across the platform.
**Capabilities:**
- Create / edit species
- Maintain canonical dataset (scientific name, common name, etc.)
- Ensure data consistency
**UI concept:**
**Outcome:**
- A clean, controlled **global species pool**
---
### 2. Organization-Level Species Selection (Org Admin)
Organization admins can select which species are relevant to their organization.
**Capabilities:**
- View global species list
- Activate/deactivate species for their organization
- Maintain a curated subset
**UI concept:**
**Outcome:**
- Each organization has a **custom species list**
---
### 3. Verification Tool Behavior
The species dropdown in the verification tool should:
- Only show **species activated for that organization**
- Not show the full global list
- Optionally support:
- search/autocomplete
- sorting by frequency or recency
**Result:**
- Faster verification workflow
- Reduced cognitive load
- Lower error rate
---
### Data Model (High-Level)
Species (global)
Organization
OrganizationSpecies
- org_id
- species_id
- is_active
---
### Edge Cases / Considerations
- **Global removal**
- If a species is removed globally, existing references should remain intact (historical data integrity)
- **Deactivation**
- Deactivated species should not appear in verification, but remain in historical records
- **Migration**
- Existing organizations may need:
- default species assignment
- or auto-selection based on historical usage
- **Permissions**
- Super Admin → full control
- Org Admin → selection only
---
### Expected Outcome
- Scalable species management across organizations
- Faster and more accurate verification
- Cleaner UI and improved usability
- Better data quality
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.