May 25, 2017 at 01:02 #5190
I have received two logs from K0ATZ at NPOTA RV05 that appear to have been uploaded under reference number KFF-3674 before KFF-4009 was assigned. I can’t verify or correct this so I’m kicking it upstairs. Log file names are:
When I tried to upload the system says they are already there.
NU0CMay 31, 2017 at 17:08 #5247w3aaxParticipant
I thought Andrew already moved logs when we were fixing parks, but I will wait to see what he says.June 3, 2017 at 21:48 #5269w3aaxParticipant
Has this been dealt with yet?June 10, 2017 at 13:51 #5335
I don’t see a sense of urgency here. Perhaps I will just upload under different file names and let the chips fall where they may.June 26, 2017 at 13:33 #5517
Please humour me a moment…
There are ten logs uploaded by you for KFF-3674 and another for KFF-4009 (all since 10th May 2017)
The two files you listed are from KFF-0378
AJune 27, 2017 at 03:32 #5537
Thank you for taking time to look at this Andrew,
As I understand the situation NPOTA RV05 was assigned as KFF-4009 only recently. K0ATZ sent me the above NPOTA log files for RV05 when he noticed that it had been assigned a KFF number (May 22) but when I tried to upload them the system informed me that logs with those names had already been uploaded.
The thinking was that perhaps these got uploaded earlier with a batch of NPOTA logs and assigned to another reference for whatever reason. K0ATZ has related that he believes he has way too many QSOs listed at KFF-3674 and of course none at KFF-4009.
Either someone coincidentally uploaded two unrelated logs with the same file names or there are some Qs somewhere on the wrong reference. I do not have the access level to figure out which is the case, I can only report. 🙂
NU0CJuly 6, 2017 at 01:33 #5628
Hello, Andrew. Please provide an update for this issue.
Jeff – KB3ZUKJuly 17, 2017 at 18:58 #5722
Hello, Andrew. I am again, requesting that you please either resolve or provide an update as to your efforts towards resolving this issue thus far. K0ATZ is one of our most active participants in KFF. This issue was posted at the end of May. Thank you for looking into this. Please me know if you require any additional information, resources, etc., to address the issue.
Very 73 es 44 de Jeff / KB3ZUKJuly 18, 2017 at 11:01 #5743
There is a reason why we request that log files are named in the format CALLSIGN REFERENCE DATE (ie K0ATZ KFF-4009 2017-05-11 or whatever) as this provides an unambiguous convention…
I can change references in the database, but I need to know which logs are incorrectly loaded…July 19, 2017 at 00:58 #5753
Perhaps I am not asking the right questions. Let’s try this a different way.
Please check the database for QSOs made by activator K0ATZ on Sept. 30 2016 between the times of 15:20z and 16:57z (90 QSOs).
And also Dec. 31 2016 between the times of 01:19z and 17:03z (202 QSOs).
If these QSOs exist in the database and are listed as activation of any reference other than KFF-4009 then there is an error.
Complete logs can be provided on request.
Jim, NU0CAugust 1, 2017 at 20:08 #5844
Hello, Andrew. I am again, in addition to the email requests, and requests here on the forum, requesting that you please either resolve or provide an update as to your efforts towards resolving this issue thus far. K0ATZ is one of our most active participants in KFF. This issue was posted at the end of May. Thank you for looking into this.
It would appear as though every request for added information that you asked for has been addressed most rapidly and then no further action seemingly takes place in response.
Please me know if you require any additional information, resources, etc., to address the issue.
Very 73 es 44 de Jeff / KB3ZUKAugust 3, 2017 at 11:30 #5894
2016-09-30 KFF-3674 is now KFF-4009 (90 QSOs)
2016-12-31 KFF-3674 is now KFF-4009 (202 QSOs)
- The topic ‘K0ATZ NPOTA RV05 KFF-4009’ is closed to new replies.