bayakarisa/Zea-Watch

Add Export/Download Functionality for Analysis Reports

Open

#20 opened on Nov 10, 2025

View on GitHub
 (0 comments) (0 reactions) (0 assignees)TypeScript (1 fork)auto 404
enhancementgood first issue

Repository metrics

Stars
 (1 star)
PR merge metrics
 (No merged PRs in 30d)

Description

Farmers need to save and share analysis results with agronomists, extension officers, or for their own records. Proposed Features

Download individual analysis as PDF

Include image, disease name, confidence, description, recommendations Add timestamp and ZeaWatch branding Formatted for printing

Download history as CSV

Export all or filtered analyses Include: date, disease, confidence, filename Useful for record-keeping

Share via WhatsApp/SMS (Mobile)

Generate shareable link Send summary text with key info

Acceptance Criteria

Add "Download PDF" button on each analysis result Add "Export History" button above history list PDF includes all relevant information and is print-friendly CSV export works with filtered results Add share button for mobile users

Technical Notes

Consider using jsPDF or html2pdf for PDF generation Use papaparse for CSV export (already installed)

Contributor guide

Research direction
Examine the analysis result component to understand the data structure, then implement PDF generation using jsPDF and CSV export using papaparse. Add buttons in the UI and test locally.
Tech stack
typescript
Domain
frontend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitTypeScriptnpm
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70