-
|
I was playing with the DUPES button in the Advanced Logbook, I was able to find a lot of dupes, but some of them were not returned, I manually changed the query to: SELECT GROUP_CONCAT(col_primary_key SEPARATOR ',') AS qsoids,
COL_CALL,
MIN(col_time_on) AS Mintime,
MAX(col_time_on) AS Maxtime
FROM TABLE_HRD_CONTACTS_V01
JOIN station_profile ON TABLE_HRD_CONTACTS_V01.station_id = station_profile.station_id
WHERE station_profile.user_id = 2
GROUP BY COL_CALL
HAVING COUNT(*) > 1 AND TIMESTAMPDIFF(SECOND, Mintime, Maxtime) < 1500;And I was able to find a lot more duplicates (even though some false positives were returned, but those were easy to filter out). What is your experience on this? It was really helpful when I merged paper logs from old contests, recovered from lost HDDs, and other unreliable sources. P.S: the "skip dupes" on the ADIF import might fail from a similar issues, as a lot of QSOs with a few minutes distance were imported |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 8 replies
-
|
Hi, Short answer is no. What you are talking about, are duplicate callsigns, without regards for band/mode/sat. The duplicate check is for duplicate QSOs. One callsign gave 9 "dupes". Again, "skip dupes" means duplicate QSOs, not callsigns. |
Beta Was this translation helpful? Give feedback.
-
|
I will try to replicate this. I remember one for sure where the mode was set to MFSK on an item, while FT4 on another one. In that case, the ADIF specs at that time did not include FT4 yet, so those were exported as MFSK and not being detected as dupes |
Beta Was this translation helpful? Give feedback.
-
|
That would be nice, but I think you have given enough information to understand your use case. Just to be clear, I am open to changes and suggestion, but not by removing all the criteria. What I am thinking, at least for the advanced logbook, is that a dialog could be opened. |
Beta Was this translation helpful? Give feedback.
-
|
That would be awesome!!! |
Beta Was this translation helpful? Give feedback.
-
|
@iu2frl i'd suggest that you go to LBA and correct those QSOs with the wrong mode to an ADIF-compliant one. After you cleaned your QSOs you can run the original DupeCheck again. and tbh: As @AndreasK79 already stated: A dupe is: Call, Time, Band and Mode are the same. If we would change that, there will be complains because of false positives. Even in a contest it's very very usual that you work the same station within seconds across several bands. A dupe-check should stay a real dupe-check. And: Cleaning up your Data / Harmonizing it / Keeping it clean is always the best option. |
Beta Was this translation helpful? Give feedback.
-
|
I double the opinion of @int2001 |
Beta Was this translation helpful? Give feedback.
-
|
Yes, there are surely alternatives and better approaches. |
Beta Was this translation helpful? Give feedback.
@iu2frl i'd suggest that you go to LBA and correct those QSOs with the wrong mode to an ADIF-compliant one. After you cleaned your QSOs you can run the original DupeCheck again.
Everything is there.
and tbh: As @AndreasK79 already stated: A dupe is: Call, Time, Band and Mode are the same. If we would change that, there will be complains because of false positives. Even in a contest it's very very usual that you work the same station within seconds across several bands. A dupe-check should stay a real dupe-check.
And: Cleaning up your Data / Harmonizing it / Keeping it clean is always the best option.