how works the database’s “first activator” algorithm?
For example on our ukrainien expedition UT/CA-376 was the first activated UT summit. HA5CQZ Zoli made the very first QSO at 14:34 UTC there, but he is not the first activator.
Only one contact is needed to activate a summit (rule 3.7.8). The 4 contact rule only applies to claiming points.
Either way, Zoli made the first contact and was also the first to qualify the summit, so there is an issue with the database.
Another issue is the fact that the database does not order activations in the order that they are carried out. To overcome this, I keep a separate spreadsheet to record the order the summits have been activated and the points gained.
Either way, Zoli made the first contact and was also the first to
qualify the summit, so there is an issue with the database.
Oh yes, definitely. Caroline and I noticed and reported this ages
ago.
Yes I too take issue with the way the database looks for this information. Helen and I had the same problem. Our plan was for me to activate a ‘First Time Unique’ by qualifying first and then the next time Helen would make hers the first, but because GW7AAU comes before GW7AAV (actually we were using GM) her call is shown as the first activator on all our FTUs. I have plans for some more FTUs in August and I think that my daughter Caroline’s call 2W0YLO (as 2M0YLO/P) will show up as the first each time.
Its not just with first activations last year I activated G/SP-016 Raw Head on the last day that it was valid (31 Aug 2009) - so being the “last activator”. The hill was acticated the day before this but because that activation was not inputted until after I had recorded my dataon the database it showed as the last activation.
As the data for hill that are removed only stays on the database for a few weeks after its removed I didn’t mention it at the time but it does seem that the algorithm is not looking for earliest time for first activation and latest for last activation.