Looking at the experimental Account Manager.
1) What are "orphans"?
2) What happens when I click "Fix" orpahns?
3) I have messed up BAD in trying to correct a QTH problem.
- It is possible to delete an account?
- It is possible to request to have a large group of QSOs deleted? (Can't do it at my end as some have already been claimed.

---

NT2F Jim Key

Hi Jim,

1. I don't see the term "Orphan" or any link to "fix orphans" when I look at my account. Thus, here's a WAG - Orphans may be secondary accounts (Old Call/QTH/Special Event, etc.) that aren't attached to your primary account. If you don't have any of those, please tell us exactly what it is you're looking at.
2. They can't reproduce?
3. a. If you have received any eQSLs to the account you want to delete, they will be lost when you close the account.
b. You can request anything from the admin(s). How long it will take them to respond is beyond my ability to guess because I have no idea about their workload.

73, Doug, W5DET

---

What?!? You're still wasting time and money sending QSL cards via Snail Mail? Whatever for? Go Unpostal!

Doug,

Thanks for the reply. Let me explain the situation in detail. I initially set up e-QSL with the account:

QTH for WB4JVR 1969-2009 in TN

In 2009 I changed call signs to NT2F set up my e-QSL correctly.

However the reality of the situation is as follows:

QTH for WB4JVR 1969-2003 in GA [103 QSOs]
QTH for WB4JVR 2003-2009 in TN (then call change) [1653 QSOs]
QTH for NT2F 2009-present in TN [978 QSOs] <== This account is correct.

I started using e-QSL in perhaps 2007 and uploaded ALL the WB4JVR QSOs with the TN QTH. It took until recently to realize my mistake ... that ALL of the GA QTH QSOs [103] had the incorrect TN address.

So I went into "My Account and using the link "Experimental: Account Manager" split the WB4JVR account into 2 QTHs, and added the WB4JVR GA QTH as an account. So I ended up with the following accounts:

QTH for WB4JVR 1969-2003 for GA QSOs
QTH for WB4JVR 2003-2009 in TN
QTH for NT2F 2009-present in TN

What I did was to ADD the TN account with the 2003-2009 range and change the old account to date range 1969-2003.

I then attempted to correct the QTH for the GA QSOs by re-uploading the 1969 - 2003 contacts with the correct GA address info. A lot of these were rejected as duplicates even with the revised QTH.

Now when I look at the Account Manager screen I see:

eQSLs
WB4JVR - GA [539 QSOs]
WB4JVR - TN [1260 QSOs] + a message"(435 orphans)"
NT2F - TN [978 QSOs]

Next to the orphan message I have a button appearing that says "Fix."

I think what has happened is that eQSL is not allowing me to revise the QSOs that have already been retrieved as QSLs by other users.

If you look at the numbers for WB4JVR you'll notice that if I subtract the 435 orphans for TN from the 539 QSOs in GA I get 104 - which is essentially the number of QSOs that should be credited to TN. Also ADDING the number of orphans (435) to the TN account (1260) gives 1695 which is close to the correct number of 1653 TN QSOs.

I cannot correct the GA address in the WB4JVR-GA account. It refuses to save my changes.

So back to the original questions:
1) What are these orphans?
(Unsure of your WAG because all counts are attached. I think they are of 2003-2009 TN
date range but still attached to the 1969-2003 GA account because that is where they
originally were created)
2) What does "Fix" orphans button do?
(I'm not brave enough now to click on it. Will it move all the incorrect GA
QSOs into the TN account?)
3) Can I request the WB4JVR account QSOs be erased or emptied?
(Seems to me the easiest solution because I can easily re-load ALL the QSOs.)

And yes I can understand the admin response time may be slow - I know exactly how those things go and can be patient. But perhaps I am missing something really obvious and can correct it without adding to their work load. Surely I'm not the first to have done something this idiotic. Or perhaps I am ... one should never underestimate their own stupidity.

Sorry for the length of this message, but it is directly proportional to the stupidity of the guy who got me into this mess.

Oh yeah, my Maltese says, "Why did you have me fixed if I wasn't broke?!?"

73, Jim/NT2F

---

NT2F Jim Key

OK, we can now move to SWAGs.

First, everything I know about eQSL I have garnered from using the system and the diagnostic skills I acquired when I used to test software systems for what they were actually doing compared to what they were supposed to be doing. Back then, I had the advantage of having the design specs on hand, but, I digress.

It appears that part of your problem is that you ended the period of WB4JVR when you acquired NT2F. I surmise that is why you are unable to revise the address for WB4JVR-GA. To further complicate matters, I think eQSL checks the FCC database for valid license periods which inhibits changing the period and other info for expired licenses.

Another part of your problem is that you were attempting to use beta software for this task. For all I know, "Experimental" may be defined as ALPHA version software on eQSL. Either way, not the best of choices.

At this juncture, I would throw myself to the mercy of the Admins and hope they can help you sort out the mess. Pragmatically, I would upgrade my eQSL membership as a sacrificial offering (not unlike throwing virgins off a cliff!) to entice the eQSL gods.

As for your original questions,

1) I think now that the definition of an "Orphan" is in incoming eQSL confirmation that cannot be matched up to an existing account because the exact callsign isn't in the database, or the callsign and date range(s) don't coincide.

2) 'Fix orphans" probably allows you to point the incoming records at the correct account belonging to you. Again, I have never seen or had occasion to use this function.

3) There might be a problem with the system rebuilding the links to incoming confirmations if your account is wiped and reloaded. The outgoing confirmations may become hosed, too.

There is a reason that the ability of users to tweak the data in their accounts is restricted. The eQSL database has tens (yea, hundreds) of millions of records and keeping it in good order is not at all like maintaining your log on your own computer.

Good luck with the virgins.

73, Doug-W5DET

---

What?!? You're still wasting time and money sending QSL cards via Snail Mail? Whatever for? Go Unpostal!

Doug,

Thank you for sharing your thoughts on my foul-up. My last e-mail was long winded so I appreciate you taking the time to read it and provide feedback.

And yes I understand why it is necessary to limit user control but you never know what a software package is capable of until you try to deal with exceptions. I have been working with computers and writing code since the late 60's (thankfully I don't code for a living). Sometimes there are clever work arounds. Sometimes there are not. Sometimes the answer is staring you in the face. Sometimes it is laughing behind your back.

I have a message into support so I'll just chill out and wait for their reply. Perhaps I'm making a big deal over nothing. After all there are only 100 or so QSOs that could be affected.

Thanks again for your time and trouble and have a great DX day.

73 - Jim/NT2F

---

NT2F Jim Key

An update on this issue.

Decided to go for broke and clicked on the "Fix" button. Doug, your guess was correct. All QSOs are now in the correct accounts.

It correctly displays the street address for the GA QTH, but will not allow me to change the county or grid square. So perhaps I'm making headway.

73 - Jim/NT2F

---

NT2F Jim Key

Someday, the question "What does the 'fix' button do?" will reappear. Thanks for letting me in on the secret.

As for changing county and grid square, for whatever reason, the system hasn't allowed that ever in my experience. The restriction is nonsensical unless the system does a lookup somewhere.

Now I'm left to wonder what happens if you change your zip code to one in another county?

W5DET

---

What?!? You're still wasting time and money sending QSL cards via Snail Mail? Whatever for? Go Unpostal!