patrickrb / patrickrb/nextlog

Duplicate Detection & Bulk Management

Open
#13 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
TypeScript
Stars
6
Forks
1
PR merge metrics
No merged PRs in 30d

Description

Description

Add data cleanup and management tools to maintain logbook quality and enable efficient bulk operations.

Current State

  • Basic ADIF import with duplicate detection
  • Individual contact editing only
  • No data validation tools
  • No bulk operations

Required Features

Duplicate Detection
  • Advanced duplicate detection beyond current import logic
  • Configurable duplicate criteria (time window, frequency tolerance)
  • Duplicate contact review interface
  • Merge duplicate contacts functionality
  • Keep best quality data during merge
  • Duplicate prevention during manual entry
Bulk Editing
  • Select multiple contacts for bulk operations
  • Bulk update common fields (QSL status, notes, station)
  • Bulk delete with confirmation
  • Bulk QSL status updates
  • Bulk station assignment
  • Undo/redo for bulk operations
Data Validation
  • Validate callsign formats
  • Check frequency/band consistency
  • Validate grid locator formats
  • Check date/time reasonableness
  • RST report validation
  • Country/zone consistency checks
Data Cleanup Tools
  • Find and fix common data issues
  • Standardize country names
  • Fix grid locator formats
  • Normalize mode names
  • Clean up QTH formatting
  • Remove trailing spaces and invalid characters
Import Improvements
  • Enhanced conflict resolution during import
  • Preview import changes before applying
  • Import statistics and error reporting
  • Custom field mapping for imports
  • Import rollback functionality
Data Quality Dashboard
  • Data quality metrics and scores
  • Common issues summary
  • Validation error reports
  • Data completeness statistics
  • Suggestions for improvements
Backup & Restore
  • Create full logbook backups
  • Selective backup by date range or criteria
  • Restore from backup files
  • Backup scheduling and automation
  • Export for external backup storage
Data Migration Tools
  • Import from other logging software
  • Convert between different ADIF versions
  • Data format conversion utilities
  • Legacy data cleanup tools

Implementation Notes

  • Use transaction-based operations for safety
  • Implement comprehensive undo functionality
  • Add progress tracking for long-running operations
  • Provide detailed operation logging

Database Changes

  • Add operation history/audit tables
  • Add data validation constraint functions
  • Add backup/restore stored procedures
  • Optimize for bulk operations

UI Components

  • Bulk selection interface
  • Duplicate resolution dialog
  • Data validation report views
  • Progress indicators for bulk operations
  • Confirmation dialogs for destructive operations

Safety Features

  • Confirmation dialogs for bulk operations
  • Automatic backup before major changes
  • Operation rollback capabilities
  • Data integrity checks
  • User permission validation

Acceptance Criteria

  • Users can detect and merge duplicate contacts
  • Bulk editing works efficiently for large selections
  • Data validation catches common errors
  • Import conflicts are resolved gracefully
  • Backup and restore functions work reliably
  • All operations are logged for audit trail

Priority

Medium - Important for maintaining data quality

Dependencies

  • Transaction support in database layer
  • Comprehensive logging system
  • User permission system

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named. Start by locating the existing ADIF import and individual contact editing flows, then map the database, API, and UI boundaries for one narrowly scoped feature. Done would require the relevant acceptance criterion, safety behavior, and audit or rollback expectations to be implemented and tested.

Written by the indexing model from the issue text.

Assessment

Tech stack
nextjs, postgresql, typescript
Domain
databases, full-stack
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.