Mike,
You are correct - adding "LotW_QSL_Sent" and the date (LotW_QSLSDATE) is
consistent with the the workflow envisioned in the Amateur Data
Interchange Format (ADIF) and many loggers that provide award tracking
operate that way. However, such capabilities are not really necessary
for a *contest* logger where adding extra fields to each log entry
carry a performance penalty (or at least processing overhead).
It's certainly not my place to tell Wayne how to design his product -
but the ability to prevent one from blindly exporting the same 5,000
QSOs to LotW every week or month (50 non-contest QSOs/week x 2 years)
probably justifies a "last upload" date.
73,
... Joe, W4TV
On 2/28/2013 8:50 AM, Mike Armstrong wrote:
Joe, it could be something as simple as the addition of a new field in the log file itself....
"LOTW qsl sent." With that flagged, it would only send those whose flag isn't
"Y." Stupidly simple idea, but I don't know how much trouble it would be to implement
it. I know a couple of other logging programs do that..... But having very limited experience with
writelog to this point, I don't know if it is already there and I just don't know it...... I leave
that for you guys with more product time to tell us :) :)
Mike AB7ZU
Kuhi no ka lima, hele no ka maka
On Feb 27, 2013, at 19:28, "Joe Subich, W4TV" <lists@subich.com> wrote:
I agree this is a cumbersome process and would hope a fix could be
provided so WL can export the date ranges itself rather than have to
produce the entire adif and then hone it down further outside of WL.
It could be something as simple as storing the date/time of the last
exported QSO in each log and then not exporting anything prior to
that unless the user confirmed an "override": "You have already
signed the QSOs before YYYY-MM-DD HH:MM for LotW. Are you sure?"
(for "General DXCC Tracking Log") or "You have already signed this
log. Are you sure?" (for a specific contest log).
73,
... Joe, W4TV
On 2/27/2013 9:14 PM, Gary AL9A wrote:
Frank,
Yes, I've seen that work around mentioned on the reflectors before. It
will work, provided the pilot is as conscientious as you and makes note
of the start and end dates to be uploaded each time. I agree this is a
cumbersome process and would hope a fix could be provided so WL can
export the date ranges itself rather than have to produce the entire
adif and then hone it down further outside of WL. Many opportunities
for something to go wrong or for inexperienced/lazy pilots to just
upload the whole shooting match each time!
73,
Gary AL9A
----- Original Message ----- From: "Frank Fallon" <n2ff@optonline.net>
To: <writelog@contesting.com>
Sent: February 27, 2013 3:12 PM
Subject: Re: [WriteLog] Writelog for general logging?
Good point, Gary.
But there is another alternative which avoids downloading another
logging program. It's a little bit more cumbersome, but I solve the
problem by having Writelog export my general DX log as an ADIF file to
a folder I named "LOTW" and then I call up TQSL and ask it to sign the
entire file. At a point in the process I then have the ability to
specify start and end dates. Using that feature enables me to send a
much smaller file. Yes, it takes more time but avoids using another
logging program. Yes, It certain would be great if the date range
features was directly available in Writelog. (hint hint nudge nudge).
Frank...N2FF....
On 2/5/2013 5:02 AM, Gary AL9A wrote:
There is a problem with using the both the DXpedition mode and
General DXCC tracking log keeper and exporting to LOTW from these
modules. Whenever you do a File/Export/Trusted QSL file... you are
exporting the ENTIRE log to LOTW, not just the latest QSOs. Unlike a
true general logger, WriteLog's various modules lack the ability to
select just some QSOs in the log by specifying a range of dates to be
included in the upload. This is not a problem for uploading a
contest log as you do want to upload the entire record. But...
If your log is small this is not a big problem. However, if your log
contains thousands of QSOs you are needlessly uploading thousands of
duplicate transactions to LOTW with each update. This is an enormous
waste of LOTW computer resources and needlessly causes delays for the
entire LOTW community. A far better approach would be to find a good
general purpose logger, either a freebee from the internet, or a low
cost product that offers the features necessary to control which of
your log records are going to be uploaded to LOTW. The DXLabs suite
at http://www.dxlabsuite.com/ comes to mind as it is a powerful
package that is free for the asking.
If you have need of a general logger and want to use one of the
WriteLog modules fine. Just be a considerate amateur and don't
utilize the LOTW upload directly from these modules. Instead find
another way to create a tq8 file that contains only the few new QSOs
that you need to upload.
73,
Gary AL9A
-
_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web: http://www.writelog.com/
-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2013.0.2899 / Virus Database: 2641/6136 - Release Date: 02/27/13
_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web: http://www.writelog.com/
_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web: http://www.writelog.com/
_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web: http://www.writelog.com/
|