Ladies and Gentlemen,
I am thinking of disabling the confirmation marker as it is no longer serving its purpose.
We have an expanding group of chasers who are changing their chaser logs to match what an activator has logged rather than what was in the QSO. This often occurs when an activator uses a special event or club callsign but enters their own callsign as the callsign used in the activator log.
- The chaser hears XX1XX and logs that call.
- The activator uses XX1XX on air but logs their own callsign YY1YY as the callsign sent.
- The chaser does not get a confirmation mark and checks the activator log.
- The chaser sees a different call logged and changes their log from XX1XX to YY1YY.
- The chaser gets a confirmation mark and is happy.
- The database manager finds the database contains imaginary QSOs and is sad.
Well, it’s simple. Next time I find someone changing their chase log to match an incorrect activation log is the time I turn off confirmation for everyone. It’s easy to check. I have every transaction log from January 2013, every edit, every amendment, every peek into an activator’s log followed by an edit to the chaser’s log.
If you misuse the facility to get a “better” looking log then there is no point in offering the facility. In fact it’s almost Kafkaesque in that the lack of a confirmation marker in these cases means the chaser was correct, so they change to incorrect data to get a marker which confirms they have entered the same nonsense data as the activator.
For the record, the MT do not use the confirmation mark in checking awards.