On 22/01/2025 4:46 pm, Dave AA6YQ via
groups.io wrote:
Thanks, Laurie.
You're saying that if the user has "QRZ XML lookup" enabled in
JTAlert and logs a QSO with PJ4JA, that because of the incorrect
DXCC entity information in QRZ, JTAlert will direct DXKeeper to
log the QSO with an incorrect DXCC entity; correct?
Correct.
To be fair, JTAlert is not knowingly logging an incorrect Dxcc
entity. It is logging what it has been told by QRZ. JTAlert has no
knowledge as to the correctness of the data QRZ has provided.
Examining the bio & mod dates of the listing could be used as
a potential risk calculation (if I chose to implement such) but in
the case of PJ4JA that would not help as both dates are less than
a month old.
<biodate>2024-12-30
22:49:21</biodate>
<moddate>2024-12-22 01:33:41</moddate>
de Laurie VK3AMA
