eQSL Upload/Download Integration
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- TypeScript
- Stars
- 6
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Description
Add eQSL support similar to LoTW integration for electronic QSL confirmation tracking.
Current State
- No eQSL integration
- Manual QSL status updates only
- LoTW integration planned/in development
Required Features
eQSL Upload
- Upload QSOs to eQSL.cc in ADIF format
- Support for selective uploads (date range, band, mode)
- eQSL-specific field mapping
- Upload progress tracking and status
- Error handling and retry logic
- Batch upload optimization
eQSL Download
- Download eQSL confirmations from eQSL.cc
- Support for incremental downloads
- Download confirmations by date range
- Progress tracking for large downloads
- Automatic scheduling options
eQSL Authentication
- Store eQSL credentials securely (encrypted)
- Username/password authentication
- Connection testing and validation
- Multi-station eQSL account support
- Credential management interface
Confirmation Matching
- Match eQSL confirmations with existing QSOs
- Update QSL_EQSL status automatically
- Handle partial matches and discrepancies
- Confirmation timestamp tracking
- Conflict resolution interface
eQSL Card Management
- View received eQSL cards
- eQSL card gallery integration
- Download eQSL card images
- eQSL card quality ratings
- Archive management for eQSL cards
UI Integration
- eQSL settings in station configuration
- eQSL upload/download dialogs
- eQSL status indicators in contact lists
- eQSL sync dashboard
- Upload/download history viewer
Status Tracking
- eQSL confirmation status per QSO
- eQSL pending/confirmed indicators
- eQSL statistics and progress
- Failed upload/download tracking
- eQSL vs LoTW comparison views
Error Handling
- Network connectivity issues
- eQSL.cc service unavailability
- Authentication failures
- Invalid ADIF data handling
- Rate limiting respect
eQSL.cc API Integration
Upload API
- ADIF file upload via HTTP POST
- Response parsing and status checking
- Upload confirmation handling
- Error code interpretation
Download API
- Confirmation download via eQSL inbox
- ADIF format confirmation parsing
- Incremental download support
- Download status tracking
Authentication Flow
- Login credential verification
- Session management
- Secure password storage
- Account validation
Implementation Notes
- Study eQSL.cc API documentation
- Implement secure credential storage
- Add background job processing
- Respect eQSL.cc rate limits and terms of service
- Provide comprehensive error logging
Database Changes
- Add eQSL sync tracking table
- Add eQSL confirmation fields to contacts
- Add eQSL operation log table
- Encrypt eQSL credentials in stations table
Configuration Options
- eQSL API endpoint configuration
- Upload/download timeout settings
- Automatic sync preferences
- Conflict resolution settings
- eQSL card storage options
Acceptance Criteria
- Users can upload QSOs to eQSL.cc
- Confirmations download and match automatically
- QSL status updates from eQSL confirmations
- eQSL cards can be viewed and managed
- Error conditions provide clear feedback
- Secure credential management works properly
Priority
Medium - Important secondary QSL confirmation method
Dependencies
- Secure credential storage system
- Background job processing
- HTTP client for API integration
- ADIF processing (✅ already implemented)
Notes
- eQSL integration is secondary to LoTW but still widely used
- Consider implementing after LoTW integration is complete
- Many operators use both LoTW and eQSL for maximum confirmation coverage
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 reading the eQSL.cc API documentation and the planned LoTW integration, then define the scope across upload, download, authentication, matching, database, and UI work; done means the listed acceptance criteria are met with secure credentials and clear error feedback.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nextjs, postgresql, react, typescript
- Domain
- api, database, frontend, full-stack, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100