[WriteLog] Writelog for general logging?

[w1mo]

I convert my log to .adi format. During the signing process, I am given 
the opportunity of selecting a specific date range, rather than sending 
the entire log file.  It's no trouble, really.

73, Norm W1MO

On 2/4/2013 20:54 PM, Andre VanWyk wrote:
> Joe,
>
> I thought LOTW had the capability of simply rejecting a record that matches 100% of what was loaded before. One would think this should not be a major problem for such a complex server?
>
> 73
> NJ0F
>
> Sent from my iPhone
>
> On Feb 4, 2013, at 7:49 PM, "Joe Subich, W4TV" <lists at subich.com> wrote:
>
>>> It loads up to LOTW just fine via Email too.
>> There is one major problem in using Writelog's general tracking mode
>> for everyday operation and then uploading to LotW directly.  WriteLog
>> is not alone in the problem - there are half a dozen other contest
>> programs with the same problem so I'm not picking on WriteLog.
>>
>> A LotW upload from WriteLog uploads *all* QSOs in that log - even
>> those that have been uploaded previously.  Thus, if one uploads to
>> LotW from the General DXCC tracking log every week or every month,
>> one is soon uploading nearly all duplicate QSOs.  Those duplicate
>> QSOs (not just from WriteLog) currently represent between 60 and
>> 75% of all uploads to Logbook of the World and were a significant
>> contributor to the recent backlog at LotW.
>>
>> If you are going to use a contest logging program for every day
>> operation, please export your log to ADIF and use something like
>> ADIF Master to trim that file to only those QSOs made since your
>> last upload *before* signing the log with tQSL and uploading.
>> Please do not simply upload the General DXCC Tracking log with
>> WriteLog's built-in upload and e-mail capability.  The WriteLog LotW
>> support is fine for a specific contest (e.g. CQWW CW, etc.) where a
>> log is uploaded *one time* after the contest is over.  However, the
>> General DXCC tracking "contest" is never over - unless you start a
>> new log each week/month and only upload at the end of that period.
>>
>> The alternative to using something like ADIF Master is to use one of
>> the "everyday" logging programs - DXLab Suite (DXKeeper), DX4Win,
>> Logger32, etc. - to import the ADIF and generate the upload since
>> they keep track of the QSOs uploaded to LotW and only upload QSOs
>> that are new since the last upload.
>>
>> 73,
>>
>>    ... Joe, W4TV
>>
>>
>> On 2/4/2013 6:26 PM, Andre VanWyk wrote:
>>> I have been using the DXpedition mode for general logging for many
>>> years. I think the latest version has a general logging module if my
>>> memory serves me right, but will have to check.
>>>
>>> It loads up to LOTW just fine via Email too.
>>>
>>> 73
>>> NJ0F
>>>
>>> --------------------------------------------------
>>> From: <ke6qr at comcast.net>
>>> Sent: Monday, February 04, 2013 4:59 PM
>>> To: <writelog at contesting.com>
>>> Subject: [WriteLog] Writelog for general logging?
>>>
>>>> Is it possible to use writelog for general day to day casual contacts?
>>>> What would be the best module to use? Thanks! Ke6qr
>>>> _______________________________________________
>>>> WriteLog mailing list
>>>> WriteLog at contesting.com
>>>> http://lists.contesting.com/mailman/listinfo/writelog
>>>> WriteLog on the web:  http://www.writelog.com/
>>> _______________________________________________
>>> WriteLog mailing list
>>> WriteLog at contesting.com
>>> http://lists.contesting.com/mailman/listinfo/writelog
>>> WriteLog on the web:  http://www.writelog.com/
>> _______________________________________________
>> WriteLog mailing list
>> WriteLog at contesting.com
>> http://lists.contesting.com/mailman/listinfo/writelog
>> WriteLog on the web:  http://www.writelog.com/
> _______________________________________________
> WriteLog mailing list
> WriteLog at 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.2897 / Virus Database: 2639/6080 - Release Date: 02/04/13
>
>