[Dx4win] LoTW Upload - Filenames

[R.T.Liddy]

I used to use a file-naming convention similar to yours, Ed. I'd use 
"L" for LOTW and the upload date such as "MMDDYY". For today
it would be L121012.
 
It's a pretty common way of doing it and I'm sure a lot of folks probably
used a similar system. But, then I read that one of the bugs at the
ARRL LOTW computer was that if a Log Submission came in with the
same name as an earlier one that hadn't been processed yet, the new
one would replace the earlier one in queue. So, if my L120112 came in
before John Doe's L120112 file, mine would be deleted from being entered
into LOTW and I wouldn't know it unless I was closely tracking everything.
I might never know if a lot of Q's were missing.
 
Now, I use a file-naming convention that would be highly unlikely used by
anyone else. It's possible, but highly unlikely.
 
The ARRL has fixed this bug and all files are now supposedly loaded into LOTW
whether they have duplicate names or not. But, I have to wonder about ones
I loaded in the past. Did any get deleted due to being duplicated by name
with someone else's newer ones? I still have all my .TQ8 files and I could
just re-upload them to LOTW. But, that would just add to the massive delays
that the LOTW system has been experiencing. So, I won't do it now.
 
I routinely compare all my credits for DXCC with what I have in DX4WIN to make
sure they match. But, it gets very tedious for other Awards and impossibly
tedious for WPX.
 
Maybe I'll just do a spot-check to see if any problems show up. Makes you
wonder how long the duplicate filename problem existed before anyone finally
realized it and the LOTW Software Gurus corrected it.
 
GL/73/MX&HNY,      Bob K8BL
 

From: Ed Hughes <kg4w at comcast.net>
Subject: Re: [Dx4win] LoTW Upload
To: dx4win at mailman.qth.net
Date: Monday, December 10, 2012, 11:02 AM



The following works for me in determining the interval LOTW takes to process 
my uploads.
I name my uploads based on the date ie LOTW12102012. Then I note the 
calender for
that date & then I just wait for a later date to show under "find call" in 
LOTW, this gives me
the interval for that upload.

Ed KG4W

----- Original Message ----- 
From: "Dan Violette" <danki6x at socal.rr.com>
To: <dx4win at mailman.qth.net>
Sent: Sunday, December 09, 2012 6:22 PM
Subject: Re: [Dx4win] LoTW Upload


> It shows an upload date which corresponds to when it is processed not 
> first
> uploaded despite the wording.  I verified this with my last upload actual
> date/time versus when new QSL matches hit..  Dan KI6X
>
> -----Original Message-----
> From: dx4win-bounces at mailman.qth.net 
> [mailto:dx4win-bounces at mailman.qth.net]
> On Behalf Of Jesse Wall
> Sent: Sunday, December 09, 2012 4:57 AM
> To: dx4win at mailman.qth.net
> Subject: [Dx4win] LoTW Upload
>
>
> Hugh,
> After you do an upload, go to Find Call and search your call? This option
> says it is the callsign's last upload. I haven't tested this myself. I'm
> waiting until the backlog clears before I do an upload again.
>
> 73 and Merry Christmas to all,
> Jesse, KA8YYZ
> --- dx4win-request at mailman.qth.net wrote:
>
> From: dx4win-request at mailman.qth.net
> To: dx4win at mailman.qth.net
> Subject: DX4WIN Digest, Vol 104, Issue 11
> Date: Sat, 08 Dec 2012 12:00:02 -0500
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sat, 8 Dec 2012 10:25:58 +0100
> From: "ON4AOI" <on4aoi at skynet.be>
> To: "'Hugh Phillips K7XM'" <jacshitt at mho.com>
> Cc: DX4WIN at mailman.qth.net
> Subject: Re: [Dx4win] LoTW file upload
> Message-ID: <002401cdd526$084d4e50$18e7eaf0$@be>
> Content-Type: text/plain; charset="us-ascii"
>
> Hugh
> It only shows up when you have uploaded those files.
> No trace afterwards, if b4 28/11/2012 you probably need to upload Again 
> due
> the BUG they fixed late evening on 28 November
>
>
> Guy ON4AOI
>
> -----Oorspronkelijk bericht-----
> Van: dx4win-bounces at mailman.qth.net 
> [mailto:dx4win-bounces at mailman.qth.net]
> Namens Hugh Phillips K7XM
> Verzonden: zaterdag 8 december 2012 1:56
> Aan: DX4WIN at mailman.qth.net
> Onderwerp: [Dx4win] LoTW file upload
>
> I have uploaded two TQ8 files to LoTW recently.
> Shouldn't those show up somewhere even though they have not been processed
> by LoTW ?
> I can't seem to find them, unless I'm not looking in the right place....
> Using Dx4Win v8.05...
>
> 73
> Hugh
> K7XM
>
>
> ------------------------------
>
> Message: 2
> Date: Sat, 08 Dec 2012 11:44:57 -0500
> From: "David Kozinn, K2DBK" <k2dbk at arrl.net>
> To: Jim Reisert AD1C <jjreisert at alum.mit.edu>
> Cc: DX4WIN Reflector <dx4win at mailman.qth.net>
> Subject: Re: [Dx4win] How to find what new countries I worked
> Message-ID: <50C36E89.7040505 at arrl.net>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Well for me, the clublog feature was exactly what I wanted in this case, 
> but
> I can see where there might be other variations as well. None of the
> examples that I can think of (including the one I started this thread
> with) are "must have" things, but rather fall into the category of
> "interesting things you can find out".
>
> On 12/7/2012 8:08 PM, Jim Reisert AD1C wrote:
>> On Tue, Dec 4, 2012 at 8:10 PM, David Kozinn, K2DBK <k2dbk at arrl.net>
> wrote:
>>
>>> Actually, that is  the perfect solution, and one I'd forgotten about.
>>> (I've been a member of Club Log for a long, long time.) That actually
>>> gives me the exact information that I was looking for. Thanks for
> mentioning it.
>> This works for all-time new ones, but not, for example, if I want to
>> see if I worked any new countries during CQWW CW for the CQ DX
>> Marathon in 2012. A while back, I wrote a quick-and-dirty program to
>> display the first time a new country was worked, given an ADIF file as
>> input.  It was never meant for release, but I could add filtering to
>> it.  That way you could export whatever portion of your log you cared
>> about (to ADIF) and run the report against that.
>>
>> But it would be better if Paul could build this into the program.  If
>> I recall, KD7P/N7XR's logging program (whose name escapes me at the
>> moment) was able to do this, back in the mid-1990's!
>>
>> - Jim
>>
>> --
>> Jim Reisert AD1C, <jjreisert at alum.mit.edu>, http://www.ad1c.us
>>
>
> --
> 73,
> David, K2DBK