View Full Version : Delete whole Logbooks
DL9KSM
08-09-2010, 07:36 AM
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
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. ;)
DL9KSM
08-09-2010, 06:27 PM
I have basically the same issue. ;)
Yes ... that's the Prob. But i don't want do delete every single QSO ... :confused: 3000 qso its torture .... :eek:
HEEEEELP US .... :(
73 de Karl :cool:
3000 qso its torture .... :eek:
I have 12000 dupes :eek::eek::eek::eek:
EI9JU
08-10-2010, 11:28 PM
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.
DL9KSM
08-15-2010, 03:26 PM
i will forward your problem
73 Helmut
What do you think how much time it takes to delete my Logbook ? :mad:
It's better to to it soon before everybody ist starting to confirm the
duped entries ? ;)
I did a request for delete the whole logbook at the support but i get
no response until today ... :(
I hide the Logbook in the Options until this is fixed for me ...
Somebody in the position to inform the support-team soon ? :cool:
73 de Karl
AA7BQ
08-16-2010, 01:13 PM
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?
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.
AA7BQ
08-16-2010, 02:11 PM
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
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.
KB8LFA
08-17-2010, 02:47 AM
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?
What about QSOs that have been confirmed automatically but have invalid or missing data? For example, I uploaded quite a few with 0.0MHz, and it appears in the log as " mhz" also another record I see all the time is "0 watts"... I would like to know my QRP contacts vs. when a record simply didn't have a power adif entry. Another I see is 0.00000 Lat/0.00000 Lon. Some I see an ITU zone defined and others not, same with CQ zone.
These are all on confirmed entries. I'd like to apply the correct ITU/CQ Zone as those might be valid for future awards. If the record is locked, that's it, done deal.
I wonder if it would be better to lock essential data, i.e. that of what constitutes a valid QSO match... date, time (+/-30min), band and mode. Then allow updates to the rest?
About awards. It's interesting that an award may be valid and then invalid. Let's give this scenario. Say I am a roving station and I submit my log in error. I had stated CQ Zone 4 but I was actually in 3. When doing routine audits I find the error but the QSO was already granted credit for CQ Zone 4. Which is worse, giving credit for an incorrect CQ Zone or allowing the logging station to update it to a correct CQ Zone 3?
I'm not sure, just tossing things out I am thinking of when browsing my own log book and confirmations.
KB8LFA
08-17-2010, 03:01 AM
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?
Thinking about this more... I wonder if the QSO XYZ shouldn't be marked as "Used in award" when a person is granted an award where QSO XYZ is used. At that point it becomes locked. If station ABC submitted wrong data they can change anything or even remove it up until the point in time the QSL is USED. If the QSO is NOT USED then any editing or removal can be done?
I think you would be much better off handling this when the logs are uploaded. Just don't accept entries with a duplicate time and call, then allow deleting of the entire log book except confirmed contacts. The user then deletes all the entries accept those that are confirmed and then uploads the log again. The upload process eliminates entries with a duplicate time and call, so it will not reenter the confirmed contacts.
The only issue I see with this approach is when the user who is uploading has confirmed the contact from another users log and the time does not match. To get around that I would think those records that have a duplicate call and date (not time) would be marked in some way.
This leads to my question. If I have the call logged in my log and the user I had the QSO with has already sent me the log to confirm, how do tell the program that these two log entries are duplicates?
DL9KSM
08-23-2010, 05:17 PM
I think you would be much better off handling this when the logs are uploaded. Just don't accept entries with a duplicate time and call, then allow deleting of the entire log book except confirmed contacts. The user then deletes all the entries accept those that are confirmed and then uploads the log again. The upload process eliminates entries with a duplicate time and call, so it will not reenter the confirmed contacts.
I agree with this totaly ... This would be the best :cool: If the Time, Call, Band is a dupe than just overwrie the existing entry ... exept confirmed QSO ...
Plus a method to mark and delete unconfirmed QSO's .... :p
73 Karl
K2AFY
08-24-2010, 08:14 PM
I think you would be much better off handling this when the logs are uploaded. Just don't accept entries with a duplicate time and call, then allow deleting of the entire log book except confirmed contacts. The user then deletes all the entries accept those that are confirmed and then uploads the log again. The upload process eliminates entries with a duplicate time and call, so it will not reenter the confirmed contacts.
The only issue I see with this approach is when the user who is uploading has confirmed the contact from another users log and the time does not match. To get around that I would think those records that have a duplicate call and date (not time) would be marked in some way.
This leads to my question. If I have the call logged in my log and the user I had the QSO with has already sent me the log to confirm, how do tell the program that these two log entries are duplicates?
In the interim I have sent e-mails to those that are dupes since I uploaded my logs a have a few that are confirmed both ways. In most cases It has been the time was off a minute or so or the frequency off one decimal position, depending on how far out a log records the frequency. Agree the best would be to have the upload handle.
I have used e-mail and not rejecting since rejected qsos can not be deleted yet.
K1NWB
10-29-2010, 12:09 AM
if we had the ability to do a 'multi-edit' so we could hi-lite the dupes we wanted to get rid of, that would be acceptable to me...thots?
ON2AD
11-29-2010, 11:55 PM
Hello,
Today my callsign is changed from ON3AD to ON2AD.
After my mail to the staf of QRZ.com the have change my login of ON3AD to ON2AD but in the logbook there are abt 93 QSO confirmed from my old Call.
How I can delete those because this isn't not QSO's from ON2AD but from ON3AD.
73 de Pat ON2AD
KB8VAO
12-12-2010, 03:59 PM
Please tell me where I can find "DELETE ALL UNCONFIRMED" button.
Thank You
Steve
ON2AD
12-12-2010, 10:43 PM
Hi, Steve
I have delete one by one, but I can't delete the Confirmed QSO's
The Confirmed QSO's are from my old Call ON3AD and now I have ON2AD .
73 de Pat ON2AD
Hello,
Today my callsign is changed from ON3AD to ON2AD.
After my mail to the staf of QRZ.com the have change my login of ON3AD to ON2AD but in the logbook there are abt 93 QSO confirmed from my old Call.
How I can delete those because this isn't not QSO's from ON2AD but from ON3AD.
73 de Pat ON2AD
Prior to adding the Logbook feature, QRZ only maintained a user’s “primary” callsign (X1XXX) in its database and not the others used by you that are referred to as “aliases”, for example a slashed prefix/suffix variant (VE2/X1XXX, X1XXX/MM, etc.) or a different past or current unique callsign (Y2YYY).
Aliases can now be added to your current primary callsign page by signing in and calling the page up; then click on the Detail tab and then the EDIT RECORD button. Select the Callsign Data option and scroll down to the “Add Aliases” section. Add the alias(es) and click on the Save Changes button. Then when anyone searches by one of your alias calls, your primary page is displayed along with an “aka callsign” label (also known as) along side of your callsign.
At the moment it is not possible to retrieve or organize your log entries by primary and alias callsigns but this should be corrected in the future.
With regard to deletion of log entries, at the moment it is also not possible to delete confirmed entries on the basis that they might already have been applied to the other party’s award record.
DO6MBA
12-16-2010, 01:01 PM
Hi,
want to delete more than 3000 QSOs.
How is this possible?
thanks a lot , 73
Manfred
DO6MBA
PA0PAF
12-18-2010, 08:07 PM
Hello Fred,
I want to stop using the logbook feature on QRZ.com entirely. So I want to remove my entire logbook. I understand and appreciate your thoughts about that, but fact is I want to stop using it. How can I solve this problem?
73, Fred PA0PAF
I want to stop using the logbook feature on QRZ.com entirely.
The QRZ Logbook function is enabled by default. To disable this function or modify its status:
· Click on “FORUMS” to launch the Forum home page
· At the top left, click on “UserCP” to launch the User Control Panel
· In left hand column, click on “Edit Options” to launch the Options page
· Search down the page and locate the Logbook choices to “Enable” or “Disable” as desired.
· Click on “Save Changes”
