SpotSpy

In my opinion his feature doesn't make sense for RDA - and IOTA - tracking where it is quite normal that the same station is working in the same mode on the same band from different RDA's or IOTA's, sometimes within hours or even minutes. It would be very beneficial, however, if the same RDA and / or IOTA by the same station at the same band and / or mode would not generate an alert if it has been worked before. However: Sometimes it will happen that you are unsure if the station has logged you properly. Therefore I suggest to use the QSL_RCVD information together with IOTA and / or RDA number for the decision (R and Y for no alert, all others for generate an alert).

Juergen, DL8LE

QSL_RCVD can take years so that is no option in my (humble) opinion.
If you are not sure about a qso you can always add a call 'needed callsign-band-mode'.

So the optimum option is: callsign-band-mode-RDA-or-IOTA not worked before.
Also a good option is to make it flexible: callsign-band-mode as default, and/or RDA and/or IOTA as option (tickbox).

My 2 cents. (About 70% of the spots in Spotspy are already worked callsign-band-mode in my case.)

Aart

DXKeeper has the option to select either R for requested, Y confirmed, S submitted, V verified, I Invalid, X Expired. If you are not sure for some reason if the station has got your call confirmed you may just select I and it will not show up in DXView as well. In my personal opinion this is the easiest way to mark a QSO as a QSO in question. This means I have to change my proposal to generate no alert for QSL_RCVD like Y, R, S and V (I am sorry that I didn't look up DXKeeper when I worte the comment).

During many of the latest DXpeditions their transmitting frequency was intentionally jammed making it often very hard to determine if it was really the own call the station responded too. If so I used that procedure until I got some confirmation by an online log. Then I either changed QSL_RCVD from I to R or did nothing depending on the online log.

The question is how the "worked" or "not worked before" is defined. As far as I am aware of DXKeeper considers I and X in QSL_RCVD as "not worked before".

73

Juergen, DL8LE

If QSL_RCVD = R is also defined as station worked in Spotspy-spots, I agree with your proposal.
But
That must be extended with the accepted electronic QSL also (LOTW). I do not always ask for qsl-card if I know for sure the qso will be confirmed via LOTW. So the expression has to be:
If (QSL_RCVD = Y or R or S or V) or (LotW_QSL_sent = R or U or Y)

See http://www.dxlabsuite.com/dxkeeper/Help/Items.htm

73, Aart PA3C

Agree, Art, the electronic QSL has to be included, i.e. either the QSL_RCVD info for LotW or eQSL or both.

Question is if eQSL should be selectable by the user or not. I am unsure about the best way because this will depend if the award checkpoints will accept eQSL in the future as it has already happened with CQ for the WAZ award.

73

Juergen, DL8LE

Any progress on this one?
With IOTA warnings I'm on 99% dupes (worked, but qsl not received yet).

Aart