|
|
-
 Delete whole Logbooks
Hi there
I did a mistake and load my log up double ...
How i can delete the whole log and correct this with an
upload completly ???
73 - Karl
-
-
-
de N4ST (Jim)
-
 Originally Posted by N4ST
I have basically the same issue. I uploaded my logbook without my personal data being completely filled in, like Lat/Lon, Grid, Power, etc. So I bulk corrected those in my HRD log and uploaded them again. On LoTW, you can overwrite unconfirmed QSOs, but here it just made two copies. 
To all of you out there that are confirming my duplicate QSOs; it does make my QSL count go up a lot quicker. 
Others must have made the same mistake because I've had several duplicate QSO's sent to me, I usually confirm one and reject the other.
-
Suport Request for delete the whole Log failed
-
Delete Whole Log
Folks,
I'm willing to provide a "Delete All" function to the logbook, however:
I feel that once a contact has been confirmed then the record should be "frozen", i.e., no longer subject to modification of any kind. Once a contact has been confirmed, both parties have agreed to the details.
Suppose, for example, that station A logs a contact with station B and this contact completes station B's DXCC award. Then, station A decides to remove all of his logs and now station B's DXCC award, which has already been issued, is invalid.
It is for this reason that I maintain that confirmed logs should be frozen. Now, on the other hand, I see nothing wrong with deleting all UNCONFIRMED log entries.
Your thoughts?
-
Originally Posted by AA7BQ
Folks,
I'm willing to provide a "Delete All" function to the logbook, however:
I feel that once a contact has been confirmed then the record should be "frozen", i.e., no longer subject to modification of any kind. Once a contact has been confirmed, both parties have agreed to the details.
Suppose, for example, that station A logs a contact with station B and this contact completes station B's DXCC award. Then, station A decides to remove all of his logs and now station B's DXCC award, which has already been issued, is invalid.
It is for this reason that I maintain that confirmed logs should be frozen. Now, on the other hand, I see nothing wrong with deleting all UNCONFIRMED log entries.
Your thoughts?
Fair enough. There should be two broad range deletes - DELETE ALL UNCONFIRMED and DELETE ALL DUPLICATES (confirmed or not) leaving only one.
-
Originally Posted by W1DQ
Fair enough. There should be two broad range deletes - DELETE ALL UNCONFIRMED and DELETE ALL DUPLICATES (confirmed or not) leaving only one.
Okay, so how do we define Duplicates? How many identical points of info between two log entries defines a duplicate? Which data are considered? Which one goes when there are two or more meeting the criteria?
-fred
-
Originally Posted by AA7BQ
Okay, so how do we define Duplicates? How many identical points of info between two log entries defines a duplicate? Which data are considered? Which one goes when there are two or more meeting the criteria?
-fred
O.K., thanks. Now we get back to the more fundamental unanswered question that is what constitutes a match? My vote is for a very basic match, that is date/time, call, band, mode. You will have to allow a time window, e,g, +/- 30 minutes.
Duplicates and confirmations thus meet the same criteria.
And thus will either duplicate contain the appropiate confirmation criteria. In the case there are two QSO'S the 30 minute window, then it is known up front that only one will be recognized and it can be either one.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
3000 qso its torture .... 
