Import dxcc record#965
Conversation
Add support for downloading and importing LoTW DXCC credit records. Introduces a LOTW_DXCC enum and a new LogFormat::runQSOCreditImport() that matches QSOs by callsign/band/date and updates credit fields (credit_submitted/granted and app_lotw_credit_submitted/granted). ADI mapping and export params updated to include app_lotw_credit_* fields. LotwQSLDownloader gains a LotwDXCCCredits flag and uses a separate DXCC_CREDIT_API endpoint and parameter set; it calls runQSOCreditImport when DXCC mode is enabled. UI: DownloadQSLDialog adds a "LoTW DXCC Credits" group box, persists its state, and queues a DXCC download task. Also adds /build to .gitignore.
AdiFormat: default to midnight UTC when a record has a valid date but no valid time to avoid creating invalid QDateTime values. LogFormat: make DXCC credit import more robust by matching records using a ±1 day tolerance (JULIANDAY difference) instead of exact same-date-only matching, log found matches, and update every matching contact (handling multiple QSOs) by setting each record and committing changes; also improve error/debug messages and adjust row-count handling. UI (DownloadQSLDialog): replace the LoTW DXCC GroupBox with a one-off checkbox (lotwDXCCCheckBox), default it to unchecked/disabled when LoTW is not configured, stop persisting its state, and update the .ui layout and tabstops accordingly.
Remove handling of app_lotw_credit_submitted and app_lotw_credit_granted across the logging code. Changes remove setting these fields into SQL records (AdiFormat::contactFields2SQLRecord), remove them from DB->ADIF export parameters (AdiFormat::DB2ADIFExportParams), and stop checking them during QSO credit import condition updates (LogFormat::runQSOCreditImport). This cleans up unused/removed LoTW app credit fields.
Updated macOS build workflow to use macos-latest and modified installation steps for Qt libraries. Added notarization and signing steps for the app and DMG.
|
I am just saving the specification : https://lotw.arrl.org/lotw-help/developer-query-dxcc-credits/ I'm a little worried about performance. Model operations are very expensive. Can you please tell me when it should be turned off and when it should be turned on? |
|
This operation would be something run very infrequently. Really only after an operator would submit a DXCC Application and it is finalized to update their log with new credits - like annually. So it may make sense to not have it here but maybe somewhere else so people don't run it often. |
Updated macOS CI workflow to include additional dependencies, improved tagging support, and enhanced error handling for notarization and codesigning processes.
This workflow builds QLog for Windows using GitHub Actions, creating both a portable ZIP and a Qt IFW installer. It includes steps for setting up the environment, installing dependencies, building the application, and packaging the outputs.
|
@aa5sh , please, could you send me an example of your "LoTW" Credits result - you can send it to my personal email. You call URL with a param |
|
I just grabbed the URL from the LoTW page: I did try without and it downloaded the same file. But here it is described as being able to select the award account: I emailed the ADI file. Let me know you want my full ADI to try and look at it I can zip and email it as well. |
|
Based on your PR, specification and your ADI file, I prepared a new patch. Please, could you test it whether everything looks good ? It's in the |
|
Thanks I’ll take a look at it tonight.
… On May 18, 2026, at 7:43 AM, Ladislav ***@***.***> wrote:
foldynl
left a comment
(foldynl/QLog#965)
<#965 (comment)>
Based on your PR, specification and your ADI file, I prepared a new patch. Please, could you test it whether everything looks good ? It's in the devel_0.51 branch.
—
Reply to this email directly, view it on GitHub <#965 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AUEEMXS4SQOFBH6JR2MOAVL43MAQJAVCNFSM6AAAAACWV6TFH6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DINZXG44DQNZWGM>.
Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you were mentioned.
|
|
No need to rush it ;-) But thank you. |
|
It was pretty straightforward and worked. My only issue is I did get a bunch of Ambiguous matches that make sense. But there is no way for me to manually create those and with some they are valid contacts. I may have worked a DX station several times to make sure I got them - I know bad form - but that was before the modern club log near instant validation we have now. So would it be possible to maybe have a window pop up with the data from the download and the ambiguous contacts and let me pick which one to update? If not we would need to expose the Awards Granted field and a way to edit it. I don't believe off the top of my head that it exists in the detailed contact form. |
|
Please, could you send me an example impacted QSO(s). I already have your Awards ADI file; I just need QSOs and what you expect. The Awards field can be edited directly in the Logbook table. Direct editing still exists in Logbook Table. It is just not available in QSO Detail. What I am interested in now is what kind of ambiguities are occurring there. Maybe there is a bug somewhere in the update logic. |
|
Ok here is an example for VP6DX. This is an interesting one because I started with a blank database and imported a backup ADI. I told it no duplicates but in my opinion some of the QSOs should have been eliminated by that. But it appears the duplicate check has to be exact and some of my QSOs may be missing seconds or something similar causing the duplicate check to fail. That is why I attempted a remove duplicates PR to try and clean some of that up, but that is another issue potentially. My log may be messier than most for some reason. But it maybe instead of just this message for the ambiguous match it could indicate what it was granted like the successful ones above and some directions on how or where to update it manually. Because when I ran it I had 153 of these unmatched messages. 2008-02-23; VP6DX; 10m; ambiguous match: 2 QSOs But I also need to spend some time to clean up my log as well. |
|
I solved it so that it does not check uniqueness, but when there is a match, all QSOs on that given day that satisfy the match are updated. It's in the |
|
This looks good to me this time.
… On May 20, 2026, at 10:20 AM, Ladislav ***@***.***> wrote:
foldynl
left a comment
(foldynl/QLog#965)
<#965 (comment)>
I solved it so that it does not check uniqueness, but when there is a match, all QSOs on that given day that satisfy the match are updated. It's in the devel_0.51 branch.
—
Reply to this email directly, view it on GitHub <#965 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AUEEMXXPTEFHIEOQOFJRW7D43XEKJAVCNFSM6AAAAACWV6TFH6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DIOJZHA2TINBUGI>.
Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you were mentioned.
|
2 participants
This adds an option to pull down DXCC Credits granted and updates the log appropriately.
