Running 1.17.1.0
Seems during QSL Mangement the LOTW Rcvd date is not remembered.
The EQSL Rcvd date is remembered.
Is this something that was overlooked or deliberate?
Mike W9MDB
LOTW QSL Mgmt
- G4POP
- Log4OM Alpha Team
- Posts: 10753
- Joined: 21 Jan 2013, 14:55
- Location: Burnham on Crouch, Essex UK
Re: LOTW QSL Mgmt
w9mdb wrote:Running 1.17.1.0
Seems during QSL Mangement the LOTW Rcvd date is not remembered.
The EQSL Rcvd date is remembered.
Is this something that was overlooked or deliberate?
Mike W9MDB
Hi Mike,
What part of QSL management for LOTW
Auto upload, auto download, manual upload, manual download, manual editing of single QSO or bulk editing etc etc?
73 Terry G4POP
Re: LOTW QSL Mgmt
I confirm that when you download a LOTW confirmation, the received date is not correct in the log.
In this example the LOTW QSL was received on 6/19/2014 but the log entry shows as 12/8/2011.
In this example the LOTW QSL was received on 6/19/2014 but the log entry shows as 12/8/2011.
- Attachments
-
- zf1a.PNG (57.5 KiB) Viewed 5679 times
K7PT-Chuck "#1 Top of the Honor Roll"
Re: LOTW QSL Mgmt
Sorry for not being specific enough.
I'm taking about the download. I always have to change the date for LOTW to get only the most recent (since my last download).
The ESQL download remembers the last one.
I'm taking about the download. I always have to change the date for LOTW to get only the most recent (since my last download).
The ESQL download remembers the last one.
Re: LOTW QSL Mgmt
As for K7RP's comment about received date I know the received date in the LOTW ADI file is the date that LOTW received it....not the date you download it.
I wrote my own LOTW utility so I'm familiar with the format. I can understand just wanting to see the important LOTW new entries which my utility does but it's up to your software to determine what's "new" relative to your software. All the programs are asynchronous with LOTW.
Are you thinking that the received date is or should be the date YOU received it in your software?
Mike W9MDB
I wrote my own LOTW utility so I'm familiar with the format. I can understand just wanting to see the important LOTW new entries which my utility does but it's up to your software to determine what's "new" relative to your software. All the programs are asynchronous with LOTW.
Are you thinking that the received date is or should be the date YOU received it in your software?
Mike W9MDB
Re: LOTW QSL Mgmt
No- the date is the date of the LOTW QSL match not when you downloaded it. It's the "QSL Date".
K7PT-Chuck "#1 Top of the Honor Roll"
Re: LOTW QSL Mgmt
I think my bug report got buried in the other comments.
Looking at this again the EQSL download has a "Download QSO from latest check" while the LOTW Download does not.
Is there some logical reason for that or could/should that same latest check be added to LOTW.
I'm always changing the date.
Mike W9MDB
Looking at this again the EQSL download has a "Download QSO from latest check" while the LOTW Download does not.
Is there some logical reason for that or could/should that same latest check be added to LOTW.
I'm always changing the date.
Mike W9MDB
Re: LOTW QSL Mgmt
Now at least I understand. The reason is that many users including myself do not download from LOTW on a regular basis and have no idea when the last was.
So, I'll go back a few months and download. The old ones are just fine and the new ones get updated in my log.
Even if my log gets completely messed up, I can go back too day one and get every QSL match updated.
And, if I have more then one computer for my logging (not connected), they could have different dates.
So, I'll go back a few months and download. The old ones are just fine and the new ones get updated in my log.
Even if my log gets completely messed up, I can go back too day one and get every QSL match updated.
And, if I have more then one computer for my logging (not connected), they could have different dates.
K7PT-Chuck "#1 Top of the Honor Roll"
Re: LOTW QSL Mgmt
Isn't that the whole idea of the software remembering?
I'm a bit pedantic and download every day (I run JT65 a lot and can keep my radio running while I work so I have QSO's every day).
Waiting for a longer download is just a few extra seconds I'd like to avoid.
And I'm all for consistency between the dialogs too.
Thanks
Mike W9MDB
I'm a bit pedantic and download every day (I run JT65 a lot and can keep my radio running while I work so I have QSO's every day).
Waiting for a longer download is just a few extra seconds I'd like to avoid.
And I'm all for consistency between the dialogs too.
Thanks
Mike W9MDB
- IW3HMH
- Site Admin
- Posts: 2925
- Joined: 21 Jan 2013, 14:20
- Location: Quarto d'Altino - Venezia (ITA)
- Contact:
Re: LOTW QSL Mgmt
This is the part of the code that manage this, it's pretty easy to understand:
So, LotwQslrdate on actualQso (the one in the database) is set equals to the qso.Qslrdate that arrives from Lotw.
There is not a LotwQslrdate in the ADIF downloaded from Lotw, they're using the Qslrdate field, and i'm setting the value on the QSO according to the information provided by Lotw ADIF file.
I can change this behaviour, but this is the information we receive.
Code: Select all
actualQso.LotwQslRcvd = "V";
actualQso.LotwQslrdate = qso.Qslrdate;
There is not a LotwQslrdate in the ADIF downloaded from Lotw, they're using the Qslrdate field, and i'm setting the value on the QSO according to the information provided by Lotw ADIF file.
I can change this behaviour, but this is the information we receive.
Daniele Pistollato - IW3HMH