[Logic] Identifying LoTW Contacts in LOGic ???
R Johnson
[email protected]
2003年9月05日 14:22:59 -0400
Hi:
With LoTW due to come on-line Real Time Sept. 15th., (only 10 days away guys),
it brought to mind the question of how to identify the QSO's in LOGic.
I know that this question was brought up last May or June, but I don't
know that there was any determination of the "Best Way" to handle the
QSO's submitted to LoTW, or eQSL for that matter.
We now have 3 methods of QSL'ing to contend with.
1-Paper Cards, same old method we've using for eons. No problem !!!
2-LoTW Contacts, no paper, good for ARRL Awards only (at this time) !!!
3-eQSL Contacts, sort of paper, but no good for ARRL Awards !!!
I don't know about other Awards like CQ, RAC, NCJ etc.
So when it comes time to check or submit proof for an award is really
where we get into a quagmire. Problems like: "Gee, I've 35 states in "REAL"
paper and 50 states in LoTW. If I check the status of WAS with Award Progress
Tracking in LOGic right now I'm only going to only get 35 states.
So the way I see it, the minimum changes to LOGic are:
1-Add a method of flagging a match for LoTW and eQSL contacts in LOGic.
2-The "Award Progress Tracking" report generator needs to reflect the method
of confirmation (XXX in paper, YYY in LoTW, and ZZZ in eQSL).
I see no need of having separate S,R,& F designations for LoTW & eQSL. I'm
willing to accept the fact that having submitted the SAME ADIF file of my entire
log to BOTH LoTW and eQSL that a "Submitted Flag" is unnecessary. The same goes
for a "Received Flag". So we're left with just a "Fulfilled Flag" to indicate a
match on that QSO. This should make programming a little easier.
My next thought (or nightmare) is having to enter each match manually. I can see
a real need for LoTW to export a list of "Matching Contacts" and LOGic being able
to read it and update the log status.
I seem to have more questions than answers.
Your thoughts Guys and Gals.
73
Bob, K1VU