Forum Replies Created
-
Posts
-
Ummm…
It should say “Apply for …” if you can apply – and it doesn’t appear to work if “All Time” selected.
Try selecting “2017” for the year and see if that works…
In the meanwhile, I’ll try and work out why it isn’t working for All-Time… the intent is that you can Apply for the latest year by default.
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…
As of Monday’s update this has now been fixed 🙂
Hello Augusto
A recent update to LogUpload introduces a two-pass checking process…
Previously, each QSO was processed individually, and if there was a problem, it (and only it) was not uploaded. This created a lot of work for coordinators, as they had to find which QSO was missing and correct it (in a separate log) – or as was quite common, just ignore the QSO so the Hunter did not get credit.
With the two-pass upload, major errors are trapped first, allowing the coordinator to correct the log before submission… this means that the whole activation gets uploaded as a single log – it also means less work for the coordinators (and more importantly, IMHO, less work for me, when I get asked to do correction!)
Hi Paul
In and around your area are a long list of references… look for any with the name starting:
- Teesmouth & Cleveland Coast SPA
- Northumbrian Coast SPA
Plus you have
- GFF-0013 – Northumberland National Park
- GFF-0267 – Northumberland Coast AONB
Amongst others…
AAs per the instructions on the Upload Screen (for those with the privileges):
Errors can be corrected…
… please DO NOT upload a duplicate log then ask me to delete the first one!If you upload a second log, it is a separate log and does NOT over-write the first one – so everything is duplicated!
