Forum Replies Created
-
AuthorPosts
-
August 17, 2025 at 11:08 in reply to: UPLOADED WITH WRONG “OPERATOR” FIELDS! Correction needed #16519
Andrew M0YMA
KeymasterPeople keep asking “Why can’t I upload my own logs?”
But yet again, we have a log submitted by an activator, that is supposedly checked by a National log manager… with an incorrect operator callsign for the whole log?
So:
Activator didn’t check their log
Log-manager didn’t check the log
IT Team have to spend time fixing the log…Deep breath, Andrew…
—
I have fixed the log
… back to retirement.Andrew M0YMA
KeymasterOK… I’ve found the error…
I’ve raised this for the dev-team to fix
Andrew M0YMA
KeymasterCurious… SE5B–>SM5CBN is one of the only (non-UK) mappings we catch during upload, so this should be handled!
I’ve fixed the relevant hunter entries, but will look as to why this hasn’t been done automatically…
Andrew M0YMA
KeymasterHi Linda
Reply sent directly
Andrew
Andrew M0YMA
KeymasterAn activator, using a club call or a special event call, should get personal credit…
That is why the correct completion of the OPERATOR field (operator’s home call) is important!
This is by design.
Andrew M0YMA
KeymasterHi Peter
To the best of my understanding, Logsearch is fully compatible with all modes in ADIF 3.1.3
The additional digital sub-modes in 3.1.4 and later are not fully supported… they’re on the ToDo list…
Note: Logsearch aggregates all digi modes as DATA for awards purposes
HTH
AndrewAndrew M0YMA
KeymasterThe use of suffixes is governed by your licence – in many countries, the use of use of such suffixes is optional.
However, IMHO, it is good practice to sign /P or /M where appropriate, as this (a) highlights you may be using limited equipment (b) highlights you are giving away some references
Andrew M0YMA
KeymasterAfter investigations…
Your interactive search shows the bigger number, as it includes BOTH calls
Top Operators matches on the HunterHomeCall – which is obviously different for the two calls.
I’ve updated your Hunts and this should now show the correct number… at least, after tonight’s run!
I’ve also added the mapping of SE5B->SM5CBN during upload, so future Hunts should be correctly allocated
-
This reply was modified 10 months, 3 weeks ago by
Andrew M0YMA.
Andrew M0YMA
KeymasterAh… Ummm… Ooops…
A change I made in August 2023 will have broken VEFF for anyone trying to claim less than 100 references ๐ฎ
I’ll try ad fix that!
Sorry…
Andrew M0YMA
KeymasterHi Stuart
I will have a look when I have a moment…
A
Andrew M0YMA
KeymasterRegarding deleted areas… there are three reasons why a reference is deleted:
1. It shouldn’t have been a reference in the first place
2. It has been replaced by another reference
3. It was a valid reference, but has ceased to be validQSOs in (1) should be invalid
QSOs in (2) should be moved to the replacement reference
QSOs in (3) are a problem, I agree.Andrew M0YMA
KeymasterIf you have included your “home call” as the Operator when activating using your special call, they should all show as SM5CBN in Top Operators
I’ll have a look at your data when I have a moment…
Andrew M0YMA
KeymasterHi Grant
The P2P score reflects unique reference combinations… so two confirmed contacts between the same references only counts as one point.
eg:
you in VKFF-1660 and VKFF-0063 (two contacts, one point)
you in VKFF-1663 and VKFF-0139 (two contacts, one point)
etcAndrew M0YMA
KeymasterNo… this has not been actioned
Issue #97 applies
https://gitlab.com/WWFF/wwff-logsearch/-/issues/97Andrew M0YMA
KeymasterNote: there is no need to list /P variations as associated call-signs…
If a STATION_CALLSIGN is callsign/P the OPERATOR is automatically populated as callsign
—
The requested change is noted, and will be actioned by the Team in due course. -
This reply was modified 10 months, 3 weeks ago by
-
AuthorPosts