Skip to content

[WIP] Enhance QSO details with additional fields#228

Draft
Claude wants to merge 2 commits into
mainfrom
claude/enhance-qso-details
Draft

[WIP] Enhance QSO details with additional fields#228
Claude wants to merge 2 commits into
mainfrom
claude/enhance-qso-details

Conversation

@Claude
Copy link
Copy Markdown
Contributor

@Claude Claude AI commented Apr 16, 2026

Thanks for asking me to work on this. I will get started on it and keep this PR's description up to date as I form a plan and make progress.


This section details on the original issue you should resolve

<issue_title>Enchance QSO details</issue_title>
<issue_description>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.

</issue_description>

Comments on the Issue (you are @claude[agent] in this section)

@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</comment_new>
<comment_new>@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</comment_new>

@Claude Claude AI linked an issue Apr 16, 2026 that may be closed by this pull request
- Complete analysis of existing QSO model and UI
- Three-phased implementation approach
- Progressive disclosure UI design (simple by default, advanced when needed)
- ADIF 3.1.4 field mappings
- Grid locator, IOTA, QTH, propagation data, QSL tracking
- Club Log and LoTW integration planning
- Awards tracking system
- Distance calculation from grid locators
- Backward compatible data model changes

Agent-Logs-Url: https://github.com/brianbruff/Log4YM/sessions/c4d51fa7-b137-4c02-8aae-f5d9d1a9bbf9

Co-authored-by: brianbruff <753297+brianbruff@users.noreply.github.com>
@Claude Claude AI requested a review from brianbruff April 16, 2026 21:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Enchance QSO details

2 participants