[Dx4win] What do you do for LoTW DXCC_QSLs... entries that have wrong or bogus dates?

[Rick Murphy]

These are probably pre-computerization QSLs. I have several DXCC records
that have no info other than a entity name since I've never submitted a
paper card or LoTW credit since computerization.
For example, this one:

*Worked Station*
*Worked*   002
*DXCC*   ABU AIL ISLANDS (DELETED) (2)
*Date*   1945-11-15
*Mode*   UNKNOWN
*Band*   UNKNOWN
There's no QSO details for LoTW to provide since there's no QSO details
recorded. I occasionally submit QSLs to fill in the details for these,
especially back when a submission allowed 100 QSLs.
73
    -Rick

On Mon, Feb 12, 2018 at 6:32 PM, Lee Hallin <hallinl at lanecc.edu> wrote:

> I have found that sometimes the entry in the DXCC_QSLs... file (that you
> download from LoTW to show DXCC confirmations) has the wrong date.  The
> date seems to be "guessed" by LoTW.  For instance, the confirmation QSO
> date for a QSO says 19890101 when in reality the date of the QSO was
> 19890304.  In this case, do you create a "dummy" QSO for 19890101 and,
> perhaps via "Notes for this QSO", point to the QSO in your log when you
> "really" worked them?
>
> Or do you just keep track of the QSOs in DXCCQSLs that are wrong and
> ignore them when they are shown as "unmatched" in your log?
>
> Other ideas?
>
> Thanks & 73,
> Lee  N7NU
>
> P.S.  Another date I have seen many times is 19451115; the date that DXCC
> started.
>
> ______________________________________________________________
> DX4WIN mailing list
> Home: http://mailman.qth.net/mailman/listinfo/dx4win
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:DX4WIN at mailman.qth.net
> Message delivered to k1mu.nospam at gmail.com
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
>



-- 
Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA