Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
Search
Verified vs Confirmed on LoTW
开云体育LotW status is not my complaint. It? is the overall personify and other logins to ARRL systems such as reading QST that are a pain. The old way of going to ONE place ad having ONE login method to go to what you wat to do was much better and less confusing than the hateful system now. ? Outlook LT Gil W0MN Hierro Candente Batir de Repente 44.08226 N 92.51265 W EN34rb ? ? From: [email protected] <[email protected]> On Behalf Of wc3w via groups.io
Sent: Sunday, March 30, 2025 7:29 AM To: [email protected] Subject: Re: [DXLab] Verified vs Confirmed on LoTW ? Not so complicated: Confirmed QSOs
So:
? Verified QSOs
So:
-- W0MN EN34rb 44.08226 N 92.51265 W Hierro candente, batir de repente HP Laptop |
|
Weeks ago I made an application to lotw for new credits, less than 40. After a few more weeks, the application was completed, all good. Then several?days later over 30 previously?credited QSOs showed up as pending.? When I looked up these now pending credit QSO, they were also shown as granted! After several?exchanges with the?help desk, it was fixed. h]the issue?was delclered?to b The?issue was said to be a "software glitch" Thanks Dan KC2STA ? On Sat, Mar 29, 2025 at 9:33?AM Salvatore Besso via <salvatore.besso=[email protected]> wrote: hello, --
Dan Ziolkowski KC2STA SKCC #4290T Ubuntu LINUX |
|
The problem reported in this thread is not "user confusion over terminology", as implied by the post below. The problem is that LoTW has begun misreporting "DXCC Credit" status for some QSOs confirmed via LoTW and submitted for DXCC credit.
73, Dave, AA6YQ Not so complicated: Confirmed QSOs * A confirmed QSO means that both parties (you and the other operator) have uploaded matching logs to LoTW. * The system checks the date, time, frequency, and mode, and if they match within certain tolerances, it confirms the QSO. * This is what counts toward award credit (e.g., DXCC, WAS, VUCC). So: Confirmed = Matched and valid in LoTW = Counts for awards. ________________________________ ? Verified QSOs * A verified QSO is typically one that has already been used for award credit, such as a confirmed QSO you've applied toward your DXCC or WAS certificate. * It’s like a step beyond "confirmed" — it's confirmed and officially credited in your award application. So: Verified = Confirmed + Used for award credit (and accepted). |
|
give me an example? A qso has been confirmed , submitted and verified, and now doesnt show, or the opposite, LOTW thinks and entity has been verified, but hasnt? last I looked ( a few weeks ago) my LOTW records, dxcc records, and my dxkeeper records all matched, I can look again, if I know what I am looking for.
toggle quoted message
Show quoted text
------ Original Message ------
From "Dave AA6YQ" <aa6yq@...> To [email protected] Date 3/30/2025 11:19:09 AM Subject Re: [DXLab] Verified vs Confirmed on LoTW The problem reported in this thread is not "user confusion over terminology", as implied by the post below. The problem is that LoTW has begun misreporting "DXCC Credit" status for some QSOs confirmed via LoTW and submitted for DXCC credit. |
|
+ AA6YQ comments below
Weeks ago I made an application to lotw for new credits, less than 40. After a few more weeks, the application was completed, all good. Then several days later over 30 previously credited QSOs showed up as pending. When I looked up these now pending credit QSO, they were also shown as granted! After several exchanges with the help desk, it was fixed. h]the issue was delclered to b The issue was said to be a "software glitch" + A lame attempt to avoid acknowledging a defect in the software or process - as if "glitches" are everyday occurrences that are to be expected and tolerated when using computers. Nothing could be further from the truth! + All developers make mistakes. Strong developers test assiduously, and find most of their mistakes before making a public release. When mistakes do reach a public release, they should be acknowledged for what they are - defects - and promptly corrected. 73, Dave, AA6YQ |
|
+ AA6YQ comments below
give me an example? + See the first message in this thread, posted by Bj?rn SM7IUN. A qso has been confirmed , submitted and verified, and now doesnt show, or the opposite, LOTW thinks and entity has been verified, but hasnt? last I looked ( a few weeks ago) my LOTW records, dxcc records, and my dxkeeper records all matched, I can look again, if I know what I am looking for. + The defective behavior occurs with some QSOs, but not all. As I posted earlier in this thread, Jon Bloom -- the original LoTW developer who is again working on LOTW -- has acknowledged that this defective behavior has begun happening, but won't explain why. All he will say is "contact the LoTW Help Desk to get it corrected". 73, Dave, AA6YQ |
|
On 2025-03-30 11:25 AM, Jamie WW3S wrote:
give me an example? A qso has been confirmed , submitted and verified,The report that started this thread was that [some] QSOs confirmed by LotW were being granted credit (verified) as *card* QSOs. Since the current "connection" between LotW and the DXCC application is by sneakernet, I would postulate that the "glitch" is human error - that is the data entry person is inadvertently indicating that the QSOs (credits) being entered are cards rather than LotW confirmations. 73, ... Joe, W4TV On 2025-03-30 11:25 AM, Jamie WW3S wrote: give me an example? A qso has been confirmed , submitted and verified, and now doesnt show, or the opposite, LOTW thinks and entity has been verified, but hasnt? last I looked ( a few weeks ago) my LOTW records, dxcc records, and my dxkeeper records all matched, I can look again, if I know what I am looking for. |
|
Where on the dxcc record does it state whether its card or lotw, and why does it matter?
toggle quoted message
Show quoted text
On Mar 30, 2025, at 11:53?AM, Joe Subich, W4TV <lists@...> wrote: |
|
On 2025-03-30 12:21 PM, Jamie WW3S wrote:
Where on the dxcc record does it state whether its card or lotw, and why does it matter?Credits are reported differently in LotW Account credit status depending on whether they are LotW credits or QSL cards. Applications can only be made using all cards or all LotW credits. DXKeeper tracks credits by source (card or LotW) and prepares submissions differently based on the source. Record keeping is made much more difficult if LotW reports the wrong source of credit (when it has kept the two separate for 20 years). 73, ... Joe, W4TV On 2025-03-30 12:21 PM, Jamie WW3S wrote: Where on the dxcc record does it state whether its card or lotw, and why does it matter?On Mar 30, 2025, at 11:53?AM, Joe Subich, W4TV <lists@...> wrote: |
|
you cant submit a hybrid (cards+lotw) application any more?
toggle quoted message
Show quoted text
------ Original Message ------
From "Joe Subich, W4TV" <lists@...> To [email protected] Date 3/30/2025 12:32:08 PM Subject Re: [DXLab] Verified vs Confirmed on LoTW
|
|
DXCC entities verified by cards only have the information from the card that applies to DXCC, so if that particular card is also good for WAZ or VUCC you would have to resubmit it for the other award. LOTW confirmations/verifications contain that extra info so you can more easily get credit for other awards.
73, Chuck KM3V |
|
Where on the dxcc record does it state whether its card or lotw, and why does it matter?
toggle quoted message
Show quoted text
+ The report was not solely "card confirmation vs LOTW confirmation". The report was "DXCC credit granted" vs "No DXCC credit granted". Dave On Mar 30, 2025, at 11:53?AM, Joe Subich, W4TV <lists@...> wrote: |
|
ahh, I thought there had to be more than just card vs lotw credit.....
toggle quoted message
Show quoted text
------ Original Message ------
From "Dave AA6YQ" <aa6yq@...> To [email protected] Date 3/30/2025 1:24:27 PM Subject Re: [DXLab] Verified vs Confirmed on LoTW Where on the dxcc record does it state whether its card or lotw, and why does it matter? |
Gilbert Baron W0MN
to navigate to use esc to dismiss