From d16ff05308c1e5ea6c26ee0030b6d0ec70a76d70 Mon Sep 17 00:00:00 2001 From: Andreas Kristiansen <6977712+AndreasK79@users.noreply.github.com> Date: Sun, 14 Dec 2025 14:21:27 +0100 Subject: [PATCH] Removed information in dialog, and instead linked to the Wiki --- application/controllers/Logbookadvanced.php | 4 - .../views/logbookadvanced/dbtoolsdialog.php | 5 +- .../logbookadvanced/dbtoolsinformation.php | 170 ------------------ assets/js/sections/logbookadvanced.js | 13 -- 4 files changed, 2 insertions(+), 190 deletions(-) delete mode 100644 application/views/logbookadvanced/dbtoolsinformation.php diff --git a/application/controllers/Logbookadvanced.php b/application/controllers/Logbookadvanced.php index ab64bfd85..e1787e6f2 100644 --- a/application/controllers/Logbookadvanced.php +++ b/application/controllers/Logbookadvanced.php @@ -888,10 +888,6 @@ class Logbookadvanced extends CI_Controller { $this->load->view('logbookadvanced/dbtoolsdialog'); } - public function dbtoolsInfo() { - $this->load->view('logbookadvanced/dbtoolsinformation'); - } - public function checkDb() { if(!clubaccess_check(9)) return; diff --git a/application/views/logbookadvanced/dbtoolsdialog.php b/application/views/logbookadvanced/dbtoolsdialog.php index 7fd0359ad..cf35b280d 100644 --- a/application/views/logbookadvanced/dbtoolsdialog.php +++ b/application/views/logbookadvanced/dbtoolsdialog.php @@ -2,9 +2,8 @@
- + +
diff --git a/application/views/logbookadvanced/dbtoolsinformation.php b/application/views/logbookadvanced/dbtoolsinformation.php deleted file mode 100644 index 49fcd22f9..000000000 --- a/application/views/logbookadvanced/dbtoolsinformation.php +++ /dev/null @@ -1,170 +0,0 @@ -
Wavelog Database Tools (DBTools)
- -

The Database Tools module in Wavelog provides a comprehensive suite of utilities for maintaining data integrity and repairing common issues in your logbook data. These tools are accessible through the Advanced Logbook interface and are designed to help operators keep their QSO records accurate and complete.

- -
Overview
- -

DBTools offers automated checking and fixing functionality for various types of QSO metadata that may be missing, incorrect, or outdated. The tools perform validation against authoritative sources and provide batch processing capabilities to efficiently handle large logbooks.

- -
Available Tools
- -
-
1. CQ Zone Fixer
-
    -
  • Purpose: Updates missing or incorrect CQ zone information
    • -
  • Function: Validates QSO coordinates against CQ zone boundaries
    • -
  • Use Case: Essential for award applications like CQ DX Field Day, CQ WW DX Contest, and other CQ-sponsored awards
    • -
-
- -
-
2. ITU Zone Fixer
-
    -
  • Purpose: Updates missing or incorrect ITU zone information
    • -
  • Function: Cross-references station locations with ITU zone definitions
    • -
  • Use Case: Required for ITU-sponsored awards and contests
    • -
-
- -
-
3. Continent Fixer
-
    -
  • Purpose: Updates missing or incorrect continent information
    • -
  • Function: Determines continent based on station coordinates or DXCC entity
    • -
  • Use Case: Useful for continental award tracking and statistics
    • -
-
- -
-
4. State/Province Fixer
-
    -
  • Purpose: Updates missing or incorrect state or province information
    • -
  • Function: Uses grid square and location data to determine administrative divisions
    • -
  • Use Case: Critical for WAS (Worked All States) and similar award programs
    • -
-
- -
-
5. Distance Calculator
-
    -
  • Purpose: Calculates and updates distance information for QSOs
    • -
  • Function: Computes great-circle distances between stations
    • -
  • Use Case: Important for distance-based awards and personal statistics
    • -
-
- -
-
6. DXCC Data Validator
-
    -
  • Purpose: Identifies QSOs missing DXCC information
    • -
  • Function: Cross-references callsigns and timestamps with DXCC entity database
    • -
  • Use Case: Essential for DXCC award tracking and eQSL/LoTW verification
    • -
-
- -
-
7. DXCC Re-check Tool
-
    -
  • Purpose: Re-evaluates all QSOs for correct DXCC assignment
    • -
  • Function: Overwrites existing DXCC data using current Wavelog database
    • -
  • Use Case: Useful when DXCC boundaries have changed or initial imports were incorrect
    • -
-
- Warning: This tool will overwrite ALL existing DXCC information -
-
-
-
How It Works
- -
Check Process
-
    -
  1. Scanning: Each tool performs a comprehensive scan of the logbook database
    2. -
  2. Validation: Data is cross-referenced against authoritative sources (DXCC lists, coordinate databases, zone definitions)
    3. -
  3. Reporting: Results display the number of records needing attention and provide detailed breakdowns
    4. -
- -
Batch Processing
-
    -
  • Tools can process thousands of QSOs efficiently
    • -
  • Progress indicators show real-time processing status
    • -
  • Results are categorized by fix type and success rate
    • -
- -
Safety Features
-
    -
  • Most tools operate in "check" mode first, allowing review before applying fixes
    • -
  • Detailed logging shows which records would be modified
    • -
  • Backup recommendations are provided before bulk operations
    • -
- -
Access and Usage
- -
Location
-
    -
  • Navigate to Advanced Logbook → DBTools tab
    • -
  • Requires appropriate user permissions (typically admin or logbook owner)
    • -
- -
Interface
-
    -
  • Left Panel: Tool selection and action buttons
    • -
  • Right Panel: Real-time results and progress information
    • -
  • Actions: Check, Fix, or Run buttons depending on tool type
    • -
- -
Workflow
-
- Step 1: Use "Check" buttons to identify issues -
-
- Step 2: Review results and affected QSOs -
-
- Step 3: Apply fixes using the appropriate action button -
-
- Step 4: Monitor progress and review final results -
-
-
Technical Implementation
- -
Data Sources
-
    -
  • DXCC entity database from official IARU listings
    • -
  • Coordinate systems using WGS-84 standard
    • -
  • Zone definitions from CQ and ITU specifications
    • -
  • Administrative boundary data for state/province determination
    • -
- -
Performance Considerations
-
    -
  • Batch processing optimized for large logbooks
    • -
  • Memory-efficient database queries
    • -
  • Progress tracking for long-running operations
    • -
- -
Best Practices
- -
    -
  1. Backup First: Always create a logbook backup before running bulk fixes
    2. -
  2. Test Small: Run checks on small date ranges first to validate results
    3. -
  3. Review Results: Carefully examine what will be changed before applying fixes
    4. -
  4. Monitor Progress: For large logbooks, allow adequate processing time
    5. -
  5. Verify After: Spot-check results after fixes are applied to ensure accuracy
    6. -
- -
Troubleshooting
- -
Common Issues
-
    -
  • Memory Limits: Large logbooks may require increased PHP memory limits
    • -
  • Timeout Issues: Long operations may need extended execution time limits
    • -
  • Coordinate Accuracy: Some fixes depend on accurate grid square data
    • -
- -
Error Handling
-
    -
  • Tools provide detailed error messages for failed operations
    • -
  • Rollback capabilities for interrupted processes
    • -
  • Logging of skipped records with reason codes
    • -
diff --git a/assets/js/sections/logbookadvanced.js b/assets/js/sections/logbookadvanced.js index 595f15658..ed07fe406 100644 --- a/assets/js/sections/logbookadvanced.js +++ b/assets/js/sections/logbookadvanced.js @@ -2231,19 +2231,6 @@ function saveOptions() { }); } - function getDbToolsInfo() { - $('#getDbToolsInfoBtn').prop("disabled", true).addClass("running"); - $.ajax({ - url: base_url + 'index.php/logbookadvanced/dbtoolsInfo', - type: 'post', - success: function (html) { - $('#getDbToolsInfoBtn').prop("disabled", false).removeClass("running"); - $('.result').html(html); - } - }); - - } - function fixMissingDxcc(all) { if (all === true) { $('#updateDxccBtn').prop("disabled", true).addClass("running");