www.dl2rum.de

Hi,
I saved my log from RUMlogNG and imported that to QRZ. The result is more than 1200 duplicate QSOs. The dupes are always 1-2 minutes later than the existing entry.
How can I remove the duplicates? The number is so high that a manual removal would be a very long task.

Thanks
IT9GGG

I asked for help from QRZ support; they said that somehow, RumLog changed the log time of 1 minute and therefore posted duplicates (several hundred) on the QRZ database that accepted them because of the different time stamps. It seems there's one unique solution: cancelling duplicates by hand. Several days of work!!!

Thanks RUMlogNG!!!

Manually removed about 900 duplicated QSOs. I could not figure out how and why RUMLog duplicated some of them (about 1900+ correct QSOs before the disaster).

It's very sad to see that nobody took care of replying to this thread. I'm abandoning RUMLogNG, of course, but I still remain curious: Why did it happen?

I'm pretty sure I did everything in the right way. I exported the log file from RUMLog and imported it into the QRZ website.
73,
IT9GGG

RumLog changed the log time of 1 minute and therefore posted duplicates

RUMlog doesn't change the log time by itself!

It's very sad to see that nobody took care of replying to this thread.

It seems nobody has an idea what you have made. Why do you upload your log twice?

Upload to qrz from the app was not working so I exported my log to an ADIF file, uploaded that to the qrz website and it did change the times of the QSOs, thus adding tons of dupes, that’s a fact although I do not understand why and how. I can report the mail from the qrz support they arrived to my same conclusion: something happened with time in the exported ADIF log file

BTW: I've just seen on the Apple store page of RUMlogNG that there has been a recent fix:
"Fix: ADIF export - QSO_DATE_OFF may be not correct - Tnx todivefor".

It seems I was not the unique one to meet this issue, thanks to todivefor from me too

Perhaps I could give RUMlogNG another try (indeed I used that for a while in the past without any issue)

No, this was another issue. There was a problem with a specific setup of the user fields when your QSO start date was different than QSO end date, around 00:00z.