Enchance QSO details

[sq3rx]

I believe the Capture QSO panel should be extended with several additional fields:
Grid Locator, IOTA, QTH, DXCC prefix, and Name (to be automatically populated based on the callsign).

Additionally, the QSO model requires new fields for better tracking and advanced filtering options
QSL Status: Received/Sent status and delivery methods (e.g., Bureau, Direct).
External Integrations: LoTW statuses (ideally synchronized via LoTW integration) and Club Log status.
Awards Tracking: Dedicated fields for Grid, ARRL, IOTA, ITU, CQ, and Prefix.
Metadata & Environment:
Contest (text field).
Propagation Data (Save, K-index, A-index, SSN, SFI).
Distance: Automatically calculated based on the Grid Locator.

[brianbruff]

hi @sq3rx ,

ok let's see what we can do, this is somehwhat of a collection of ideas, if you can split out some sub issues with more detali it would be great.

also 3.9 dropped today with the initial statistics panel, i'm not a big stats chaser myself so would love if you can tell me where this is lacking

i've also still gotta get the lotw dont, i was hoping to get to this this w/end but ran out of time, but it's comming,,, the biggest issue is i need to re-familiarize myself with it all, i only every used it once.. but bear with me i'll get there.

cheers
ei6lf

[sq3rx]

Hi Brian,
I’ve been thinking about this feature enhancement (and even consulted with Gemini about it). In my opinion, we should at least cover the standard ADIF fields listed below.
We could split this issue into two parts:

• Capture Panel: For entering details during a QSO. (TBD)
• Edit Panel: For reviewing and modifying QSO details later.

For the edit/review functionality, we will need all the fields, ideally grouped into subpanels to keep the interface clean.

Regarding the DXCC mapping, I'm not sure how you currently map CALL to DXCC. I believe the proper way would be to use the cty.dat file, which could be downloaded along with the software to ensure accuracy.

Let me know what do you think about this.

CALL
QSO_DATE
TIME_ON
BAND
FREQ
MODE
RST_SENT
RST_RCVD
GRIDSQUARE
DXCC
COUNTRY
NAME
QTH
IOTA
STATE
QSL_SENT
QSL_RCVD
LOTW_QSL_SENT
LOTW_QSL_RCVD
STATION_CALLSIGN
MY_GRIDSQUARE
TX_PWR
COMMENT

[brianbruff]

ok i must renew my claude sub, it expired last week so i was thankful of a break :-)

I do have a gemini subscription so i'll throw this at it perhaps tomorrow and see how it gets on..

tnx for the detail

[brianbruff]

@claude review this request, plan an approach
strive for simplicity but allow complexity

advanced menu perhaps?

create me a detailed design spec

[claude]

Claude finished @brianbruff's task in 2m 51s —— View job

---

QSO Details Enhancement — Design Specification

Tasks:

• Understand the request
• Explore codebase (current QSO model, capture panel, ADIF contracts)
• Analyse architecture and patterns
• Draft detailed design specification

---

Executive Summary

The QSO data model already holds most of the requested fields internally (QslStatus, LotwStatus, ContestInfo, StationInfo, AdifExtra) — but the frontend capture panel exposes only a minimal set and the API DTOs don't surface them. This is primarily a UI exposure and API surface problem, not a data-modelling problem. A few fields do need to be added to the model (IOTA, TX_PWR, propagation data).

The guiding principle: simple by default, complex on demand — achieved through progressive disclosure using an expandable "Advanced" section in the capture panel, and a full-featured tabbed QSO edit modal.

---

Gap Analysis

Already in the Qso model (just not exposed)

Field	Model Location
Name	Qso.Name
Grid	Qso.Grid
Country / DXCC / Continent	Qso.Country, Qso.Dxcc, Qso.Continent
QTH	Qso.Station.Qth
State, CQ Zone, ITU Zone	Qso.Station.*
QSL Sent/Rcvd + dates	Qso.Qsl.Sent/Rcvd/SentDate/RcvdDate
LoTW Sent/Rcvd	Qso.Qsl.Lotw.Sent/Rcvd
eQSL Sent/Rcvd	Qso.Qsl.Eqsl.Sent/Rcvd
Contest ID, exchange, serials	Qso.Contest.*
Lat/Lon	Qso.Station.Latitude/Longitude

Missing — needs adding to model

Field	Notes
Iota (string)	e.g. EU-001. Currently goes to AdifExtra
TxPwr (double, watts)	Currently goes to AdifExtra
AIndex (int)	Propagation
KIndex (int)	Propagation
Sfi (int)	Solar Flux Index
Ssn (int)	Sunspot Number
Distance (int, km)	Auto-calculated from grids; also in ADIF DISTANCE
MyGrid (string)	Station's own grid — currently Station.Grid but needs surfacing
ClubLogStatus	Sent (Y/N) — Club Log confirmation

API DTOs — need extending

• CreateQsoRequest: only exposes ~12 fields; needs grid, IOTA, power, QSL, contest, and propagation fields
• UpdateQsoRequest: same gap
• QsoResponse: missing QSL detail, Contest, propagation fields

ADIF — already mostly mapped

A_INDEX, K_INDEX, SFI, TX_PWR, IOTA, DISTANCE currently land in AdifExtra; they just need first-class properties.

---

UI Design

1. Capture Panel — Progressive Disclosure

The existing LogEntryPlugin.tsx layout stays unchanged at the top. Below the current RST row, a toggle expands the "Advanced" section.

┌─────────────────────────────────────────────────────┐
│  [CALLSIGN]  [BAND▼]  [MODE▼]              [LOG IT] │
│  Name: ______ 🔒   Grid: ______                      │
│  Freq: ______  TX RST: ___  RX RST: ___              │
│  Comment: ____________________                       │
│                                                      │
│  ▶ Advanced  ──────────────────────────────────────  │
│  (collapsed by default, state persisted in          │
│   localStorage per layout panel)                     │
│                                                      │
│  When expanded:                                      │
│  ┌── Station ────────────────────────────────────┐  │
│  │  QTH: ________  IOTA: _______  TX Pwr: __ W  │  │
│  └───────────────────────────────────────────────┘  │
│  ┌── Contest ─────────────────────────────────────┐  │
│  │  Contest: _________  Sent: _____  Rcvd: ____  │  │
│  └───────────────────────────────────────────────┘  │
│  ┌── QSL ─────────────────────────────────────────┐  │
│  │  QSL Sent: [N▼]  Method: [Bureau▼]            │  │
│  │  LoTW: [─▼]  eQSL: [─▼]                       │  │
│  └───────────────────────────────────────────────┘  │
│  ┌── Propagation ─────────────────────────────────┐  │
│  │  SFI: ___  A: ___  K: ___  SSN: ___            │  │
│  │  [Fetch current conditions 🌐]                  │  │
│  └───────────────────────────────────────────────┘  │
└─────────────────────────────────────────────────────┘

UX notes:

• "Advanced" section remembers open/closed state per user in localStorage
• Each sub-section (Station, Contest, QSL, Propagation) is individually collapsible inside "Advanced"
• "Fetch current conditions" can hit a free solar data API (e.g. hamqsl.com/solarxml.php) and auto-fill SFI/A/K/SSN
• QSL Method dropdown: Bureau, Direct, Electronic, via Manager
• Auto-populate propagation at QSO log time as an option in settings

2. QSO Edit / Detail Panel (new panel type)

A new FlexLayout panel (QsoDetailPlugin) opens when double-clicking any log entry. Uses a tabbed layout:

QSO Detail: EA4ZX — 2026-04-16 14:32Z
┌──────────────────────────────────────────────────────┐
│ [Basic] [Station] [QSL & Awards] [Contest] [Propag.] │
├──────────────────────────────────────────────────────┤
│                                                      │
│  Basic tab:                                          │
│  Call: EA4ZX    Date: 2026-04-16  Time: 1432         │
│  Band: 20m   Mode: FT8   Freq: 14.074 MHz            │
│  RST Sent: -10   RST Rcvd: -12                       │
│  Name: John   Country: Spain   Grid: IM68             │
│  Comment: ____________________                       │
│  Notes: ____________________________                  │
│                               [Save]  [Delete]       │
└──────────────────────────────────────────────────────┘

Tab breakdown:

Tab	Fields
Basic	Call, Date, Time On/Off, Band, Mode, Freq, RST Sent/Rcvd, Name, Country, Grid, Comment, Notes
Station	QTH, IOTA, State, CQ Zone, ITU Zone, DXCC (read-only auto), Continent, Lat/Lon, My Grid, TX Pwr
QSL & Awards	QSL Sent (Y/N/M/R) + date + method; QSL Rcvd + date; LoTW Sent/Rcvd; eQSL Sent/Rcvd; Club Log status; Distance (auto-calc)
Contest	Contest ID, Serial Sent, Serial Rcvd, Exchange
Propagation	SFI, A-index, K-index, SSN

Awards & Tracking (within QSL tab or sub-section):

Rather than separate "awards tracking" fields (which are complex and typically calculated, not stored per-QSO), the recommendation is to track QSL confirmation status and derive award progress in the Statistics panel. Adding per-QSO award flags (DXCC confirmed, IOTA confirmed, Grid confirmed) as boolean checkboxes is low cost and enables future award tracking dashboards.

3. Log List Panel

The existing log list should gain configurable columns — users can toggle visibility of QSL Sent, LoTW Sent/Rcvd columns. A small QSL indicator (coloured dot) per row gives at-a-glance status.

---

Backend Changes

Phase 1 — Model additions (small, safe)

File: src/Log4YM.Contracts/Models/Qso.cs

// Add to Qso class
[BsonElement("iota")]        public string? Iota { get; set; }
[BsonElement("tx_pwr")]      public double? TxPwr { get; set; }
[BsonElement("distance")]    public int? Distance { get; set; }
[BsonElement("a_index")]     public int? AIndex { get; set; }
[BsonElement("k_index")]     public int? KIndex { get; set; }
[BsonElement("sfi")]         public int? Sfi { get; set; }
[BsonElement("ssn")]         public int? Ssn { get; set; }

Add ClubLog status alongside Lotw/Eqsl in QslStatus:

public ClubLogStatus? ClubLog { get; set; }
// ClubLogStatus { Sent: string? }

Phase 2 — DTO/API changes

Files: src/Log4YM.Contracts/Api/QsoDto.cs

Extend CreateQsoRequest and UpdateQsoRequest with all new fields. Extend QsoResponse to include:

• qsl (QslStatusDto with sent/rcvd/dates/method/lotw/eqsl/clublog)
• contest (ContestDto)
• propagation (PropagationDto: sfi, aIndex, kIndex, ssn)
• iota, txPwr, distance

Phase 3 — ADIF mapping

File: src/Log4YM.Server/Services/AdifService.cs

Move IOTA, TX_PWR, DISTANCE, A_INDEX, K_INDEX, SFI, SRX from AdifExtra fallback into first-class property mapping. Add QSL_VIA, PROP_MODE.

Phase 4 — Distance auto-calculation

When both Grid and Station.Grid (my grid) are set, calculate distance using the Maidenhead grid formula server-side on save. Store in Qso.Distance. Can also be a utility endpoint: GET /api/utils/distance?from=JO62&to=IM68.

---

Suggested Implementation Phases

Phase	Scope	Effort
1	Model fields + ADIF mapping (IOTA, TX_PWR, propagation)	Small — ~1 day
2	DTO/API surface expansion	Small — ~1 day
3	Capture panel "Advanced" section	Medium — ~2 days
4	QSO Edit/Detail panel (tabbed)	Medium-large — ~3–4 days
5	Log list QSL indicator columns	Small — ~1 day
6	Solar propagation auto-fetch	Small — ~0.5 day
7	Distance auto-calculation	Small — ~0.5 day
8	Club Log integration (live sync)	Large — depends on Club Log API

Phases 1–5 deliver most of the value. Phases 6–7 are quick wins. Phase 8 is deferred to a separate issue alongside LoTW sync.

---

Open Questions for @brianbruff

1. QSL method during capture — do you want Bureau/Direct/Electronic as a dropdown on capture, or only in the edit panel?
2. Propagation auto-fetch — happy to use hamqsl.com/solarxml.php (free, no auth)? Opt-in or opt-out?
3. My Grid — is this always the station's grid from settings, or do you want per-QSO override?
4. Awards tracking fields (Grid confirmed, IOTA confirmed, etc.) — checkbox per QSO, or defer entirely to the Statistics panel?
5. Club Log — is this in scope for this issue or a separate follow-up?
6. Distance — store in dB (km only, or also miles toggle)?

---