Hi All,
I have seen that in V2 there is no LOTW qsl status "Validated" and that during the Adif import from V1 all QSO's with LOTW QSL status "Validated" are changed to QSL status "Yes".
This has major consequences for the upload to Clublog because after a complete upload, only QSOs with "Confirmed" and "Worked" are shown there. All QSO's that had the status "Validated" in V1 are now displayed as "Confirmed" in Clublog.
Clublog normally displays the status "Validated" as "Verified".
The same QSO with FT5ZM in V2
73 Dick DL1CLM
LOTW qsl status "Validated" not available in V2
LOTW qsl status "Validated" not available in V2
Win10 64b v21H2 Log4OM v2.21.1.0
IC 7300 / IC 756 Pro II via Omnirig v1.19
Optibeam OB 9-5
IC 7300 / IC 756 Pro II via Omnirig v1.19
Optibeam OB 9-5
Re: LOTW qsl status "Validated" not available in V2
Some additional info:
that's what it looks like on the DXCC charts in club logs.
After the upload from V2 all blue "V" were changed to green "C".
I hope this can be resolved very soon.
73 DIck DL1CLM
that's what it looks like on the DXCC charts in club logs.
After the upload from V2 all blue "V" were changed to green "C".
I hope this can be resolved very soon.
73 DIck DL1CLM
Win10 64b v21H2 Log4OM v2.21.1.0
IC 7300 / IC 756 Pro II via Omnirig v1.19
Optibeam OB 9-5
IC 7300 / IC 756 Pro II via Omnirig v1.19
Optibeam OB 9-5
- IW3HMH
- Site Admin
- Posts: 2988
- Joined: 21 Jan 2013, 14:20
- Location: Quarto d'Altino - Venezia (ITA)
- Contact:
Re: LOTW qsl status "Validated" not available in V2
Hi Dick
Log4OM works with ADIF 3.10 specifications. Those specifications removes the "VALIDATED" concept from the QSL confirmation.
According to that, Log4OM will IMPORT validated value for QSL and save it as "CONFIRMED" as per specifications.
Choice was made probably because they finally understood that a qsl card received can be used to "validate" a big number of awards, not only the ARRL DXCC.
QSL management is intended to manage the status of the requested/sent confirmation.
Status of a reference gained with the QSL is mantained in the references environment of Log4OM, that is integrated but different from confirmation environment.
Based on your screen it seems Clublog is still (as many other does) working with "validated" concept in the QSL received status.
I will check what i can do, eventually, to produce an "old" format for clublog needs mixing up dxcc confirmation status with the qsl received status.
Log4OM works with ADIF 3.10 specifications. Those specifications removes the "VALIDATED" concept from the QSL confirmation.
According to that, Log4OM will IMPORT validated value for QSL and save it as "CONFIRMED" as per specifications.
Choice was made probably because they finally understood that a qsl card received can be used to "validate" a big number of awards, not only the ARRL DXCC.
QSL management is intended to manage the status of the requested/sent confirmation.
Status of a reference gained with the QSL is mantained in the references environment of Log4OM, that is integrated but different from confirmation environment.
Based on your screen it seems Clublog is still (as many other does) working with "validated" concept in the QSL received status.
I will check what i can do, eventually, to produce an "old" format for clublog needs mixing up dxcc confirmation status with the qsl received status.
Daniele Pistollato - IW3HMH
Re: LOTW qsl status "Validated" not available in V2
Hi Daniele,
Thanks for your quick response.
It might be a solution to first run an SQL query in QSO Manager before sending an adif file to clublog.
This query can then change value from <LOTW_QSL_RCVD:1>Y to <LOTW_QSL_RCVD:1>V .
Every LOTW confirmation received has the status Verified (Validated), so changing all Y to a V solves the problem.
or is that a bad solution (work around)?
Dick DL1CLM
Thanks for your quick response.
It might be a solution to first run an SQL query in QSO Manager before sending an adif file to clublog.
This query can then change value from <LOTW_QSL_RCVD:1>Y to <LOTW_QSL_RCVD:1>V .
Every LOTW confirmation received has the status Verified (Validated), so changing all Y to a V solves the problem.
or is that a bad solution (work around)?
Dick DL1CLM
Win10 64b v21H2 Log4OM v2.21.1.0
IC 7300 / IC 756 Pro II via Omnirig v1.19
Optibeam OB 9-5
IC 7300 / IC 756 Pro II via Omnirig v1.19
Optibeam OB 9-5