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
DXCC Verification Discrepancy resolution how-to?
¿ªÔÆÌåÓýI¡¯m having some difficulty making sense of the DXCC Verification Discrepancies report and how to resolve what shows up on the report. There are two specific cases I¡¯m dealing with. ? One example is the report contains a record for say entity=TK, mode=CW, Log Status=V, ARRL Status=null. On the ARRL LOTW website, my account has an entry for TK5EP, 15M, CW. This matches exactly a logbook entry which also has LoTW Receive Status=V. This credit is missing from the list of downloaded credits, which has been updated. I don¡¯t understand the discrepancy and how best to resolve it? ? There other example which I believe I have an explanation is from QSL cards that were submitted many years ago, long before LoTW. The LoTW credits do not contain band or mode, just entity. The discrepancy report for these same DXCC entities call out band and/or mode discrepancies. I believe this to be caused by the LoTW credit missing both band and mode with the QSL status=V in the log. The question again is how best to resolve this discrepancy? ? I¡¯ve tried both Autolink and Repair for LoTW. Perhaps I should reset the LoTW QSL status and resend the QSO¡¯s to be processed again? For the paper QSL¡¯s, do I need to resend the cards for band/mode credit? ? Thanks for any input and/or suggestions. ? Ken WB1DX ?
? Sent from for Windows 10 ? |
From: dxlab@... [mailto:dxlab@...]AA6YQ comments below Sent: Saturday, February 27, 2016 6:47 PM To: dxlab@... Subject: [dxlab] DXCC Verification Discrepancy resolution how-to? I¡¯m having some difficulty making sense of the DXCC Verification Discrepancies report and how to resolve what shows up on the report. There are two specific cases I¡¯m dealing with. One example is the report contains a record for say entity=TK, mode=CW, Log Status=V, ARRL Status=null. On the ARRL LOTW website, my account has an entry for TK5EP, 15M, CW. This matches exactly a logbook entry which also has LoTW Receive Status=V. This credit is missing from the list of downloaded credits, which has been updated. I don¡¯t understand the discrepancy and how best to resolve it? There other example which I believe I have an explanation is from QSL cards that were submitted many years ago, long before LoTW. The LoTW credits do not contain band or mode, just entity.Log into your LoTW web account and view your DXCC Award Credit Matrix. (I can't cite a URL in "Using LoTW" that explains how to do this because LoTW is down for scheduled maintenance at this moment). Does it show that DXCC credit has been granted for TK in CW? That¡¯s not correct. DXCC credits created by submitting an LoTW confirmation always specify the entity, band, and mode. The discrepancy report for these same DXCC entities call out band and/or mode discrepancies. I believe this to be caused by the LoTW credit missing both band and mode with the QSL status=V in the log. The question again is how best to resolve this discrepancy? How/why was the QSL status set to 'V' in the logged QSO? LoTW confirmations are not DXCC Credits; an LoTW Confirmation must be included in a DXCC application to generate a DXCC Credit. I¡¯ve tried both Autolink and Repair for LoTW.DXCC Credits generated from QSL cards can contain errors in their callsign, date, band, and mode fields. Such credits must be manually linked. <>Neither will link a credit to a QSO unless the credit exactly matches the QSO. ¡°Imperfect¡± credits must be manually linked to their QSOs, as is described in Perhaps I should reset the LoTW QSL status and resend the QSO¡¯s to be processed again? For the paper QSL¡¯s, do I need to resend the cards for band/mode credit?That will produce a result no different than what you now see. 73,If the expected credit does not appear in your DXCC Award Credit Matrix, yes ¨C though you should first contact the DXCC desk and see if they can determine how a DXCC credit previously granted has disappeared. Dave, AA6YQ |
|
Hi Dave. Thanks for the quick reply. I am in good shape now. Most of the ¡°V¡±erified were from my first DXCC card submission. I went through that submission way back when and manually marked them ¡°V¡±erified in logger. These particular credits are for entity only. I¡¯m not sure why that is but I¡¯ll follow up with DXCC desk and figure that out. What I ended up doing was using the ¡°E¡±ntity option on those contacts. I¡¯m not sure when that option, and the others were introduced, but I¡¯ve been sidelined for several years and just now getting things going again.
As far as the others, like the EK example, the DXCC didn¡¯t have it marked as a credit for me for that band/mode. I must have at some point jumped the gun and marked it and a few others like it ¡°V¡±erified by mistake. Everything checks out now. Your software is a real joy to use, thanks for that. 73, Ken WB1DX Sent from Mail for Windows 10 From: 'Dave AA6YQ' aa6yq@... [dxlab] Sent: Saturday, February 27, 2016 11:42 PM To: dxlab@... Subject: RE: [dxlab] DXCC Verification Discrepancy resolution how-to? ? From: dxlab@... [mailto:dxlab@...]AA6YQ comments below Sent: Saturday, February 27, 2016 6:47 PM To: dxlab@... Subject: [dxlab] DXCC Verification Discrepancy resolution how-to? I¡¯m having some difficulty making sense of the DXCC Verification Discrepancies report and how to resolve what shows up on the report. There are two specific cases I¡¯m dealing with. One example is the report contains a record for say entity=TK, mode=CW, Log Status=V, ARRL Status=null. On the ARRL LOTW website, my account has an entry for TK5EP, 15M, CW. This matches exactly a logbook entry which also has LoTW Receive Status=V. This credit is missing from the list of downloaded credits, which has been updated. I don¡¯t understand the discrepancy and how best to resolve it? There other example which I believe I have an explanation is from QSL cards that were submitted many years ago, long before LoTW. The LoTW credits do not contain band or mode, just entity.Log into your LoTW web account and view your DXCC Award Credit Matrix. (I can't cite a URL in "Using LoTW" that explains how to do this because LoTW is down for scheduled maintenance at this moment). Does it show that DXCC credit has been granted for TK in CW? The discrepancy report for these same DXCC entities call out band and/or mode discrepancies. I believe this to be caused by the LoTW credit missing both band and mode with the QSL status=V in the log. The question again is how best to resolve this discrepancy?That¡¯s not correct. DXCC credits created by submitting an LoTW confirmation always specify the entity, band, and mode. How/why was the QSL status set to 'V' in the logged QSO? LoTW confirmations are not DXCC Credits; an LoTW Confirmation must be included in a DXCC application to generate a DXCC Credit. I¡¯ve tried both Autolink and Repair for LoTW.DXCC Credits generated from QSL cards can contain errors in their callsign, date, band, and mode fields. Such credits must be manually linked. <>Neither will link a credit to a QSO unless the credit exactly matches the QSO. ¡°Imperfect¡± credits must be manually linked to their QSOs, as is described in Perhaps I should reset the LoTW QSL status and resend the QSO¡¯s to be processed again? For the paper QSL¡¯s, do I need to resend the cards for band/mode credit?That will produce a result no different than what you now see. 73,If the expected credit does not appear in your DXCC Award Credit Matrix, yes ¨C though you should first contact the DXCC desk and see if they can determine how a DXCC credit previously granted has disappeared. Dave, AA6YQ [Non-text portions of this message have been removed] |
-----Original Message-----AA6YQ comments below From: dxlab@... [mailto:dxlab@...] Sent: Sunday, February 28, 2016 2:40 PM To: 'Dave AA6YQ' aa6yq@... [dxlab] Subject: RE: [dxlab] DXCC Verification Discrepancy resolution how-to? Thanks for the quick reply. I am in good shape now. Most of the ¡°V¡±erified were from my first DXCC card submission. I went through that submission way back when and manually marked them ¡°V¡±erified in logger. These particular credits are for entity only. I¡¯m not sure why that is but I¡¯ll follow up with DXCC desk and figure that out. What I ended up doing was using the ¡°E¡±ntity option on those contacts.Before the DXCC desk began using a computer to track award progress, if you submitted a QSL card seeking entity credit, the band and mode were not recorded. If the DXCC desk confirms that to be the case for your QSOs, then you'll want to resubmit those cards to get entity-band and entity-mode cred. I¡¯m not sure when that option, and the others were introduced, but I¡¯ve been sidelined for several years and just now getting things going again.Exactly right. 73,Welcome back, Ken! Dave, AA6YQ |
to navigate to use esc to dismiss