> I'm speechless! Entering double logs may be the worst
> workaround I've
> ever seen.
>From LOTW a day or two ago:
"
Not everyone makes certificates with the extra designators. Not every logging
program allows for recording of that data.
Since this is the case, you may strip the QSOs of that extra designator,
re-sign the QSOs and upload them again for possible QSLs. This way you will
have the QSO in LoTW with and without the extra designator. Depending on what
the other operator has submitted, you may get a QSL from one or the other QSO
that you upload. No QSO can be removed.
The confusion comes when people give out a specific callsign with the extra
designator, the recipient logs and uploads it that way, but the person who gave
out the callsign does NOT upload it the same way. Technically, a certificate
for that SPECIFIC callsign would be best but, due to various circumstances, the
recipient may upload the same QSO both with and without the extra designator
for possible QSLs.
A callsign is used for DXCC and WAS purposes. LoTW takes whatever information
is valid for those two purposes. Any additional data is for either future
awards or personal use.
If you want to upload QSOs for the special calls (N8Q and N4Q), please create
SIGNED requests and lock down the exact dates because those callsign will be
issued again."
>
> Let's hope they get that software "feature" fixed soon.
>
Methinks a "fix" is not planned, or required from LoTW perspective...
73,
Julius
n2wn
_______________________________________________
CQ-Contest mailing list
CQ-Contest@contesting.com
http://lists.contesting.com/mailman/listinfo/cq-contest
|