The new SOTA database has provided me with an incentive to correct any historic logging errors, and I found quite a big one. I activated G/SP-008 Boulsworth Hill on 31/08/2008, but my log was corrupt. I guess its been like this for almost 15 years, but by searching the database honour rolls either as a chaser or activator using the pull down option for a band you may never use, or a mode you would never use, (such as OTHER) you may also find you have made input error mistakes and you could consider correcting them yourself.
For instance, as an example try this in the new database with these filters set:
Activator Roll of Honour:
All G - All Years - All Bands - OTHER
40 UK activators have used mode OTHER.
Chaser Roll of Honour:
All G - All Years - All Bands - OTHER
104 UK chasers have used mode OTHER
It’s up to you whether you find and correct your logging errors. You cannot expect the MT or database manager to do it for you - they do more than enough work for our community on all our behalfs.
In my opinion self imposed Quality Assurance of your logs should be seen as important, so as to provide integrity of the SOTA database.
I will continue to search for errors in my logs to ensure they are as near to 100% accurate as they can be.
73 Phil G4OBK
PS Just tried this one with filters set to:
All Associations - All Years - VLF - All Modes
325 Chasers have made VLF contacts (Highest VLF points score 342)
149 Activators have made VLF contacts (Highest VLF points score 46)
LOL!!
